Here is the reply of Nadeem Mohammad, NVIDIA’s PhysX director of product management, to AMD’s accusations:
I have been a member of the PhysX team, first with AEGIA, and then with Nvidia, and I can honestly say that since the merger with Nvidia there have been no changes to the SDK code which purposely reduces the software performance of PhysX or its use of CPU multi-cores.
Our PhysX SDK API is designed such that thread control is done explicitly by the application developer, not by the SDK functions themselves. One of the best examples is 3DMarkVantage which can use 12 threads while running in software-only PhysX. This can easily be tested by anyone with a multi-core CPU system and a PhysX-capable GeForce GPU. This level of multi-core support and programming methodology has not changed since day one. And to anticipate another ridiculous claim, it would be nonsense to say we “tuned” PhysX multi-core support for this case.
PhysX is a cross platform solution. Our SDKs and tools are available for the Wii, PS3, Xbox 360, the PC and even the iPhone through one of our partners. We continue to invest substantial resources into improving PhysX support on ALL platforms–not just for those supporting GPU acceleration.
As is par for the course, this is yet another completely unsubstantiated accusation made by an employee of one of our competitors. I am writing here to address it directly and call it for what it is, completely false. Nvidia PhysX fully supports multi-core CPUs and multithreaded applications, period. Our developer tools allow developers to design their use of PhysX in PC games to take full advantage of multi-core CPUs and to fully use the multithreaded capabilities.
In the next update of PhysX FluidMark (just after FurMark update), I’ll try to add a multi-core CPU support…
Thanks for the update on adding multi-core support.
Hopefully Bullet OpenCL physics will come out this year so we can forget about PhysX…
I am really sorry but I have never seen more than 30% CPU usage on my Core i7 in PhysX games.
Now someone must take the blame. Either the developers suck balls either the SDK. If someone has to bust his balls to make multi core support work, then they probably won’t!
How about those nvidia PhysX demos? Do they use multicore cpu support? Don’t think so….!
i cannot see any reason why Physx hasnt been ported to ati (or running alongside ati) considering its “a cross platform solution”..
physx will die soon as openCL kicks in anyway
on a side note..
physx = TWIMTBP = gimmick to sell more cards
Will I be able to run PhysX FluidMark only on CPU, because I have ATI card?
@Dmitry: actually you can already run PhysX stuff of FluidMark on CPU. If you don’t have a GeForce 8+ GPU, PhysX runs in software mode.
Where is the multi core support??? Link: http://www.youtube.com/watch?v=3V_5lWYZfls
@userx: I never said that the current FluidMark has multi-core CPU support, I said I will add it in the next update…
FluidMark PhysX use, but if it does not support multi core implementation, FluidMark will not!
Actually PhysX has an option for using a multithreaded path (I can’t remember if this option is enabled). But I think the application has also to provide some support like a real thread dedicated to PhysX engine. Currently in FluidMark, PhysX update, scene update and rendering are in the same thread. Anyway, I will look at this problem shortly…
“Our PhysX SDK API is designed such that thread control is done explicitly by the application developer, not by the SDK functions themselves.”
Pingback: [PREVIEW] Multi-Core CPU Support in PhysX Coming To PhysX FluidMark
“i cannot see any reason why Physx hasnt been ported to ati (or running alongside ati) considering its “a cross platform solution”..”
It was, by the administrator of NGOHQ. He was refused development hardware, and not long after the ATI drivers entirely disabled his physx wrapper.
Pingback: [SA] Nvidia purposefully hobbles PhysX on the CPU - Page 16 - Overclock.net - Overclocking.net
maybe what Nvidia are saying is that sure it supports multi-core on non-Nvidia systems, it’s a whole different thing to saying it uses the full potential of the multi-cores.