Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I like setting it to high. It changes the game a little. For instance, the drapes that hang down over openings can interfere with you until you tear them off by walking through.
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.
A second older Nvidia GPU will work as long as both of the them support installing the same driver. The reason is because you cannot install two different Nvidia drivers on the same OS. So this means you can only go so far back on your driver versions, and considering that Nvidia eventually drops support for older GPUs not updating drivers slowly you will not be able to use your fancy new Nvidia GPU with older Nvidia GPU for the purpose of 32 bit Physx.
Currently the most recent driver version for the 50 series supports GPUs from 40 series all the way down the the 700 and Titan series.
So if I wanted to use my GTX 670 with a 5090 for example it's not going to work.
Also, been wanting to move to laptops since last year waiting for a good deal, now looks like I will have to stick to a 40 series if I want to use GPU accelerated Physx, because obviously you can't add a second GPU to laptops......unless you can use those expensive hacky/buggy/most of the time not working eGPUs or NVME to PCIE adaptops.
We really need the community to make a translation layer for Physx or fix the older Physx code. Isn't the older Physx open source?
edit: Better yet would be updating the Physx version of this to version 3 which supported multithreading and SSE instructtions instead of x87 on CPUs, which should allow better performance for everyone enabling it on Medium and HIgh.
I mean cmon, it's about time everybody can experience Physx on this game as even today's modern CPUs tank performance on this gimped version of Physx which is single threaded and using x87 instructions.
https://youtu.be/mJGf0-tGaf4 Nope look at how a 7700X performs in Batman Arkham Asylum which uses the same Physx version. A newer CPU will never make this game work well when using CPU Physx 2.x.x whatever because it's single threaded x87 code.
edit: here 9800x3D have a laugh https://youtu.be/_dUjUNrbHis
I highly doubt that WoW64 subsystem(compatibility layer for x86/32 bit apps) from Windows will be removed any time soon.
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.
it is also funny to see just how many people constantly, on every game, complained about PhysX and now they cry about the support for the old 32bit version being dropped. If memory serves me correctly the last release with such an old version is now over 10 years ago.
CUDA version 3 was release 2010 - that was the switch to 64bit only. BL2 was released in 2012 and received updates till 2014. And there are hundreds of problems and bugs they never fixed, they didn't want to pay for the Linux/mac ports but Mac DID get a 64 bit upgrade eventually. And even if not going 64bit - CUDA 1 was the only major version where the fallback was singlethreaded x87. CUDA2 still was 32bit and had a far more performant CPU fallback.
I think it is understandable that 15 years after they switched to 64bit they finally drop support on their newest hardware. Not nice and i would like this not to be the case, but understandable.
Also there have been and still are some projects that worked on emulating or transcoding CUDA, even just supporting it natively. Cause Yes - everybody is free to support CUDA on their hardware. Intel and AMD both would be allowed to implement it (heck, they are the sponsors for one of the software-projects.
They dropped 32bit support.. 20 !!!! years after 64bit became the norm for desktop CPUs... yeah you might just as well complain that Microsoft nolonger ships 16bit support out of the box.