I can only wonder how much data communication is required between the CPU and this physics engine, but I would guess its pretty huge, meaning, its not all that usefull if you can't bring it closer to the CPU or eventually integrate it.
Well, with a standard PCI Express or PCI interface it's going to have to be a pretty low bandwidth system. You're right though, integrating it is the better idea. You're wrong about integrating it with the CPU though. The much more effective point of integration in this case is with the GPU. (So for that matter would be the integration of the sound card into the GPU for handling 3D sound effects.)
I've been dreaming of the day when some bright spark finally integrates the 3D graphics, sound, and physics engine into one core API for years. I mean imagine how much data is needed to produce the graphics, sound, and physics seperately that could be saved by integrating these into one device.
Well ... perhaps two devices, with one interface. I could easily see an SLI-type setup with a graphics card and a physically seperate physics/sound card.
IMHO anything short of that level of integration is wasteful. Not that this goofy PhysX chip wouldn't be a step forward, but really I'd rather wait two years for a fully integrated Game PU (name chosen for its acronym equivalent to Graphics PU) than one year for a completely seperated Physics PU.
Of course the graphics and coding would likely be a lot different under the fully integrated Game PU than it is now, because you'd be more concerned with higher-order object associations than with direct verticies and normals being drawn. But updating the GPU programming world to the 21st Century is another topic all together. **LOL**
<pre>Antec Sonata 2x120mm
P4C 2.6
Asus P4P800Dlx
2x512MB CorsairXMS3200C2
Leadtek A6600GT TDH
RAID1 2xHitachi 60GB
BENQ 16X DVD+/-RW
Altec Lansing 251
NEC FE990 19"CRT</pre><p>