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
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
Add comment