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.

Galaxy Explorer protected memory exception

Dave_WDave_W
edited April 2016 in Questions And Answers

I keep getting a protected memory exception whenever I try to run Galaxy Explorer in the emulator. Once the application starts, I am able to see the initial introduction and the app prompts me to "pin the earth in the center" of my room. I pin the earth, an animation starts, and then the below exception is immediately thrown...

"An unhandled exception of type 'System.AccessViolationException' occurred in UnityEngineProxy.dll
Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

  • The project builds without issue in Visual Studio.
  • Deployment to the HoloLens Emulator works fine as well.
  • I've tried building the project within Unity on multiple computers and running the outputted Visual Studio project/emulator on multiple computers but all of them throw the same exception.
  • The app is able to build and run in Unity without any issues, the exception only shows up when starting the emulator from Visual Studio.

Any ideas?

Best Answer

Answers

  • jstulojstulo
    edited April 2016

    I am getting the same error at exactly the same point.

  • I am getting the same error at exactly the same point. The error is thrown in the TransitionManager class at the point when the array of colliders is enumerated disabling each.

  • @DeckTwelve I had just come the same conclusion a couple of minutes before you posted the answer :) Thanks!

Sign In or Register to comment.