Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.17.4-preview
Issue ID
ADDR-1820
Regression
No
Textures on a material within an Addressable asset bundle becomes mixed up after loading it in a scene
Reproduction steps:
1. Open attached project "RollerStrip.zip" and scene "Boot"
2. In Addressable Groups window, select Play Mode Script -> Use Existing Build (requires built group)
3. In Addressable Groups window, select Build -> New Build -> Default Build Script
4. After the build is complete, enter Play Mode
5. In Game View, observe the two models
Expected result: No differences
Actual result: Mixed up textures on the right model
Reproducible with: 1.17.4-preview (2019.4.20f1)
Not reproducible with: 1.17.4-preview (2020.1.17f1, 2020.2.4f1)
Could not test with: 2018.4.31f1 (compilation errors), 2021.1.0b7, 2021.2.0a5 (Adressables build fails to compile)
Note:
To reproduce with attached project, in "UnityWebViewPostprocessBuild.cs" comment out lines that contain compilation errors.
Workarounds:
1. If you place the textures under the folder Assets/_ResourceBank/Textures/Characters/Logos into another addressable group and build that into another separate asset bundle, the textures will not get mixed up
2. If you clone the textures and use those cloned textures for the materials instead, this problem isn't reproducible as well.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Fixed in 2020.1.0a18