Search Issue Tracker
Fixed in 1.1.10
Votes
1
Found in [Package]
1.1.4
Issue ID
1164325
Regression
No
[Addressables] Default Unity Shaders special bundle always uses LZMA compression and is hence unusable for Web builds
How to reproduce:
1. Open the attached project ("case_1164325-UnityAddressableTest.zip")
2. Build Player Content
3. Build for WebGL (in "build" folder)
4. Upload both the Addressable bundles and the WebGL build to a web server
5. Run the build
Expected results: A house loads from the asset bundle
Actual results: House does not load from the asset bundle; errors in the web-browser
Reproducible with: 2018.4.3f1, 2019.1.8f1, 2019.2.0b7, 2019.3.0a7
Reproducible with package versions: 0.8.6, 1.1.4
Note
A possible workaround is setting the BundleCompression in the constructor of AddressableAssetsBundleBuildParameters.cs to set BundleCompression = BuildCompression.LZ4, as stated in the forums: https://forum.unity.com/threads/webgl-and-addressable-scenes.569353/
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 (fix version 1.1.10):
Now handling which compression is being done at runtime. WebGL should be detected which should make it LZ4.