Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X
Votes
0
Found in
2022.3.46f1
6000.0.19f1
6000.1.0a7
7000.0.0a1
Issue ID
UUM-79996
Regression
No
Shaders are compiled synchronously when "Asynchronous Shader Compilation" is enabled and the Camera Overlay is invoked
How to reproduce:
1. Create and open a new project from a URP Sample Template
2. Enable the “Asynchronous Shader Compilation“ checkbox in the Project Settings > Editor
3. Focus on the Scene view tab
4. Move the Scene view Camera low on the Z axis in the Scene view (to prevent instant Shader compilation on the next step)
5. Open any other Scene in the “Assets/Scenes“ in the Project tab
6. Enable the Camera Overlay in the Scene view
7. Observe the Editor
Expected result: The “Compiling shader“ box does not pop up, but a progress bar starts loading at the bottom right (Asynchronous Shader compiling behavior)
Actual result: The “Compiling shader“ box pops up (Synchronous Shader compiling behavior)
Reproducible in: 2022.3.46f1, 6000.0.19f1
Couldn’t test in: 2021.3.43f1 (No “Compiling Shaders“ box, instead “SceneView.Repaint“ pops up)
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- When “Asynchronous Shader Compilation“ is enabled, Scene view and Game view Compile shaders asynchronously as expected, only the overlay is affected
- In versions 2021.3.43f1 and 2022.3.46f1, the overlay is invoked by selecting the Camera GameObject in the Hierarchy, while in version 6000.0.19f1 there is a button in the Overlays menu (by default at the bottom) In the Scene view
- Once the shaders are compiled they are cached, the problem will not be reproducible. To be able to reproduce this issue again, the project needs to be restarted and the “Library / ShaderCache“ folder needs to be deleted beforehand
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment