Search Issue Tracker
Fixed
Fixed in 2021.3.25f1, 2022.2.18f1, 2023.1.0b14, 2023.2.0a12
Votes
0
Found in
2021.3.23f1
2022.2.9f1
2023.1.0b6
2023.2.0a4
Issue ID
UUM-29281
Regression
No
DLSS "Ultra Performance" mode performs worse than other DLSS modes
How to reproduce:
1. Open the user-attached project “hdrp_dlss_ultra_performance_bugreport”
2. Open the “OutdoorsScene” scene
3. On the “Main Camera” GameObject set DLSS Mode to “Maximum Performance”
4. Open Window → Analysis → Profiler and leave only the “Rendering” field enabled under the “CPU Usage” field
5. Enter the Play Mode and observe the framerate in the Profiler
6. Switch DLSS Mode to “Ultra Performance”
7. Observe the framerate in the Profiler
Expected result: The framerate in “Ultra Performance” mode is higher than in “Maximum Performance” mode
Actual result: The framerate in “Ultra Performance” is significantly lower than in any other DLSS mode
Reproducible with: 2022.2.9f1, 2023.1.0b6, 2023.2.0a4
Couldn’t test with: 2020.3.45f1 (There are no DLSS options), 2021.3.20f1 (Shaders can’t be loaded)
Reproducible on: Windows 11 Pro with Nvidia GeForce RTX 3050Ti
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Editor becomes unresponsive and memory allocation errors are spammed in the Console when Generating Lightning
- Crash on BatchApplyPropertiesFromSourceAssetDB when opening a specific project
- Scene view Camera cannot be moved with WASD/QE keys when the Right Mouse Button is held down and the Mouse is not moved
- Crash when calling default interface method from virtual method with same name
- [Android] Unity does not include the ".aab" extension for an AppBundle when it is built via script with the buildPlayerOptions.locationPathName = "AppName.apk" and EditorUserBuildSettings.buildAppBundle = true
Add comment