Search Issue Tracker
By Design
Votes
0
Found in
2021.3
2022.1
2022.2
2022.2.0a10
Issue ID
1419872
Regression
No
HDAdditionalCameraData.deepLearningSuperSamplingQuality field values are out of order compared to the Inspector field
How to reproduce:
1. Open the OutdoorsScene in the attached project and enter Play mode
2. In the Game View using the Drop-down menu, select the Index 1 option which should be the "Balanced" DLSS Quality preset
3. In the Inspector window, observe that the custom DLSS quality Mode field for the Main Camera matches the Selected preset in the Game view
4. In the Game View using the Drop-down menu, select the Index 2 option which should be the "Maximum Performance" DLSS Quality preset
5. Observe the custom DLSS quality Mode field in the Inspector window again
Expected results: DLSS quality presets match between in Game UI and the Inspector window
Actual results: DLSS quality presets do not match
Testing note - DLSS modes are ordered in terms of Quality in the descending order for the Inspector field. .deepLearningSuperSamplingQuality appears to have mixed Maximum Performance and Maximum Quality index numbers. Index 0 in the Inspector window is used for "Maximum Quality" preset, while in the API call it is used for "Maximum Performance" (And vice versa)
Repropducible with: 2021.3.1f1(12.1.6), 2022.1.0f1(13.1.7), 2022.2.0a10(14.0.2)
Could not test with: 2019.4.38f1, 2020.3.29f1 (.deepLearningSuperSamplingQuality method was not available in HDRP versions prior to 12.x)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Resolution Note:
This takes the assumption that the value of the quality setting enum corresponds to the position in the Inspector UI. This is incorrect. We intentionally keep them decoupled so they could be reordered arbitrarily.