Search Issue Tracker
By Design
Votes
1
Found in
4.2.0f4
Issue ID
563165
Regression
No
AssetBundles with shaders do not work in editor
Targeting Android, Unity Pro's AssetBundles-with-Shaders feature works great on-device (tested on different phones) but totally fails in Unity Editor's Game View, making any sane prototyping/testing of such AssetBundles essentially unworkable.
Note this applies to Unity Editor started with -force-opengl. No idea if this happens in DirectX mode, since that is simply irrelevant to Unity development for mobile.
Resolution:
Once shaders are serialized for opengl es target it is impossible to load them using dx9/11 device.
As a workaround '-force-glcore' can be used on Windows to be able to emulate gles behavior
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Character spacing value is not applied when using a specific font asset
- [Android][IL2CPP] Player crashes on __memcpy_aarch64_simd+276 when invoking native code via a plugin on some ARM64 Android devices
- [Android]Resources fail to load when the AAB build contains a large Addressables Bundle
- Unity is loading internal version of SharpZipLib instead of local version
- The Context Menu items are ordered incorrectly
Add comment