Search Issue Tracker
Fixed in 2021.3.13f1
Fixed in 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X, 2023.1.0a10
Votes
0
Found in
2023.1.0a1
Issue ID
UUM-7962
Regression
No
[WebGL] context powerPreference should default to high-performance
Web browsers moved to change the default WebGL powerPreference from high-performance to low-power (e.g. in Chrome 80). This caused a regression in performance for Unity WebGL content on laptops with two GPUs (a low-power integrated GPU and a dedicated GPU) where now the low-power GPU is selected.
We need to default to selecting the high-power powerPreference, but add an option to the WebGL Player Settings to allow the user to choose a different setting (default or low-power) if their content is more suited.
See:
https://forum.unity.com/threads/force-the-use-of-dedicated-gpu.1115851/
https://github.com/emscripten-core/emscripten/issues/10000
https://www.khronos.org/registry/webgl/specs/latest/1.0/#5.2.1
Users can currently work around this by setting the config['webglContextAttributes'] when calling createUnityInstance from their WebGL template, and we should still respect that setting if set.
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
- [Linux] Mouse cursor gets stuck at the edge of the screen when trying to pan in the Scene view
- Docked Multiplayer Play Mode window disappears when switching back to a saved Editor layout
- Audio files fail to be imported when the file path is 260 characters or longer
- Error SGICE002 is wrongly shown when more than one argument is passed into GetComponentRW()
- Crash on MeshRenderer::DispatchUpdate when disabling the second Mesh Renderer on a GameObject
Resolution Note (fix version 2023.1):
Fixed in: 2023.1.0a10
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0b10
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.19f1
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.13f1