Search Issue Tracker
Fixed
Votes
0
Found in
5.4.1f1
Issue ID
842163
Regression
No
WebGL: UnityProgress.js SetProgress is not called during decompression
On WebGL build, SetProgress function is not called when decompressing compressed files in Release directory. Instead, SetProgress gets called many times after decompression is done.
Reproduction steps:
1. Create new project
2. Set WebGL template as "default" in player settings
3. Build project as WebGL build
4. Run the index.html file
Expected result: loading bar moves smoothly from start to end
Actual result: loading bar jumps only once while loading.
This happens because SetProgress is called once before files decompression and many times on the same frame after decompression.
Tested on: Unity 5.4.1f1, 5.3.3f1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment