Search Issue Tracker
Fixed in 2017.2.0f3
Votes
1
Found in
2017.2.0b10
Issue ID
950510
Regression
Yes
[WindowsMR] Unity repeatedly asserts when starting play-in-Editor without MRP running
Steps to reproduce:
1. Open the attached project
2. Open the default scene
3. Switch platform to Windows Store
4. Play the scene (when Mixed Reality Portal is not running)
5. Observe the assertion:
Assertion failed: Failed to get culling frustum from IHolographicCameraPose! [0x0]
Actual results: Unity throws the assertion
Expected results: Unity should not throw assertion
Note:
Make sure you are running Windows 10 build 16257 or higher
Reproduced with: 2017.2.0b8, 2017.2.0b11, 2017.3.0b17
Not reproduced with: 2017.2.0b7
Regression introduced in: 2017.2.0b8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
- "Unable to get the list of approved APIs." is thrown when testing the App Packages with Windows App Certification Kit
- [Linux] The mouse wheel input is inverted when scrolling in the Build
Add comment