Search Issue Tracker
Active
Under Consideration for 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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
spektragames
Nov 24, 2025 07:33
+1, Having same issue with Addressables 2.7.4 and Unity 6000.1.17f1