The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
HoloLens Unity UWP Build Type XAML vs D3D
The HoloLens Unity layer doesn't provide a built-in virtual on-screen keyboard for text input.
The docs mention one would have to create the app as XAML Build Type:
https://developer.microsoft.com/en-us/windows/holographic/keyboard_input_in_unity
Interestingly does XAML build type still render as 3D into a holographic view now. I tried that and used XAML as build type in Unity Build Settings and it actually still rendered in 3D not in a 2D window. Previously it rendered XAML build type as 2D window, not 3D. Not sure when that changed.
What is actually the drawback of using XAML as build type compared to D3D?
SwapChain and overlaying overhead?
René Schulte | Director, Immersive Experiences | Microsoft MVP Windows Development
www.identitymine.com | http://blog.rene-schulte.info
Best Answers
-
Options
AlexD
✭✭✭
I was confused as well at the beginning, thinking that XAML will render a 2D app while D3D will give you a 3D app but that's not the case.
The 2D / 3D switch is dictated by theVirtual Reality Supportedflag in the Player settings.
The difference between XAML and D3D is actually in the UWP project that gets generated related to the way the space is initialized - the XAML one will start as 2D and seamlessly migrate to volumetric 3D. This allows you to go back to 2D when you need to open the keyboard then back to 3D when you're done with it.5 -
OptionsAlexD
✭✭✭
Not that I can see so far. I'm actually in the process of writing a blog post about this, I'll come back with a link when I publish
5
Answers
I was confused as well at the beginning, thinking that XAML will render a 2D app while D3D will give you a 3D app but that's not the case.
The 2D / 3D switch is dictated by the
Virtual Reality Supportedflag in the Player settings.The difference between XAML and D3D is actually in the UWP project that gets generated related to the way the space is initialized - the XAML one will start as 2D and seamlessly migrate to volumetric 3D. This allows you to go back to 2D when you need to open the keyboard then back to 3D when you're done with it.
Toronto-HoloLens | Blog | @alexdrenea
Thanks Alex, so there's actually no downside in using XAML as Build Type?
René Schulte | Director, Immersive Experiences | Microsoft MVP Windows Development
www.identitymine.com | http://blog.rene-schulte.info
Not that I can see so far. I'm actually in the process of writing a blog post about this, I'll come back with a link when I publish
Toronto-HoloLens | Blog | @alexdrenea
Sounds great. Looking forward to it.
René Schulte | Director, Immersive Experiences | Microsoft MVP Windows Development
www.identitymine.com | http://blog.rene-schulte.info
published that article I promised: You can find it here
Toronto-HoloLens | Blog | @alexdrenea