Yeah as others mentioned this was reported early on in SU10 beta for a lot of people.
I have see it mentioned somewhere else that some people impacted by this had done a registry edit previously to try and improve performance in the Sim. Obviously no idea if that is the case here but some state they fixed it by restoring their backed up registry. Take with pinch of salt as it worked fine for me always in the Beta but then I never did a registry hack so who knows.
OK someone I know tried it doing this. Before doing anything back up your registry I cant stress that enough. This is what they said.
I had both registry tweaks active. Reverted only the one, where you add “TRDLevel=0” in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers (Key TDRLevel deleted) and now it works.
Absense of this is the default and these keys must created manually.
Did I understand correct, that reverting of the manually settings for “Timeout of Driver Recovery” fixed your problem that you not get the DLSS option ?
That would be an intressting side effect of that parameter and if that was the reason, it is may be the major cause of user reports. A lot of users fiddle around this parameter.
The default of these parameter is “3” ( recovery on" ) , which should be same as “not present parameter”.
EDIT:
ah, I see now… this is also mentioned within an existing Bug and users confirm same solution ( revert user tweaks ):
( so, sounds for me not like a bug, just a user tweak with side effects )
When users “fiddle around” with registry parameters to fix something, they unknowingly assume the responsibility of troubleshooting future problems caused by the “fiddling”. If the Registry change “fixed” their current problem, then the fix needs to be communicated to MS Windows, Asobo, NVIDIA, AMD, etc. so the fix is incorporated into future patches/updates. This then shifts the troubleshooting responsibility back to the vendor/developer.
The alternative is for users when encountering a problem is to first remove any of their “fiddling” even if it seems unrelated to the current problems.
These TDRLevel and in special disabling the Recovery, was never a solution. I often warned the users about that ( e.g. CTD in DX11 mode without FPS Cap - #47 by MichaMMA ). The newest post within the former linked bug-topic also describe that : the user got still CTD , but not revered the TDRLevel setting.
For me intressting is the side-effect… I also had not expected that disabling the recovery have an effect on DLSS
Some users see that popup about “gpu problem happend…” . May be that comes from a different “fiddeling” too
Mine is clearer in TAA. Tried all the different settings under the DLSS, none did better at the clarity of instruments, seemed to be ok, just not as crisp.
Well you only need to do this is you ever edited the registry previously so by the sounds of it you didnt if you are unsure? Or did you? Just checking that is all mate
