Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
2019.2.3f1
2019.3.0a1
2020.1.0a3
Issue ID
1181148
Regression
No
[XR][WindowsMR] Using camera with Near Clipping Plane is set to 0.01 results in Screen Tearing on the device
Steps to reproduce:
1. Download attached project
2. Switch to UWP and enable XR
3. Make sure that Cameras Near Clipping Plane is set to 0.01
4. Enter play mode and look at the cylinder
Actual results: Bottom and Top of the cylinder is glitching, similarly to screen tearing.
Reproduced with: 2020.1.0a3, 2019.3.0b2, 2019.2.3f1, 2018.4.9f1, 2017.4.32f1
Note:
- The issue is visible just from WindowsMR device
- The issue is not visible in Editor or WindowMR Portal
- The is not reproducible with Oculus or OpenVR
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Resolution Note:
Won’t fix due to 2018.4 being no longer supported