Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

NVidia Cripples PhysX "Open API"

Anonymous Coward writes | more than 4 years ago


An anonymous reader writes "In a foot-meet-bullet type move, NVidia is going to disable PhysX engine if you are using a display adapter other than one that came from their company. This despite the fact that you may have an NVidia card on your system specifically to do this type of processing. "For a variety of reasons some development expense, some quality assurance and some business reasons Nvidia will not support GPU accelerated PhysX with Nvidia GPUs while GPU rendering is happening on non-Nvidia GPUs." Time to say hello to Microsoft dx physics or Intel's Havok engine."

Sorry! There are no comments related to the filter you selected.

Couldn't agree more (1) (1563557) | more than 4 years ago | (#29597723)

with the submitters opening line. I've been holding off on a new workstation purchase specifically to skip geforce 7x00, 8x00, 9x00, and gts x00 models and jump to a Larrabee based GPGPU. Also skipped dual core, core2duo, and core2quad to save for a nice Nehalem based CPU. Things are starting to look really fucking interesting in the high-end workstation markets...
Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?