Search Issue Tracker
Fixed in 2021.2.X
Votes
2
Found in
2020.2
2020.2.0b8
2021.1
2021.2
Issue ID
1288367
Regression
No
[WebGL] Incorrect loading progress is shown in the Player when Build files are compressed using Brotli
How to reproduce:
1. Open the attached project
2. In the Publishing Settings, set the Compression Format to "Brotli" (Edit->Project Settings->Player->Publishing Settings)
3. Make a WebGL build
4. Open the built WebGL Player in a browser
5. Spam the refresh button
Expected result: Loading progress is shown iteratively
Actual result: Loading progress is not shown until it reaches 90%
Reproducible with: 2020.2.2f1, 2021.1.0b2, 2021.2.0a2
Couldn't test with: 2018.4.31f1, 2019.4.18f1 (Brotli compressed files don't have the ".br" file extension)
Notes:
- Web server should be configured to add correct encoding for *.br files
- Player loading progress with Brotli compression jumps from 0 to 90 percent
Comments (4)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
koZis
Apr 11, 2022 10:01
Hello, there is no 2021 LTS version. Can you implement this fix into 2020.x LTS? Thank You!
preislter
Apr 01, 2022 08:39
I would also like to have this fixed in 2020.
AliAlbarrak
Feb 22, 2022 05:54
We would also like to have this fixed in 2020 LTS.
Or at least provide a way to manually backport the fix
AlexWijnbeek
Feb 16, 2022 11:45
Will this be fixed in 2020.x as well, seen as that is the current LTS version?