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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment