Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.2.0f1
Issue ID
953977
Regression
No
Editor with no Mixed Reality device attached to the machine and simulation turned off causes the Unity editor to hard crash
Steps to reproduce:
1. Open the attached project
2. Open the Crash scene
3. Switch platform to Windows Store
4. Play the scene (when Mixed Reality Portal is on. Simulation is off and device is not connected)
5. Observe the native crash
Actual results: Unity crashes
Expected results: Unity crashes
Note:
Make sure you are running Windows 10 build 16257 or higher
Reproduced with: 2017.2.0f2
Not reproduced with: 2017.3.0b2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment