Hello everyone.

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.
Options

Hologram sharing performance issues

I'm working on adding sharing to an app. Some holograms are "shared" (i.e. child of a an gameObject that is a spatial anchor) and one is not. The hologram that is not shared is dynamic and changes position as the user moves (it's a floating menu UI). I have noticed when testing that the floating menu flickers and lags much more than the other holograms in the scene which are attached to an anchor point. Any tips on "best practices" when mixing shared/non-shared holograms in an app to help with the performance issue? Or tips for helping with performance issues in general related to sharing?

Answers

  • Options

    It's worth noting that there's usually more of a performance lag on the second device that joins the sharing session (so far I've only tested the sharing using two devices).

Sign In or Register to comment.