Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.1.X
Votes
0
Found in
6000.0.45f1
6000.1.0b14
Issue ID
UUM-102361
Regression
No
[Vulkan][Quest] FrameBufferFetch sample causes framebuffer corruption artifacts on Meta Quest 2/3 devices when using Vulkan
Steps to reproduce:
1. Open the attached project "Fetch.zip"
2. Open "SampleScene.unity" and enter Play Mode to observe correct rendering (Output is tinted blue)
3. Switch to Android Platform and make sure Graphics Api is Vulkan
4. Build to a Quest 2/3 device
5. Observe the corrupted rendering
Expected Results: framebuffer fetch does not produce artifacts with Vulkan on Quest 2/3
Actual Results: framebuffer fetch produces artifacts with Vulkan on Quest 2/3
Reproducible with: 6000.0.45f1, 6000.1.0b14
Could not effectively test on 6000.2.0a8 due to the output not matching the Editor (no blue tint) and no artifacts appearing
Could not test on 2021.3.50f1, 2022.3.61f1 due to RenderGraph scripting errors
Reproducible with these devices:
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
VLNQA00417 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 10
Environment tested: Windows 11 24H2
Notes:
-Issue only reproduces with Vulkan, on OpenGLES3 left eye does not render but the artifacts are not present
-Discussion thread: https://discussions.unity.com/t/urp-framebuffer-fetch-from-backbuffer/1617802/10
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 PluginManager::RefreshPlugins when closing the Editor without making any changes with JetBrains Rider selected as the External Code Editor and Google Mobile Ads third-party plugin imported
- GetMainLight() returns incorrect distanceAttenuation value for a Custom Shader when URP Forward+ Rendering Path is used
- Standalone Profiler crash on GuidReservations::Reserve when it is opened on a specific project
- m_RenderPipelineGlobalSettingsMap or m_SRPDefaultSettings is pointing to UnityEngine.Rendering.HighDefinition.HDRenderPipeline when High Definition RP package is removed
- Rendering Debugger fields have no padding at the bottom of the fields list
Add comment