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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment