Search Issue Tracker
Third Party Issue
Votes
0
Found in
2020.3
2021.2
2021.2.11f1
2022.1
2022.2
Issue ID
1403426
Regression
No
WebGL Player builds are running extremely slow when using WebCam Textures
How to reproduce:
1. Open the attached project "WebGLPerformanceTest.zip"
2. Open the "demoScene_free" Scene
3. Switch to the WebGL platform (File > Build Settings...)
4. Build And Run
Expected result: The Player runs on 60fps
Actual result: The Player runs on 2fps
Reproducible with: 2020.3.31f1, 2021.2.15f1, 2022.1.0b11, 2022.2.0a8
Could not test with: 2019.4.36f1 - due to errors in the Console window
Tested with: Safari Version 15.3 (17612.4.9.1.8)
Notes:
- Not reproducible on Google Chrome
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2022.2.X):
Resolving this ticket as a "Third Party Issue" since there is a big performance problem in the Metal backend for WebGL of Safari. We are currently working with Google to make sure they address the issue with their Metal implementation.