Hope you weren’t planning to play PhysX games on Nvidia’s new 50-series GPUs
-
CPU accelerated physics were severeley dumbed down to make PhysX look better and there are several high profile games on that list that will forever have physics stupidified because of corporate BS back then that affects them now.
-
That list has some incredibly popular games on it... Hardly rage bait if you'll get worse performance in the greatest AC game to have come out.
-
PhysX has just been a CUDA application for a long time, there's not been a dedicated PPU on any card in a very long time
-
I'm too poor to worry about this. My wife bought eggs recently
-
My understanding is 32-bit PhysX games are broken.
64-bit compiled games are fine.
-
Yeah you are going to get "horrible" 100fps lows in AC4 and borderlands 2 whit physx enabled.
How many of the two dozen games affected were already capped engine wise to 60 or 30fps because of console ports? If you can afford 5000-series then you probably also have a processor that can more than enough offset the GPUs workload. AC4 for example came out when gtx 980 was bleeding edge. It's just what AMD GPU users have been living with for decades, and not even really noticing. Even my three gen old low tier AMD laptop with integrated graphics can eek out 30+ fps in mirrors edge with physX on and all graphics maxed. I'm sure all of these games will be fine.
-
I'm so sorry you needed eggs
-
I played Mirrors Edge a bit. The only part of physx in the game that I remember, as i didn't finish it, was that there were some random curtains that would blow in the wind and weren't placed anywhere where they would actually matter
-
It's too bad the CPU path for PhysX is crappy. It would be a good use of the many cores/threads we have available to us these days.
-
The only part of physx in that game that I remember is that it used to cause massive performance and stability issues.
-
Mirror's Edge actually had a place with tons of broken glass falling down, where the framerate would drop into the single digits if it used CPU PhysX. I remember that because it shipped with an outdated PhysX library that would run on the CPU even though I had an Nvidia GPU, so I had to delete the game's PhysX library to force it to use the version from the graphics driver, in order to get it to playable performance. If you didn't have an Nvidia driver you would need to disable PhysX for that segment to be playable.
-
I don't think there has ever been a PPU on the GPU. It did originally run on PPU cards by Ageia, but AFAIK PhysX on GPU:s used CUDA GPGPU right from the start.
-
I actually wasn't, no, planning to ride this 30 series out for about a decade.
-
No, the card is broken. Only suitable for newer games.
-
That's misleading in the other direction, though, as PhysX is really two things, a regular boring CPU-side physics library (just like Havok, Jolt and Bullet), and the GPU-accelerated physics library which only does a few things, but does them faster. Most things that use PhysX just use the CPU-side part and won't notice or care if the GPU changes. A few things use the GPU-accelerated part, but the overwhelming majority of those use it for optional extra features that only work on Nvidia cards, and instead of running the same effects on the CPU if there's no Nvidia card available, they just skip them, so it's not the end of the world to leave them disabled on the 5000-series.
-
Ah, the good old days
having to manually fix drivers but with limited help from the internet -
My wife had to start laying her own.
-
The enshittification of green has begun
-
DECEARING EGG
