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.
GalaxyExplorer crash when running on device
ccifra
✭
Hi,
I am new to this but I was hoping to get off to a good start by playing with the galaxy explorer. Unfortunately it crashes just after I place the earth on screen and see the solar system. I get an AccessViolation here:
Collider[] colliders = content.GetComponentsInChildren<Collider>(true);
foreach (Collider collider in colliders)
In TransitionManager.cs line 505.
And the output window shows:
ViewLoader: Loaded SolarSystemView
(Filename: C:\buildslave\unity\build\artifacts/generated/Metro/runtime/UnityEngineDebugBindings.gen.cpp Line: 45)
ViewLoader: Loaded GalaxyView
(Filename: C:\buildslave\unity\build\artifacts/generated/Metro/runtime/UnityEngineDebugBindings.gen.cpp Line: 45)
Supplied PxGeometry is not valid. Shape creation method returns NULL.
(Filename: C:/buildslave/physx/build/Source/PhysX/src/NpFactory.cpp Line: 675)
Exception thrown: 'System.AccessViolationException' in UnityEngineProxy.dll
The program '[2872] GalaxyExplorer.exe' has exited with code -1 (0xffffffff).
Any idea what could be wrong? I am using VS 2015 Update 2 and Unity 5.4.0b10-HTP
Answers
Fails same way in HoloLens Emulator when built in Debug x86 Stops at same line number. This runs in the Unity player
Have you tried to use a release deployment onto the device then go into the portal and start the deployment from the app section of the portal. This is probably how developers did not see this problems especially as the program runs on Unity player