Search Issue Tracker
Won't Fix
Votes
15
Found in [Package]
3.3.0
Issue ID
1152916
Regression
No
[XR][WindowsMR][URP] GameView Camera rendering from incorrect transform when entering play mode
Steps to reproduce:
1. Download the attached project and open "SampleScene" scene
2. Make sure that platform is UWP, XR is enabled and set to Windows Mixed Reality SDK
3. Disconnect any VR device
4. Check game view, notice that the camera is surrounded by red walls
5. Enter play mode, notice that the red walls are visible from a distance
Expected results: Entering play mode without a VR device doesn't change game view camera position
Actual results: Entering play mode without a VR device changes game view camera position
Reproduced with: 2019.3.0a3, 2019.2.0b3, 2019.1.4f1, 2018.4.1f1
Reproducible with LWRP packages: 6.5.2, 3.3.0
Note:
- Tested and did not reproduce with Oculus and OpenVR SDKs
- Could not test in older then 2018.3.0b1 due to LWRP throws multiple errors
- The issue isn't reproducible with HDRP
Workarounds:
- Enable Simulate in Editor in Holographic Emulation setting
- Switching Windows Mixed Reality SDK to none in Player settings
- Stream to HoloLens or connected WindowsMR device.
-
chris_gsa
Apr 29, 2020 06:15
Still occuring for me in Unity 2019.3.10f1 with Windows XR plugin v2.1.5.
-
Yacuzo
Jan 29, 2020 08:39
This error also occurs with the new Windows XR plugin v2.0.3 verified.
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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Resolution Note:
Given the unique set of circumstances to reproduce it, which seems unlikely to arise in normal usage, and that this occurs using the now deprecated legacy VR system, closing this issue without the intention to fix it. If you would like us to reconsider this issue, please reopen the issue.