Search Issue Tracker
Active
Votes
0
Found in
1.28.1
2.7.6
Issue ID
UUM-131793
Regression
No
Shader is not packed correctly in Addressables build when using a specific configuration
Reproduction steps:
1. Open the attached “IN-127559“ project
2. Open OutdoorScene
3. In Addresssables Groups Window, Run the Default Build Script
4. Set the Play Mode Script to “Use Exisiting Build”
5. Enter Play Mode
6. Observe the left icon shader in Game view
Actual result: The shader is not loaded (a pink texture is displayed)
Expected result: The shader is loaded correctly
Reproduced with: 1.28.1 (2022.3.71f1), 2.6.0 (6000.0.55f1), 2.7.6 (6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4)
Reproducible on: macOS 26.2
Not reproducible on: No other environments tested
Workarounds:
- Change the “Others” asset group to “Pack Together”
- Move HUDIconData_EnemySentry.asset to the “Failing” group
- Move HUDIconData_EnemySentry.asset to the “Working” group
- Move PF_Icon_TargetMaker.asset to the “Failing” group
- Remove reference to PF_Icon_TargetMaker in HUDIconData_EnemySentry.asset
- Remove reference to HUDIconData_EnemySentry in PF_AISentry_Missile
After any of these steps, Run the Default Build Script again
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Console Warning -- KeyboardIconAtlas sprite Input Outline goes beyond the boundary of the Sprite rect.
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
Add comment