Search Issue Tracker
Fixed in 2021.3.13f1, 2022.1.19f1, 2022.2.0b10, 2023.1.0a10
Unknown (hidden) 2020.3.X
[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.
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.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- SHADERPASS has incorrect value when using Shader Graph for Built-In target
- [VFX] Gizmo still incorrectly rendered for a hidden property
- Nested object label indentation is incorrect when using the UI Toolkit Inspector
- Crash on tlsf_free when UI Elements are moved to the side by scrolling
- Crash on AudioUtil_CUSTOM_HasAudioCallback when entering PlayMode while the GameObject's Properties Inspector window is in Debug mode