-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Since you are among the best uwp rendering gurus at Microsoft, I was wondering what thoughts you might have about a somewhat similar rendering problem but in a very different context.
I've been toying with how best to render a XAML surface and have it displayed within a Unity texture. For now I'm mostly interested in the rendering side of things and not worrying about input just yet. What would be the best approach from a performance perspective?
I would like to leverage XAML for the many complex 2D panels I'll need in my Unity app. XAML is so much more efficient for 2D work and has such a rich API, it seems wasteful not to leverage what's there when running on a Mixed Reality device.
I'm also curious why XAML surfaces aren't a thing in any of the WinRT 3D API's currently available from Microsoft?
Thoughts, ideas, suggestions?