NVIDIA GeForce 591.44 WHQL Driver

[Astyanax]

@Exostenza

Proper SDK and system software development patterns do not assume that it is mandatory to recompile a software with each new SDK version release. Software compiled with any previous SDK version is expected to work with future API updates with properly maintained backward compatibility.

Oh, but they aren't beholden to retaining deprecated function that no longer has adequate QC either, and that expectation is not realistic.

ABI breakage is not uncommon, it's undesirable and preferably avoided but happens all the time.

There are intel quicksync features, as well as AMD Media SDK deprecation that have seen encoder updates made mandatory over the years, do these get a pass because their software teams are smaller and generally accepted as less capable(That free pass mantra)

The VD team is getting scorn because they lied in their change notes about the source of the problem, citing it as a bug instead of their willful ignorance of an upcoming, not at all secretive change to the upcoming driver.

The NVIDIA Video Codec SDK is working towards updates regarding preset support. In this update support for older presets will be removed.


Background:

• Video Codec SDK introduced new presets (p1-p7) and RC modes for H264 and HEVC in Video Codec SDK 10.0 in June 2020. This was done to simplify the usage of NVENC presets.
• Older presets and RC modes are currently supported in four SDK versions (10.0, 11.0, 11.1, 12.0).
• The older presets and RC modes support only HEVC and H.264. ‌AV1 or new features such as split encode, encode quality improvements done post v10.0 are not supported.
• In SDK 12.1, the older presets and RC modes were removed from the Video SDK C header.
• Video Codec SDK supports backward compatibility. Applications compiled with SDK versions < 10.0 using older presets and older RC modes are supported in the driver.

Future steps:

• The plan is to remove ‌driver support in R550 (Q1’24). Therefore, all applications compiled with older presets/RC modes will stop working if upgraded to R550 drivers.
• The R545 will be the last driver release which will support the older presets and RC modes. The R545 release notes will have the final warning included.

Migration guide:

• NVIDIA has provided a migration guide (NVENC Preset Migration Guide - NVIDIA Docs) to enable a seamless transition to the new NVENC API preset architecture.
• Please refer to the link below for details regarding HEVC, H.264 migration tables.

This email went out to all registered users of the nvidia media sdk, and it was pushed out to r590 after consultation with affected software vendors.

VD are not in the right here.

 

[Astyanax]

In don't know if it's just this driver, but yesterday I did try Black Flag and with using RTSS for framerate info I couldn't get it full super wide res. Just a small 4:3 / 16:9 box in the middle of the screen. I turned off RTSS completely, also the global profile to none detection, and suddenly I've got the full super wide res game.

I know it's an old game, but I was just surprised it does support the full resolution in all its glory.

5120x1440 Is what I'm talking about btw. And PhysX does work in that game, in Mirrors Edge I couldn't get it to work..

Mirrors edge is broken by the legacy installer if it is run after the driver is installed, or the standalone physx installer is used.

Run the legacy pack before anything else, then the driver installer / standalone installer.

 

[spajdr]

Man I was about to post the same.
My RTX 5090 in Steel Nomad, same settings and undervolt, gives me about 400 points(2.5%) less.

Here is the comparison 581.80 581.94 and 591.44 : https://www.3dmark.com/compare/sn/10320111/sn/9841928/sn/10007837

I can't confirm, my score is exactly same as before (-+ 25 points)

 

[mrrulez911]

Is there a config file you can edit? I had to do this for FEAR and a couple of older games.

You mean for Mirrors?

Mirrors edge is broken by the legacy installer if it is run after the driver is installed, or the standalone physx installer is used.

Run the legacy pack before anything else, then the driver installer / standalone installer.

Ehm, I only have 1 version which is the one that I installed via my Game Pass Ultimate, EA app. Don't see anything about a legacy version/installer..

 

[Cave Waverider]

You mean for Mirrors?

Ehm, I only have 1 version which is the one that I installed via my Game Pass Ultimate, EA app. Don't see anything about a legacy version/installer..

I've installed the EA Play version from the EA App to test PhysX on the 5090 and it works fine on this one so it should work for you as well as well, unless GamePass installs it's own thing instead of the EA Play version.

 

[Astyanax]

Ehm, I only have 1 version which is the one that I installed via my Game Pass Ultimate, EA app. Don't see anything about a legacy version/installer..

Install this first

https://www.nvidia.com/en-us/drivers/physx/physx-9-13-0604-legacy-driver/

then install this

https://www.nvidia.com/en-us/drivers/physx/physx-9-23-1019-driver/

not in the opposite order, as the legacy installer deletes the physxdevice file for some reason.

 

[Astyanax]

I can't confirm, my score is exactly same as before (-+ 25 points)

benchmarking during changed seasonal ambients be like.....

 

[Archvile82]

Mirrors edge is broken by the legacy installer if it is run after the driver is installed, or the standalone physx installer is used.

Run the legacy pack before anything else, then the driver installer / standalone installer.

Regarding another game with physx, playing cryostasis on my 4090 the game will lock up or crash with physx enabled. Is this poor implementation or just old software being unreliable?

Its fine with physx disabled.

 

[Astyanax]

Regarding another game with physx, playing cryostasis on my 4090 the game will lock up or crash with physx enabled. Is this poor implementation or just old software being unreliable?

Its fine with physx disabled.

cryostasis has been tested to run fine in the reddit tests.

 

[pegasus1]

You mean for Mirrors?

For resolution, adding a custom resolution into the config file.

 

[szpunk]

NOOOOOO!!!

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\nvlddmkm\NVTray]
"ShowlnSedona"=dword:00000000
"StartOnLogin"=dword:00000000

 

[mrrulez911]

For resolution, adding a custom resolution into the config file.

The resolution did work for Mirrors, just the fov is a bit weird. For Black Flag I had the thing with the resolution in combination with RTSS overlay. I'm gonna try the PhysX thing to get it working. Thnx @Astyanax

 

[caleb59]

If clean installing the drivers doesn't work, then something else must be corrupting it. It could be OS or hardware related.

Run these commands in elevated cmd prompt in order for Windows:

dism /online /cleanup-image /restorehealth
sfc /scannow

From my experience, unstable RAM can also cause the drivers to become corrupted so make sure your memory is stable, especially if it's overclocked or tweaked.

It was one time incident for now and my PC is overall perfectly stable.

 

[Astyanax]

It was one time incident for now and my PC is overall perfectly stable.

perfectly stable is a myth.

 

[ValSidalv21]

As with GPU Tweak III few day ago, now Amoury Crate also received update that fixed compatibility with this new driver. Everything works as intended again.

 

[janos666]

perfectly stable is a myth.

Undetected/uncorrected ECC errors are also very extremely rare.

 

[Spider-Vice]

in Mirrors Edge I couldn't get it to work.

Did you delete the PhysX dll files from the game binary directory so it uses the system ones instead of the old DLL's the game ships with? This is what makes PhysX not work on modern machines in ME 2008.

Works on my 5070 Ti if I do that.

 

[mbk1969]

My two cents about NVENC issue:

NVIDIA gave a finger by changing NVENC API - no matter if they warned about it or not.
Now all developers who used older API should decide whether to support two versions of their software or not - for all users who can`t install newer drivers and for all other users who can install newer drivers.

Introduce new version of API leaving older one intact - just do not spend time with support of older one - ideal solution for all users of NVENC API. But NV just does not care. And I will never believe that NV can`t afford coexistence of two versions of API.

 

[Marco123]

As with GPU Tweak III few day ago, now Amoury Crate also received update that fixed compatibility with this new driver. Everything works as intended again.

Everything works, there were problems recently.

 

[Astyanax]

Did you delete the PhysX dll files from the game binary directory so it uses the system ones instead of the old DLL's the game ships with? This is what makes PhysX not work on modern machines in ME 2008.

Works on my 5070 Ti if I do that.

This is unnecessary, i disproved the need to a month or so ago.

Nvidia long ago fixed whatever was being an issue that caused the physxloader not to forward onto and reload with the system newer version