Steps to reproduce:
1. Open the attached user's project "fmod-rendergraph-bug-master.zip"
2. Switch to Android and open "Assets/Scenes/Scene_Sample.unity" Scene
3. Make sure a Development Build is enabled
4. Make sure Render Graph Compatibility mode is enabled
5. Build to a Quest 2/3/3S devices
6. Observe the rendering artifacts in the HMD (additionally 1 eye doesn't render)
Expected result: rendering is the same as in Game View
Actual result: graphical artifacts appear when all 3 conditions are met (Vulkan, Development build, FMOD plugin)
Reproducible with: 6000.0.3f1, 6000.0.56f1, 6000.2.0f1
Not reproducible with: 6000.0.2f1
Could not test on 2022.3.65f1 due to FMOD plugin errors when trying to perform a build
Could not effectively test on 6000.3.x stream due to when upgrading provided project, current FMOD installation breaks and reinstalling the FMOD plugin no longer reproduces the issue (most likely due to an incorrect configuration)
Reproducible with these devices:
VLNQA00644 - Oculus Quest 3S (Quest 3S), CPU: Google Tensor G2, GPU: Adreno 740, OS: 14
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:
-A RenderDoc capture is attached "RenderdocCapture"
-Issue only reproduces with Vulkan Graphics API
-Issue only reproduces when Development Build is enabled
-Issue only reproduces with the FMOD plugin installed
-Issue reproduces with both OpenXR and OculusXR plugins