NVIDIA Profile Inspector 2.4.0.4

You do realize as Nvidia adds features, the program needs to be modified. Are you paying for it? Have you considered asking or filing a respectful bug report?

 

working as intended.

 

Haven't downloaded yet.
But, the new low latency mode and sharpening are only a global option now?
Where as NVCP can do it per profile?
Also: How were people breaking games with ULL?

 

Since R445.75 the NVAPI does not allow either to read or write the following settings anymore. So i removed them because of errors.

Code:

GSYNC - Indicator Overlay                0x10029538
Ultra Low Latency                        0x10835000
Sharpening - Denoising Factor            0x002ED8CE
Sharpening Filter                        0x00598928
Sharpening Value                         0x002ED8CD
Optimize for Compute Performance         0x10C158AD
Ultra Low Latency CPL State              0x0005F543

 

Thanks for the App Orb it's useful, what is the CPL state about for low latency?

 

That's interesting, and kind of sucks too. It was nice to use it on a per profile basis.

What about profiles that may have the options already set before updating to the new version? Does it get ignored?

 

It still works on per profile basis in the NV panel. Though it's really a bad decision by them to deliberately lock out the Profile Inspector.

 

its locking down the ability to enable wallhacks.

 

With... sharpening? You need depth buffer access for that.

Also it's still individual via the NV control panel.

 

and nvidia sharpening does........

 

WHAT????
since when does sharpening needs the depth buffer?!?!?!?!
Theres only ONE (1) shader that uses teh depth buffer and this one is for ReShade... i think it was teh smart sharpen or filmic sharpen...

Nvidias sharpen filter, as far as i know, does NOT use teh depth buffer...

 

nvidia nvcpl sharpening isn't just a sharpen, its also a upscaler.

 

And you need depth buffer access for upscaling? That seems highly unusual.
Have any known examples of people abusing this? (With links) I'm interested to read about it.

 

of course you do. lol.

or you end up with the same issues DSR encounters with screen coordinates being off.

 

I've never heard of a need for depth buffer access to upscale a final 2D output. I have heard of needing a framebuffer for upscaling in actual hardware scalers. (Compared to line doublers)Which usually incur a frame delay or so.
None of those devices have access to a depth buffer. What depth would there be to calculate? A hardware scaler wouldn't know what pixels of what objects are closer to the camera.

Are we talking about the same things here?? I can understand upscaling internal render targets. (Like a UI pass done at a lower resolution than output. So it needs to maintain the same size and position relative on screen)
But what does a depth buffer have to do with scaling this
http://u.cubeupload.com/MrBonk/3a1NoAA.png
Into this
http://u.cubeupload.com/MrBonk/NoAAupscaled.jpg
Or sharpening? That's also something that is typically done to a final 2D image by itself.

I feel like something is being lost in translation somewhere.

 

https://www.uni-konstanz.de/mmsp/pubsys/publishedFiles/LuCoDe06.pdf maybe it's about this research? idk.

 

It simply stored the Nvidia control panel state of the low latency mode setting.

 

With the current driver Nvidia profile changes for Ansel Flags are flipped back somehow.
Is there a way close the opportunity to undo the changes after Profile Inspector was used?

Or, is there any ways to look for the whitelist? Is it stored anywhere?

 

How can I find the HEX code for the Firefox profile (present in NVCP with "show installed only" ticked) if I can't find it in Inspector by typing fire or firefox.exe?

 

by typing mozilla firefox