Mass Effect physx problem

[MatrixOguz1]

Guys, the problem is, I was having physx problem in Mass Effect 2, I installed an old driver to fix it and I solved the problem, but this time I can't enter the 3rd game, it gives the same error.

What to do to solve this nonsense?

[Iceira]

DL it from Nvidia support page as standalone DL, do note vulkan driver has take over it , and optimized with preshader cache is enable through steam option, might be the problem with newer gamers thats use vulkan as a most have installed, not sure i have seen this yet but it will happend. ( nothing prevent a game devs has this as most be installed someday VULCAN DRIVERS )

same goes with VC++ from MS support page also has new files then game old VC++ once used then that game was released, and watchout for double install in windows with same bulid but diffrent version nr. ( i have seen games work bertter then old version is uninstalled as double version.

if you are tired of old outdate VC++ version google all in one VC++ and learn how to mass fix them all. ( its same on MS page but you have to do it yourself.

just so you graps this, there has not been a game i cant startup over 20 years, i think i need a total broken game where game engine is the problem and game devs left or dont support it anymore. this dont ruleout each steam forum own fiddle with setting to fix them.

im not so sure if you dont have a install version config script issue, such is seen before.
you have to uninstall it physX then install game ( if i recall correctly game will not install because new physX was there, you might want to edit game install config file part of the after main install then thirdpart app run in silent mode.

man this is complicated, if you dont know this, and its not suppose to be this way. but i cant do anything about it this is the results over many diffrent VC++ and all the DirectX and PhysX over many years and forced old ways in scripts, so as you see game devs screw up and it ends there.

( thirdpart app ) aka. VC++ is not part of MS OS , they are game devs requirements for every game.

https://learn.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist?view=msvc-170
this is check in the OS as installed Visual Studio 2015, 2017, 2019, and 2022

watchout here its same build from 2015 to 2022+, things can effect old version that depend whatever game you install on fresh OS, so technicaly newest game will have newest file, this is the trap who said gamer know this, what if you install and old game from2015 then its not same as newest , and its here most do not get it. ( this is here where games devs lost all credit and steam lost all knowledge.
and where MS wins , they know best, game devs dont know jack and crap. and why sometime ingame things act odd. and VC++ is the issue.

dont forget this took ½ to years to learn, before you notice what happend here with game devs then MS now use same build for several years in same build 2015, 2017, 2019, and 2022

gl with it,


ps.
watchout for trap with validate steam game content, it will rerun old VC++ files through the scripts. ( now you graps the many traps with old outdate VC++ ways.

its here game devs lost credit with old VC++ then MS has newer, and i stick to my point they dont know jack and crap about update files. and this is now steam user most know better then them.