Search Issue Tracker
Fixed in 2021.3.25f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 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
- 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
Add comment