physx no longer works on 50 series cards

[megatron302]

https://www.resetera.com/threads/rtx-50-series-gpus-have-dropped-support-for-32-bit-physx-many-older-pc-games-are-impacted-mirrors-edge-borderlands-etc.1111698/

https://www.pcgamer.com/hardware/graphics-cards/nvidia-has-quietly-ended-support-for-32-bit-physx-on-its-new-rtx-50-series-so-games-like-batman-arkham-city-might-look-and-run-better-on-older-gpus/

[Funk]

Originally posted by Ba Ba Bi Bu Bu Ba ♪:

you could ask this guy on youtube, here is one video of him where he uses an 50 series card https://www.youtube.com/watch?v=_dUjUNrbHis&lc=Ugx-EoUgGJd2VqxGPf94AaABAg.AEjYKABAU6nAElI4t53xtF

Well, I tried and I think youtube removed my comment. Not gonna try again stoopid youtube comment approval system.

[Chinfu1189]

They arent gonna fix this issue for two obvious reason
PhysX is a dead tech basically in modern gaming so spending time to patch out an issue on a game over 10 years old isnt profitable for them
Second reason is Bl2 is a poorly optimized overall and you are gonna have to patch the issue yourself if you want the physX to work properly.

there should be a steam guide on how to replace the old D3D9 files with new ones that nivida provides on their website for the PhysX tech

[B]

Originally posted by Funk:

Originally posted by Ba Ba Bi Bu Bu Ba ♪:

you could ask this guy on youtube, here is one video of him where he uses an 50 series card https://www.youtube.com/watch?v=_dUjUNrbHis&lc=Ugx-EoUgGJd2VqxGPf94AaABAg.AEjYKABAU6nAElI4t53xtF

Well, I tried and I think youtube removed my comment. Not gonna try again stoopid youtube comment approval system.

did share a link in your comment? if yes that could have been the reason for the removed comment, but anyways i too hate the youtube comment pproval system, its so trash lol.

[MrEWhite]

Originally posted by Funk:

Strange, I don't have a RTX 50 series GPU but I thought I'd do some testing replacing certain DLL files with their 64 bit counterparts and renaming them from C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common into Borderlands 2\Binaries\Win32

PhysXDevice64.dll copy and rename to PhysXDevice.dll(backup old file first)
PhysXLoader64.dll copy and rename to PhysXLoader.dll(backup old file first)

Get PhysXCore64.dll from same 2.8.6.4 but 64 bit version from dllme.com, copy and rename to PhysXCore.dll(backup old file first)

https://www.dllme.com/dll/files/physxcore64/1c26757fc0906004df702aa7f6c6e845/download

I had Nvidia Physx indicator, and it switches to GPU still apparently, but is it actually using hte 64 bit version of Physx no idea. All seemed to be working with the particle and liquid effects and all.

Wish someone could test on a 50 series card to see if this works.

edit: I experimented with other files and renaming them to their x86/32 counterparts such as:

ApexFramework_x64.dll ----------> ApexFramework_x86.dll
APEX_Clothing_Legacy_x64.dll ----------> APEX_Clothing_Legacy_x86.dll
APEX_Clothing_x64.dll ----------> APEX_Clothing_x86.dll
APEX_Destructible_Legacy_x64.dll ----------> APEX_Destructible_Legacy_x86.dll
APEX_Destructible_x64.dll ----------> APEX_Destructible_x86.dll
cudart64_30_9.dll ----------> cudart32_30_9.dll
cudart64_41_22.dll ----------> cudart32_41_22.dll
PhysXCore64.dll ----------> PhysXCore.dll
These worked

PhysXCooking64.dll ----------> PhysXCooking.dll complained about having too older of drivers installed

physXExtensions64.dll ----------> physXExtensions.dll didn't launch Borderlands at all after the splash screen.

That won't work because a 32-bit app cannot use 64-bit DLLs whatsoever. Only solution in this case is to buy a previous gen card and use it as a dedicated PhysX card.

[Kobi Blade]

Originally posted by Out Of Bubblegum:

I see what is happening. The support for 32 bit applications is going away. Only 32 bit versions of PhysX will not run. Just like 32 bit Windows is gone. No more support for non Windows 11 which only has a 64 bit version.

If you want to play old games then you will need to keep an older PC around. One that will not usually connect to the internet. We can play old dos games with an emulator. Looks like there will need to be a 32 bit Windows emulator soon. I have no idea how Windows 11 will run 32 bit games. I assume they gave it some way to run them. For now. Until a future update removes that ability.

Don't think you see what is happening at all, since Windows x64 already emulates x86.

[Casurin]

Originally posted by Chinfu1189:

PhysX is a dead tech basically in modern gaming

that is just completely wrong.
PhysX is still wildely used as it forms the basis of many gameengine physics, GPU accelerated physX is as good as it had ever been, and the ONLY thing they removed is driver-support for the 32bit version which had been fully removed from the SDK 15 years ago - 2 years before BL2 was released.

Tell 2K games to no use an SDK that was ALREADY DEPRECATED when BL2 development started. Not just that, they opted to us the first SDK version with the rudamentary CPU-fallback that was never meant to be used for actually playing anything while SDK 2.0 (available long before development started) would have had multithreading - those are things that were supported on the 32bit version. And v3.0 was 64bit, significantly faster on the GPU and CPU, as well as supporting SSE.

Again - since v1.0, 15 years ago, 32bit was only for compatibility and 64bit was the standard.

Originally posted by Kobi Blade:

Don't think you see what is happening at all, since Windows x64 already emulates x86.

There is a big difference between having a compatibility layer for 32bit applications and supporting 32bit systems - the later is no longer available. You simply can not install Win11 on a 32bit system as that is just impossible.

[Kobi Blade]

Originally posted by Casurin:

Originally posted by Chinfu1189:

PhysX is a dead tech basically in modern gaming

that is just completely wrong.
PhysX is still wildely used as it forms the basis of many gameengine physics, GPU accelerated physX is as good as it had ever been, and the ONLY thing they removed is driver-support for the 32bit version which had been fully removed from the SDK 15 years ago - 2 years before BL2 was released.

Tell 2K games to no use an SDK that was ALREADY DEPRECATED when BL2 development started. Not just that, they opted to us the first SDK version with the rudamentary CPU-fallback that was never meant to be used for actually playing anything while SDK 2.0 (available long before development started) would have had multithreading - those are things that were supported on the 32bit version. And v3.0 was 64bit, significantly faster on the GPU and CPU, as well as supporting SSE.

Again - since v1.0, 15 years ago, 32bit was only for compatibility and 64bit was the standard.

Originally posted by Kobi Blade:

Don't think you see what is happening at all, since Windows x64 already emulates x86.

There is a big difference between having a compatibility layer for 32bit applications and supporting 32bit systems - the later is no longer available. You simply can not install Win11 on a 32bit system as that is just impossible.

I don't know why you decided to waste my time, there is no such thing as a 32bit system in 2025, you can install Windows 11 wherever you want.

Consumer CPUs have supported 64 bits for almost four decades now, same way they supported TPM for the last two decades.

[EricOfMelnibone]

Consumer CPUs have supported 64 bits for almost four decades now, same way they supported TPM for the last two decades.

We were still using 8-bit CPUs in 1985. Except for a few of the cool kids who had 16 bits.

Windows was built on backwards compatibility; it's why everyone used it over other operating systems. Removing support for 32-bit games means one less reason to use Windows in future.

[Kobi Blade]

Originally posted by EricOfMelnibone:

Consumer CPUs have supported 64 bits for almost four decades now, same way they supported TPM for the last two decades.

We were still using 8-bit CPUs in 1985. Except for a few of the cool kids who had 16 bits.

Windows was built on backwards compatibility; it's why everyone used it over other operating systems. Removing support for 32-bit games means one less reason to use Windows in future.

Keep in mind Microsoft is not removing anything, WoW64 is not going anywhere anytime soon, there a huge difference between support and not working.

32-bit games will stop working when hardware itself removes the instructions, is in AMD and Intel hands.

NVidia dropping the ball with PhysX won't stop the games from working, but if they had bothered to support modern CPU instructions in PhysX this wouldn't be a problem for starters (they crippled CPU performance with PhysX on purpose to sell GPUs).

[Rod]

I have fallen victim to this i play older games i never had a pc that can run bl2 the way i want i play with minimums of 120 so naturally i play older games. And my upgrade cycles now 7800x3d and a 5080.

Removing the physx from the 5080 means im screwed for games i need to play Mafia remaster series, All the Metro games and BL2 and pre sequel i think thats it... so it means either awkwardly sliding in a 2080 alongside a 5080 or looking for a single slot 3060 a minimum would be 150 just to get a card dedicated to physx. Nvidia think physx is dead but being shallow they would think that at long as people play the games it is not dead.

[Casurin]

Originally posted by Kobi Blade:

NVidia dropping the ball with PhysX won't stop the games from working, but if they had bothered to support modern CPU instructions in PhysX this wouldn't be a problem for starters (they crippled CPU performance with PhysX on purpose to sell GPUs).

They did - how about you just learn to READ?
What you are complaining that Nvidia supposedly did not do - they in fact did BEFORE BL2 started development.

Originally posted by Rod:

Nvidia think physx is dead but being shallow they would think that at long as people play the games it is not dead.

PhysX is just the most used physics-backend in the entire gaming industry and used in literally thousands of games.
It is BL2 that does not support the over 15 year old 64bit API but opted for the back then already deprecated 32bit version with the already no-longer available at the time old SDK.