Search Issue Tracker
Fixed
Fixed in 1.19.5
Votes
0
Found in [Package]
1.18.15
Issue ID
ADDR-2186
Regression
No
Custom Shader Bundle Naming Prefix is incorrect when building Addressable content
How to reproduce:
1. Open the user's attached project
2. Open Window -> Asset Management -> Addressables -> Settings
3. In the Inspector window, find the "Shader Bundle Naming Prefix" setting (under "Build")
4. Set "Shader Bundle Naming Prefix" to "Custom"
5. In the "Shader Bundle Custom Prefix" field, write "helloworld"
6. Go to Window -> Asset Management -> Addressables -> Groups
7. In the toolbar of the Addressables Groups window, select Build -> New Build -> Default Build Script
8. In the project folder, find the directory Library/com.unity.addressables/aa/OSX/StandaloneOSX (or Library/com.unity.addressables/aa/Windows/StandaloneWindows64)
9. Observe the filename of the Shader Bundle
Expected result: custom naming prefix appears in filename
Actual result: custom prefix doesn't appear in filename, hash appears instead, and is attached as a suffix rather than a prefix
Reproducible with: 1.18.2, 1.18.15 (2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0b7, 2022.1.0a5)
Could not test with: 1.16.19 (relevant settings not found after downgrading)
Comments (1)
-
Peter77
Aug 11, 2021 12:37
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
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Resolution Note (fix version 1.19.5):
Fixed in Addressables 1.19.5