Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
1
Found in
2020.3.4f1
Issue ID
UUM-6143
Regression
No
[XR][Vulkan] Post Processing artifacts on Quest 1
Steps to reproduce:
1. Open the attached project "URP_Template.zip"
2. In Build settings, switch platform to Android
3. In Player settings, make sure Vulkan is the Graphics API
4. Build and Run on Quest 1
Expected results: post-processing artifacts are not present on Quest 1 when using Vulkan
Actual results: post-processing artifacts are present on Quest 1 when using Vulkan
Reproducible on: URP 10.4.0 - 13.1.6 (2020.3.40f1, 2021.3.10f1, 2022.1.19f1)
Not reproducible on: URP 14.0.3 - 15.0.1 (2022.2.0b8, 2023.1.0a12)
Reproducible with these devices(Vulkan):
VLNQA00275 - Oculus Quest (Quest), CPU: Snapdragon 835 MSM8998, GPU: Adreno 540, OS: 10
Not reproducible with these devices(Vulkan):
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 10
N/A, Google Pixel 3 (Pixel 3), Android 12, CPU: Snapdragon 845, GPU: Adreno (TM) 630
VLNQA00413 - Samsung Galaxy Note10+ (SM-N975F), OS: 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
VLNQA00372 - Galaxy S21 5G (SM-G991U), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00202 - Samsung Galaxy Note 9 USA (SM-N9600), CPU: Snapdragon 845 SDM845, GPU: Adreno 630, OS: 9.0.0
VLNQA00177 - Xiaomi Mi Note 2 (Mi Note 2), OS: 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno 530
Notes:
-If post-proc volume is disabled then the bug does not occur. The bug does not occur using OpenGLES3. If XR Management and the Oculus package are removed from the project and ran as non-XR on Quest, then the bug does not occur.
-In the blackness of the background if there are thin squiggly lines like elevation gradients on a contour map, then you are experiencing the bug.
-Head tracking is not enabled on the Camera to make it easy to compare XR versus non-XR behavior.
-Note that if you wish to run on Quest as a non-XR app, you need to remove XRSDK and the Oculus provider via Package Manager. Toggling these off in Project settings is not sufficient.
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2020.3.X):
Won't fix: in the generated shader code GPU driver rounds extremely small value "9.9999997473787516355514526367188e-06)" to zero, which later causes division by zero in the Bloom postprocessing shader.