Hello,
Some time ago, I’ve reported a bug to Unity which prevents us from debugging our game builds (internal ticket Jira Service Management ), however I’ve gotten no response for two months. This is quite troublesome as the player count is growing in our game and I have no way to test certain issues, thus I’m re-posting the issue here as Unity folks seem to be busy:
Building the game in Development mode completely breaks rendering on Quest 2/Quest 3 devices and results in square artifacts all over the screen. I noticed that it’s affected by Compatibility Mode, Development builds and FMOD plugin. Seeing how unchecking compatibility mode causes this issue, its leading me to believe there is some regression in the URP library. The issue was not present in prior minor U6 versions (prior to 6000.0.47f1), though I cannot pinpoint exactly if this started on 6000.0.47f1, though I can confirm that this setup worked on U6 (no black squares).
Repro steps:
- Enable Render Graph Compatibility Mode (enabled in attached project by default)
- Plug in Q2 or Q3 device
- Make a Development Android build
- Deploy it to the HMD
- Run game
- Notice black squares all over the screen with distorted rendering
Workarounds (each can be done separately):
- Disabling Compatibility Mode
- Making a Non Development build
- Deleting FMOD Plugin
None of the workarounds apply to us, FMOD is essential, and we cannot use non-compatibility mode as it halves our performance on Q2 builds. Additionally, temporarily disabling compatibility mode is also a no-go, as then we get false results when profiling with RenderDoc.
I can send the repro project via DM to an FMOD developer, though I don’t want to share it publicly as it contains paid assets.
Any tips appreciated!