I thiiiink older DLSS versions will just fall back on whatever the game sets as the default? Not too sure.
I've only some some small visual tests of E in HFW during night (lol) so can't really say much about it's quality. Seems like a solid preset for SR though.
Yeah well kinda already was the case previously. I was impressed by the details DLSS P with preset E is able to resolve though.
Games pre-3.1 didn't really have any preset control and whatever they are defaulting to in these versions is usually DLSS side choice based on app id.
So E is an updated version of D, and there's a new "unused" preset G now. Makes you wonder why use a new preset if it's just an update of D...
Preset E seems more a new thing than just an update for D: it looks like C but it's stable like F, which is exactly what DLSS needed for SR.
Oh thank God, alpha support...
All game graphics are blended prior to becoming front buffer which you see which is why there is no need to handle alpha channel usually or even have it in the front buffer color format (RGB10A2 leaves just 2 bits for alpha values for example).
That's just a badly implemented upscaling of this screen in particular.
Anything which can be overlaid on top of the rendered image can be native res. The background and the model in the example above should just provide the data needed for the upscaler to work - which it apparently does not.
You don't have to add manual frame limiters anymore.
I probably worded this badly but my issue is with things like idle games or wallpaper engine, having them run at 144fps makes no sense and just puts stress on the gpu/consumes power.
Reaching 140fps doesn't automatically mean the GPU will be at 100% usage and max Watts consumption.
Yeah. P40L0 has different kind of guides at Patreon, so some of them are behind a paywall.
I think I may have figured it out. I monitored the GPU usage via the windows task manager which apparently doesnt take the GPU clock into account. So it sometimes looks like the GPU is under heavy load even though its downclocked. Monitoring the usage and GPU clock with GPU-Z showed that while load % seems to increase, the GPU clock stays almost the same so the actual difference isnt that big.
There is no real difference for SDR content (and even in HDR you won't see much of it really but at least going with less than 10 bits puts it out of spec).
wiki.special-k.info
Always staying in HDR @ 10-bit (and then setup SDR within HDR through Win11) solves it, even when using VRR and even for Borderless window along with old Fullscreen.
This sounds potentially terrible so I definitely don't want to have these issues.It's a thing which allows low latency frame presentation which support all fullscreen features basically.Presentation Model (D3D11-12)
For when you wonder why things are the way they are...
Two main advantages it provides in modern Win11 are:
1. Low latency frame presentation inside a window (bypassing DWM s/w composition). Note that fullscreen borderless is less affected by that since modern Win11 have a DWM bypass mode even without MPO support.
2. Support for multiple overlays which is used by Windows OSDs (Game Bar, system notifications, volume bar, etc) which should either lessen or completely remove syncing issues when such OSD objects appear above a VRR'ed game window. Without MPOs such OSD elements appearing lead to DWM intervention which essentially disable VRR and force vsynced high latency composition.
Basically I would probably prefer MPO support over pointless 10 bit SDR color. But it depends on your typical gaming scenarios.
If this is how it works, it's really not THAT bad but I suppose it would get annoying down the line if you're having issues with a game using HDR and potentially forgetting this could be causing it.
Interesting. I'm not actually using my C9 with this but my QD-OLED MSI 32URX, but I imagine it would be the same thing. Funny enough I have my SDR slider set to 40 within my calibrated W11 profile. You're saying dropping that down to 35 would essentially be the same thing as using SDR fully with 10bit activated?
Yeah, same thing.
MPO doesn't work with 10 bit SDR mode on Nvidia at all, doesn't matter what you toggle.
Now If I do this, what about playing games that don't support HDR? I'd have to turn Auto HDR off right?
Yeah, in that case I won't do it for sure.
AutoHDR will just work as usual for supported games (if you use it, but I vastly prefer NVIDIA RTX HDR over it + this will work with almost any SDR game)
Gotcha. So just to be clear Auto HDR is really just for SDR titles with no HDR that support it and RTX HDR can actually be used for both compatible HDR and non native HDR titles that support Auto HDR?
No.
I see, thank you for the information. For the RTX HDR to work what exactly is the requirement, dx11/12 titles or just anything?
Officially it will work for all DX9-12 titles but it actually works on almost anything (DX8, OpenGL, Vulkan) with some adjustments in Win11 and NVCP.
I would leave it at default 1.000 nits as 460 nits it's really not HDR, so the monitor for sure has some tone mapping going on in accepting standard HDR10 1.000 nits.
leave it at 1.000 even with the new QD-OLEDs using HDR 400? I do have a 1000 mode but the PQ tacking on these 2024 QD-OLEDs using it aren't great and 400 in most situations look brighter, for now anyway.
I would use the standard 1.000 on monitors unless those have a (properly working) HGIG mode which will turn off any tone mapping altogether, so the nits you put there exactly match what the display will output (to the max it's actually capable of).
Thanks for this tip. While I can't tell the difference on a VRR display, this really improved my moonlight AV1 streaming. With the old settings I was getting 15 MS spikes running 1080p 120fps, now it runs flawlessly at 1440p 120 fps with 4 ms decoder lag. I'm also no longer getting camera judder at all even with mouse and keyboard.
