Search Issue Tracker
Duplicate
Duplicate in 6000.5.X
Votes
0
Found in
6000.2.11f1
6000.3.0b10
6000.4.0a5
6000.5.0a1
Issue ID
UUM-127590
Regression
No
Running Project Auditor's analysis only on "Assets" also analyses the "Shaders" when only "Assets" is selected
How to reproduce:
1. Create a new Unity project
2. Go to Window -> Analysis -> Project Auditor -> three-dot menu -> Preferences
3. In "Project Areas" select only "Assets"
4. In the Project Auditor, click "Start Analysis"
5. Observe the analyzed areas
Expected results: Only "Assets" are analysed
Actual results: "Assets" and "Shaders" are analysed
Reproducible with: 6000.2.11f1, 6000.3.0b10, 6000.4.0a5, 6000.5.0a1
Reproducible on: macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested
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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.
We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.
Thank you for helping us improve Unity!
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.
We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.
Thank you for helping us improve Unity!