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
- Multiple errors are thrown and file does not parse when saving after removing a duplicate UI Document instance from the hierarchy
- Custom Inspector throws a NullReferenceException error even when using #if UNITY_EDITOR preprocessor directive
- Sun and Clouds are distorted when using Tonemapping mode ACES
- "Camera" component's FSR2 Mode override does not change the FSR2 Mode when the "Use FSR2 Custom Attributes" option is disabled in the "Camera" component
- Addressable Asset Settings link to the documentation isn’t working
Add comment