Archive for October, 2010
Marvelous informational video was uploaded today by our regular reader – Andrew Elliott (also known as elliottad or MohawkADE). It is related to overview of Ageia PPU card history and it’s place in current hardware accelerated PhysX infrastructure.
Also, you can find full transcript at our forums.
- How to put the Demos back in the PhysX Control Panel: Video Guide
- How to restore Ageia PPU support with latest NVIDIA Drivers: Video Guide
If you own an Ageia PhysX card, planning to buy one, or just interested in PhysX lifecycle – this video is worth watching without doubt
If you’re watching over Carmageddon remake, powered by XNA and PhysX.NET wrapper, we’ve got a surprise for you – first public beta version of OpenC1 project (that’s how it is called now, due to copyright issues) was released today.
Update: v1.1 available, should fix some of the crashes.
Update #2: version 1.3.1 available
Basically, OpenC1 is a accurate remake of classic Carmageddon by Stainless Software (original data files are used, but underlaying code is completely new). Currently, all basic systems (car physics, opponents AI, carcase deformation, pedestrians, sound, user interface, race logic, etc) are already implemented.
- Install XNA Framework 3.0
- Install latest PhysX System Software.
- Download OpenC1 v1.1 Beta from original post. Extract the OpenC1 files, check out the readme.txt, then run OpenCarmageddon.exe.
Remember that this is still early beta, and stable work is not garanteed. Please report found bugs and errors here.
Those of you who are familiar with PhysX plug-in for 3ds Max (for example, recently released 2.40 version) may already notice that by default simulation is not going as smooth as you can expect – rigid body objects are often interpenetrating each other, jittering and jiggling (especially when stacked) , and so on – making it hardly suitable for some scenes.
UPDATE: Not valid for 2.60 PhysX plug-ins and above
So, we’ve contacted Gavin Kistner, Product Designer for PhysX Max and Maya plug-ins at NVIDIA, and he gave us several tips, using those you can deal with simulation stability problems in most of the cases:
TIP I – Increase Frame Rate
If rigid bodies are showing inaccurate behaviour, this is indicating that physics engine is just not performing enough simulation substeps between frames. To fix that (as separate substeps control is yet not availalbe in public versions of PhysX plug-in) you can simply increase Frame Rate before previewing or baking the simulation (and than revert it back to normal during composing, for example).
To illustrate this tip, let’s set up a simple scene – several rigid body planks falling one at each other, trying to form a stack.
With default Frame Rate – 30 fps (shown above), simulation is just messed up. At certain frame planks are stuck together, solver is trying to resolve inter-collisions and repels planks – stack collapses.