Search Issue Tracker
Third Party Issue
Third Party Issue in 2023.3.X
Votes
0
Found in
2021.3.32f1
2022.3.13f1
2023.1.20f1
2023.2.0f1
2023.3.0a14
Issue ID
UUM-56516
Regression
No
RTX card is not detected when running the editor with the -load-renderdoc command line argument
How to reproduce:
1. Open the user-attached project “HDRP-DLSS-RenderDoc” with the command line argument “-load-renderdoc”
2. Open the “HDRP High Fidelity” Asset
3. In the Inspector, observe the Rendering → Dynamic resolution
Expected result: DLSS can be enabled
Actual result: DLSS can’t be enabled because Unity is not detecting DLSS-capable GPU
Reproducible with: 2021.3.32f1, 2022.3.13f1, 2023.1.20f1, 2023.2.0f1, 2023.3.0a14
Reproducible on: Windows 11 Pro
Note: Ray-tracing can’t be enabled too
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
- [Android][IL2CPP][ARMv7] Struct field value corrupts when invoking a generic delegate with a large struct by value
- Highlights persist throughout Options Panels in the Rendering Debugger Window
- Typing numbers in Matrix node’s numeric fields stretches Node
- Streaming is misspelled as "Steaming" in "Enable GPU Streaming" and "Enable Disk Streaming" tooltpis
- "IndexOutOfRangeException" thrown when moving caret left at start of TMP Input Field with rich text
Resolution Note:
DLSS is proprietary Nvidia technology. Renderdoc does not support DLSS. If frame debugging is required with DLSS then Nvidia Nsight should be used.
Resolution Note (2023.3.X):
DLSS is proprietary Nvidia technology. Renderdoc does not support DLSS. If frame debugging is required with DLSS then Nvidia Nsight should be used.