Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a1
2019.1.10f1
2019.2.0a1
2019.3.0a1
Issue ID
1169416
Regression
No
Warning on affected shader count is not thrown when trying to collect shader variants with Async Shader compilation enabled
How to reproduce:
1. Create and open a new Unity Project
2. Create a new Cube GameObject in the Hierarchy window
3. Go to Edit -> Project Settings -> Editor
4. Enable the Asynchronous Shader compilation
5. Go to Edit -> Project Settings -> Graphics
6. Click on the "Clear" button at the bottom of the window
Expected result: A warning about additional shaders being added by Async Shader compilation
Actual result: No warnings
Reproducible with: 2019.1.11f1, 2019.2.0b10, 2019.3.0a10
Additional notes: You can see which Shaders are being added when Async Shader compilation is enabled if you clear tracked shader information and click on "Save to asset..." button next to the "Clear" button in both cases, and then compare saved Shader assets.
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
- Internal Package Manager window lines becomes duplicated or splits into two when window is docked
- Particle System curve editor does not remove or delete a curve when clicking the "Remove" button
- Some deprecated packages are seen in "Unity Registry"
- [Material]The emission of the materials used in scenes does not carried over correctly after upgrade project to 6000.0.44f1
- Crash on StackWalker::GetCurrentCallstack when opening a project
Resolution Note (2019.3.X):
Every few months we look at bugs which we have not had the opportunity to fix yet. We try to be as diligent as we can and want to prioritize bugs that are causing issues with shipping and frequent pain points in day to day works. To ensure we are targeting the most important bugs we regularly close out older bugs that have not reached this threshold over the past months. The bug you have currently raised has not met this threshold for fixing over the last few months. If you feel this bug has been closed by mistake then please reopen the case.