Search Issue Tracker
In Progress
In Progress in 6000.6.X
Votes
5
Found in
6000.0.57f1
6000.1.16f1
6000.2.3f1
6000.3.0b1
6000.4.0b9
6000.5.0a7
6000.6.0a1
Issue ID
UUM-115875
Regression
No
Graphics State Collection warm-up does not work when using with Addressables Shaders
Steps to reproduce:
1. Open the “IN-112227” project
2. Open the “TerminalScene” scene
3. Enter Play Mode
4. Don’t provide any input and wait for the preview 2nd round
Expected result: No shader issues
Actual result: Some shaders fail to render
Reproducible with: 6000.0.57f1, 6000.1.16f1, 6000.2.3f1, 6000.3.0b1
Testing environment: macOS 15.6.1 (M4 Pro), macOS 15.5 (M2) (by user), macOS Standalone, iOS
Not reproducible on: No other environment tested
Notes:
- Also reproducible in macOS and iOS builds
- Disabling Addressables for shaders removes the problem entirely
- This suggests the Graphics State Collection warm-up process is not targeting shaders stored in Addressable memory
Comments (1)
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
- 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
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
spektragames
Nov 24, 2025 07:33
+1, Having same issue with Addressables 2.7.4 and Unity 6000.1.17f1