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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note:
Won’t fix due to 2018.4 being no longer supported