- May 16, 2008
- 3,180
- 0
- 0
Are you a game developer who also works with physx?It also drops to slideshow FPS in single player with PhysX on high in certain locations, so what's your point?
Wrong. You've shown that you don't understand the relationship between CPUs and GPUs in games. Just because PhysX uses the GPU for calculations, doesn't mean the CPU has no part to play.
The CPU issues draw calls for everything that is rendered by the GPU on the screen. With PhysX enabled, the amount of draw calls is increased big time due to all of the added particles and effects.
The engine lacking multithreaded capabilities loads all of the draw calls on only ONE core, which isn't enough for PhysX on medium or high. So the CPU gets taxed to the limit (up to 100% usage on two cores on my 4.5ghz 3930K) and eventually gets bogged down when the draw call limitation is exceeded, which causes the GPUs to stop being fed data and the frame rate to plummet.
It does demonstrate it, you just don't understand it
Gearbox should never have used DX9 for this game. DX9 uses a single core for rendering if I'm not mistaken, which destroys performance in a big game like BL2 with massive draw distances and detail.
Until then I don't take an avid physx/nv fans word for why physx doesn't work in bl2.
I understand the CPU and gpu are working in sync etc. but your explanation falls short when the other games are at 100% load and don't falter (as bad afaik).