Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.4
2019.4.19f1
2020.1
Issue ID
1312648
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 "TestScene"
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, the model
Expected result: No texture mixup
Actual result: Mixed up textures on the model
Reproducible with: 2019.4.20f1, 2020.1.0a18
Not reproducible with: 2020.1.0a19, 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
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a19