Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X
Votes
0
Found in
Issue ID
1368213
Regression
No
Loading shader is picked when allowAsyncCompilation = false and async compilation is ongoing
The cyan loading shader would in some cases leak into baked reflection probes. This problem may be a general shader/material problem. From studying the reflection probe behaviour, it seems that the loading shader is sometimes picked for drawing in cases where allowAsyncCompilation = false and async compilation is already ongoing. According to the semantics of allowAsyncCompilation this should not happen.
This issue does not reproduce on trunk as of Sep 24th. Repro verified in BiRP and URP. HDRP was not tested.
Remark 1: The reason that the scene view must be visible in the repro is probably that this triggers the asynchronous compilation. If you bake a reflection probe without triggering an asynchronous compilation (e.g. by hiding scene and game view) then the issue does not happen.
Remark 2: If you cannot repro the issue, you can try to clear the GI cache.
Attachments:
CyanLeak.zip: A simple Unity project that contains a sphere and reflection (as described in the repro above).
cyan-leak.mov: A video showing the repro in action.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment