NVIDIA PhysX
About NVIDIA PhysX
Most people meet this software the same way. A game refuses to start, mentions a missing component, and installing it makes the problem go away. NVIDIA PhysX is that component, and understanding what it is prevents a set of misunderstandings that have followed it for years.
NVIDIA PhysX is a physics engine, meaning the code working out how objects in a game move, collide, fall over and break. A game built with it needs the matching runtime present on your machine, which is what you are installing.
The important consequence comes first. This is a dependency rather than an improvement. Installing it on a machine where nothing has asked for it changes precisely nothing, adds no performance and improves no game, because nothing will call it.
What the engine actually does
NVIDIA PhysX exists to replace animation with simulation. Rather than an artist deciding how a crate falls, the engine works it out from mass, shape, friction, whatever hit it, which means the crate falls differently every time.
It covers rigid bodies and their collisions, joints connecting objects, cloth that drapes and tears, fluid and particle behaviour, then the destruction of structures into pieces that then behave as objects themselves.
That last one is where the effect is most visible. A wall that shatters into fragments which bounce and settle realistically is doing considerably more work than a wall playing a pre-made animation of shattering.
It is a dependency, not an upgrade
Installing NVIDIA PhysX when nothing has asked is the most common wasted click in this category. A game needing it will say so, and a game that does not will never call it however carefully it is installed.
That also means it cannot be blamed for anything. A machine running badly is not running badly because this is missing, and adding it will not change a frame rate.
The misunderstanding about graphics cards
Here is the belief worth correcting, because it is nearly universal and it is wrong.
NVIDIA PhysX does not require a particular graphics card and mostly does not use one. The overwhelming majority of physics calculated by this engine runs on the processor, across every platform it has been used on, including consoles carrying hardware from entirely different manufacturers.
Graphics acceleration applied to a specific set of optional effects, meaning dense particle systems, cloth, fluid, in a limited number of titles that chose to implement them. Those effects were extras that could be switched off, and the game ran perfectly well without them.
So a machine with a card from another manufacturer runs games built on this engine normally. Confirming what card is actually present takes seconds with GPU-Z, which also reports whether the driver stack supporting these features is installed at all.
The problem with older games on newer cards
This part is very current and catches people out. The newest card generations dropped support for the older thirty-two bit implementation of the accelerated effects.
The consequence is specific. Games built as thirty-two bit applications, from the years when those effects were promoted heavily, can no longer run them on the graphics card. NVIDIA PhysX effects either disappear or fall back to the processor, and the processor doing work designed for thousands of parallel units produces frame rates far worse than the game ever had.
Anybody replaying an older title known for elaborate particle effects and finding it stuttering on hardware that should demolish it has met this. The workaround is switching those effects off in the game’s settings, which restores performance and loses the effect.
Establishing whether the processor or the card is the limit in such a case is exactly what a benchmark reporting where the bottleneck sits exists to answer.
It is open source now
The NVIDIA PhysX source is public, which changes things for people building games and nothing at all for people playing them.
For programmers it means the engine can be studied, modified, integrated without a licensing conversation, which matters for smaller studios and for anybody working outside games entirely, since physics simulation appears in robotics, training simulators and research.
For players it means nothing changes. The runtime is still what a game requires and still what you install when prompted.
Watching what the machine is actually doing during a demanding scene is a separate exercise, and MSI Afterburner shows processor and card load side by side, which distinguishes a physics bottleneck from a graphics one.
Conclusion
NVIDIA PhysX is one of those components that exists to be installed once and forgotten, and most of what people believe about it is incorrect. It does not need a particular graphics card, it does not improve anything on its own, and installing it when nothing has asked is a wasted click.
The one situation where it matters now is the reverse of what it was known for. Older games built around accelerated effects can run badly on current hardware because that acceleration path was retired, and the fix is switching the effects off rather than hunting for a driver. Beyond that, install it when a game asks and think about it no further.
Pros & Cons
- Provides the runtime that games built on this engine need before they will start
- Simulates rigid bodies, cloth, fluids, particles, destruction rather than animating them
- Runs on the processor, so it works regardless of which graphics card is installed
- Cross-platform, including hardware from manufacturers unrelated to the name
- Source is public, which matters for anybody building rather than playing
- Installing it is a single step and then it is never seen again
- Installing it does nothing unless a game specifically requires it
- Widely misunderstood as needing a particular graphics card, which it does not
- Accelerated effects in older titles no longer work on the newest card generations
- Falling back to the processor for those effects produces very poor frame rates
- Nothing here is configurable or useful outside the games that call it
Frequently asked questions
Only if something asks for it. Games requiring it usually install it themselves, and a manual installation is the fix when a game reports the component missing. Installing it speculatively achieves nothing.
No. Most physics calculated by this engine runs on the processor, and games using it work normally on cards from any manufacturer. Only certain optional accelerated effects ever used the graphics card, in a limited set of titles.
No. It is a dependency that games call rather than an enhancement layer. A machine with it installed and no game requiring it behaves exactly as it did before.
Because the newest card generations dropped support for the older thirty-two bit accelerated implementation. Those effects now fall back to the processor, which handles them badly, so switching them off in the game restores performance.
Rigid body movement and collisions, joints connecting objects, cloth that drapes and tears, fluid and particle behaviour, plus structures breaking into pieces that then behave as objects.