Search Issue Tracker
Fixed in 6000.1.0a4
Won't Fix in 6000.0.X
Fixed in 6000.1.X, 7000.0.0a8, future release
Votes
38
Found in
6000.0.10f1
6000.1.0a1
Issue ID
UUM-75262
Regression
No
Shaders are always recompiled when the Editor is opened
Reproduction steps:
1. Open the attached “IN-77989“ project
2. Open the “Level_Bionic_Downfall“ scene and observe the Scene view
3. Notice that the shaders appear cyan for a brief moment
4. Close the Unity Editor
5. Open the project again
6. Observe the Scene view
Expected result: The shaders are immediately rendered
Actual result: Shaders appear cyan for a brief moment, signaling shader recompilation
Reproducible in: 6000.0.10f1
Could not test with: 2021.3.40f1, 2022.3.37f1 (Could not resolve package errors)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Note: Could not search for regression due to package errors when downgrading the project
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
- [VisionOS] Animating a material property results in artifacts when the app mode is set to RealityKit and shader modifies the Vertex Shader
- "DirectoryNotFoundException" is thrown and Shader Graph does not open when opening a .shadegraph from a long path
- “Full Screen Pass Renderer Feature_Old GUID” text is cut off in Renderer Features window
- "Undo: Already found nextRootTransform, but with different state cached" error thrown when undoing changes made to the Hierarchy using a script
- "No GUI Implemented" is displayed when using PhysicsMask with a CustomEditor
Resolution Note (fix version future release):
The editor startup shader variant warmup had a bug that prevented correct variants from being warmed in time, thus causing the one frame of cyan. However, the cyan rendering does not necessarily mean recompilation. This also happens atm when the variant is loaded from the cache.
Resolution Note (fix version 6000.1):
The editor startup shader variant warmup had a bug that prevented correct variants from being warmed in time, thus causing the one frame of cyan. However, the cyan rendering does not necessarily mean recompilation. This also happens atm when the variant is loaded from the cache.
Resolution Note (6000.0.X):
The cyan rendering does not always mean recompilation. Loading the variant from the cache is also treated as an async operation which means there could be one frame of cyan when loading from the cache. This is what happens in this bug case.
The issue is cosmetic only and the proper fix involves enough risk that we wanted to postpone it until 6.1 to avoid any regressions in the live version.