Archive for the ‘PhysX Drivers’ Category
Nvidia has revealed new PhysX System Software package – 9.10.0513
According to release notes, main difference from previous PhysX drivers is
- Bug fixes for Mafia 2
You can download 9.10.0513 PSS from here
Update: We can’t notice any performance increase in Mafia II.
- Fixes a bug that prevented PhysX from being accelerated on Optimus PCs.
You can download PhysX System Software 9.10.0224 from our server (34 mb – download currently unavailable)
Also, it seems that naming sheme has changed completely – from dates to version numbers of some kind.
Recent whql release of GeForce/ION 257.21 GPU drivers has brought us updated PhysX System Software v. 9.10.0223.
If naming sheme is still following same pattern, .0223 drivers are dated just day after previous 9.10.0222 System Software, and their feature set is also unknown currently (at least, SDK .dlls haven’t changed).
Update: System Software 9.10.0223 is now available for official download
- Bug fixes for Metro 2033 in SDKs version 2.8.3.
- Clothing bug fix in SDKs version 2.8.3 with respect to max distance clamping.
- GPU PhysX Performance optimizations for GeForce 400-series GPUs in all GPU PhysX enabled SDKs versions.
- Better error handling for GPU PhysX in the unlikely event of a CUDA error in SDKs version 2.8.3.
- Other miscellaneous bug fixes.
Anyway, you can download PhysX System Software 9.10.0223 from our server (27 mb – download currently unavailable)
Today, Nvidia has presented new 256 Family of GeForce/ION drivers. Among from other features, like improved performance for GTX 400 Series GPUs, Blu-Ray 3D, CUDA 3.1 and OpenGL 4.0 support, new drivers are introducing enhanced configuration panel for Multi-GPU and PhysX configurations, with more intuitive interface.
In addition, it’s now posible to specify which GPU use for each CUDA (and PhysX) application via Manage 3D settings page.
Recent news coming from NGOHQ website with statement “performance on non-Cuda cards got dropped even further (from 20 fps to 5 fps [Mirror's Edge]) in the recent PhysX software” have forced us to perform more detailed testing procedures, to discover how actually valid such claims are.
Update: From NGOHQ:
After deeper investigation, this issue has identified as a rare overflow bug. Looks like Nvidia PhysX System Software 9.10.0222 doesn’t cripple performance, but I’ll run more tests just to be sure
In following article we are comparing both GPU and CPU performance of PhysX effects, using most recent PhysX System Software 9.10.0222 (blamed for “ruining game experience”), previous 9.10.0129 version and several games – Mirror’s Edge 1.01 and Cryostasis Tech Demo.
System: C2Q 9400 @2.66 GHz CPU, GTX 275 GPU, 4GB RAM, Windows 7 Professional x64
Standart “Flight Fly By” sequence was used (can be activated by “- FlybyFlight” parameter), in-game setting; 1680×1050, all high, 4xAA. Framerate measured by FRAPS 3.0.1.
New PhysX System Software 9.10.0222, which comes with recently released Metro 2033 title, emerges on the web.
This release includes updated engine .dll’s for SDK from 2.7.3.. to 2.8.3 and is dated 22 February 2010.
Download PhysX System Software 9.10.0222 from our server (34 mb – download currently unavailable)
Source: Guru3D forums
Recent Geforce 196.75 GPU drivers from Nvidia have brought us something interesting – they include new PhysX System Software 9.10.0129.
This release is smaller than previous 9.09.1112 drivers – only 27 mb vs 34 mb previously, and is dated 29 January 2010, according to PhysX drivers naming system.
Download PhysX System Software 9.10.0129 from our server (download currently unavailable)
Update: Simple look at drivers installation folder reveals that engine .dll’s for SDK 2.7.3, 2.7.4.. all to 2.8.3 were updated with new subversions. No major changes except this.
Update #2: PhysX System software 9.10.0129 is now available as separate download from Nvidia website.
Includes the latest PhysX runtime builds to support all released PhysX content including Dark Void and others.
Supports NVIDIA PhysX acceleration on all GeForce 8-series, 9-series, 100-series, 200-series, and 300-series GPUs with a minimum of 256MB dedicated graphics memory and 32 CUDA cores. Note: Some applications may have higher minimum requirements.
Supports NVIDIA PhysX acceleration on GeForce via CUDA 3.0 for SDK versions 2.7.1, 2.7.3, 2.7.4, 2.7.5, 2.7.6, 2.8.0, 2.8.1 and 2.8.3 (requires graphics driver v196.21 or later).
Supports control of your GPU PhysX configuration from the NVIDIA display driver control panel. (requires graphics driver v196.21 or later).
Official Release Notes are also available:
- Includes the latest PhysX runtime builds to support all released PhysX content including Batman Arkham Asylum and others.
- This release also resolves issues with Arabic language installations and occasional simulation interruption on some machines and titles.
- New runtimes for the PhysX SDK 2.8.3.
- Supports NVIDIA PhysX acceleration on all GeForce 8-series, 9-series, 100-series and 200-series GPUs with a minimum of 256MB dedicated graphics memory and 32 CUDA cores. Note: Some applications may have higher minimum requirements.
Newest PhysX System Software 9.09.1112 was uploaded to Developer Support Center. It contains updated runtimes for some upcoming APEX tools, but most of users and developers won’t see any differences from 9.09.30 System Software.
In addition, according to our sources, PhysX System Software 9.09.1112 will be included into next release of public GeForce drivers.
If you are experiencing trouble with registration of PhysX Developer account, please refer to our registration guide.
Update #2: official WHQL version is available
PhysX System Software 9.09.30, available only for PhysX developers previously, leaks out. As anyone else, were were not authorised to provide public download, but as concerned gamers gained access to Developer Support center, download link emerges.
Main difference in this release from 9.09.14 Drivers is updated .dlls for 2.8.3 PhysX SDK.
You can grab 9.09.30 PhysX Drivers here, while download is still available.
Update: Mirror #2;