Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
4.0
Issue ID
1087702
Regression
Yes
[Addressables] Materials are unlinked from GameObject in packed mode
Steps to reproduce:
1. Open user attached project
2. Play the scene and press "Q"
3. Observe that materials are not displayed
4. Stop playmode and choose Virtual or Fast mode
5. Play the scene, press "Q" and observe that materials are displayed now
Expected result: Materials should stay linked with GameObjects in Packed Mode
Reproduced in: 2019.1.0a3, 2018.3.0b5, 2018.3.0a1
No repro in: 2018.2.11f1
Regression since: 2018.3.0a1
-
adamgolden
Feb 22, 2020 21:39
I had the same issue with Packed Play mode. Here's the easiest workaround ever:
..while this is broken..
Material m = new Material(myShader);
..this isn't..
Material m = new Material(Shader.Find(myShader.name));
-
Cleverlie
Jan 17, 2019 15:43
this is happening to me even when the build target is StandaloneWindows64, and I'm running the editor in windows 64bit. even a built player shows the models with pink shaders.
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Resolution Note:
This is due to building incompatible asset bundles (i.e. android bundles running on a windows machine). This will never work if shaders are included in the bundles since they are platform specific.