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.
- [URP] Exceeding the platform's supported light limit gives shadow distortion when using Deferred Rendering Path
- URP Sample Buffer Image Tile is moved when the Offset Value is changed
- Static constructor in a struct returns false when running tests with IL2CPP
- Console throws warnings and a MissingReferenceException error for XR packages when doing a clean project import
- [Linux][IL2CPP] Dedicated server crashes when calling Socket.Send
Resolution Note (fix version 2023.1.0a10):
Fixed in: 2023.1.0a10
Resolution Note (fix version 2022.2.0b10):
Fixed in: 2022.2.0b10
Resolution Note (fix version 2022.1.19f1):
Fixed in: 2022.1.19f1
Resolution Note (fix version 2021.3.13f1):
Fixed in: 2021.3.13f1
Resolution Note (2020.3.X):
2020.3 uses a version of emscripten which doesn't support the power preference attribute.