Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.2.0b5
2019.3.0a6
Issue ID
1161577
Regression
Yes
[WindowMR] Assertion failed on expression: 'm_FrameIndexGfxThread != m_FrameAddIndex' are thrown in play mode
Steps to reproduce:
1. Create a new project
2. Switch platform to UWP
3. Enabled XR
4. Connect WindowMR device
4. Enter play mode
Actual results: Multiple exceptions are thrown
Failed to update back buffer on holographic camera - renders may become out of sync! Error code: '0x80004005'
Assertion failed on expression: 'm_FrameIndexGfxThread != m_FrameAddIndex'
Failed to get IHolographicCameraRenderingParameters from main camera for updating rendering parameter.
Failed to get IHolographicCameraRenderingParameters from camera for depth buffer commit.
PresentUsingCurrentPredictionWithBehavior failed unexpectedly! [0x8000000e]
Reproduced with: 2019.3.0a6, 2019.2.0b6
Not reproducible with: 2019.3.0a5, 2019.2.0b4, 2019.1.7f1
Regression introduced in: 2019.3.0a6, 2019.2.0b5
Note:
-Not reproducible when remoting to HoloLens
-Not reproducible with WindowMR device with OpenVR SDK
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Incorrect warning icon and wrong message displayed in HDRP Decal Projector
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
Alexees
Jun 29, 2019 14:03
Similar here on Unity 2018.4.2f1.
Something must have happened to either Windows, Unity or NVidia Graphics drivers. Running the MR Portal from the Unity Editor is just awful. Rendering is broken (top and bottom portion smear all the time), starting the editor takes forever, MotionControllers are sometimes just not registered like they should... and, well, sometimes this error appears.