GDC 2010 (Game Developer Conference) is just about to start, and is going to be rich on PhysX related content this year. Apart from session on APEX Clothing integration with EvE Incarna we mentined previously, featured talks will include “Authoring Physically Simulated Destruction with NVIDIA APEX” and “Taking Fluid Simulation Out of the Box: Particle Effects in Dark Void“.

You can read session descriptions via provided links, but actually not only this has catched my eye. Nvidia GDC 2010 page was updated with schedule of presentations, that are going to be demonstrated at Nvidia booth #1702 at March 12-13

Those include such intriguing topics like:

Unity for Engineers – are they planning to demonstrate update physics system in Unity 3.0 ?

Authoring Runtime Animation with NaturalMotion Morpheme 2.3 – I’ve heard that Morpheme is going to be integrated with APEX Clothing, is that it ?

Softimage 2011 Enhanced with PhysX – next version of Softimage will include updated PhysX SDK integration ?

Streamlining PhysX Content in Max – is it related to rumored new physics system in XBR ?

Sadly I can’t visit GDC myself, but I’ll try to provide you with any open or insider information I’ll be able to gather

UNITY is popular multiplatform development tool, used in many titles, from numerous iPhone games to major one like Interstellar Marines.

Internal physics system in Unity is using custom driverless version PhysX SDK – unfortunately, since main SDK core is very old (2.5, afair), it’s missing not only recent updates and bugfixes, but some features like fluids, cloth, forcefields and even GPU-acceleration. While Unity Technologies were keeping PhysX un-updated for years in a matter of “combability”, such renovation was actually needed by developers.

And, finally – recent announce of long awaited Unity 3.0 engine promises not only iPad and Ps3 platforms support, deferred render, built-in lightmapping system and unified editors, but “major updates to Unity’s.. physics features“

No details were revealed, but Tom Higgins, Unity Product Evangelist, made a short sneak-peak

We are upgrading PhysX but will be saving the specifics until later, let’s just say it will have some juicy new features for sure!

We’ll try to keep an eye on this, so stay tuned.

Update: new details on PhysX features for Unity 3.0 beta

Recent articles about Metro 2033 have revealed so much technical details (about engine itself, and PhysX components specifically) so, one would think, nothing new can be added. However, recent interview with Chief Technical Officer Oles Shishkovstov by PCGamesHardware.com has something to offer:

PCGH: It could be read that your game offers an advanced physics simulation as well as a support for Nvidia’s PhysX (GPU calculated physics) can you tell us more details here? Does regular by CPU calculated physics affect visuals only or is it used for gameplay terms like enemies getting hit by shattered bits of blown-away walls and the like?

Oles Shishkovstov: Yes, the physics is tightly integrated into game-play. And your example applies as well.

PCGH: Besides PhysX support why did you decide to use Nvidia’s physics middleware instead of other physics libraries like Havok or ODE? What makes Nvidia’s SDK so suitable for your title?

Oles Shishkovstov: We’ve chosen the SDK back when it was Novodex SDK (that’s even before they became AGEIA). It was high performance and feature reach solution. Some of the reasons why we did this – they had a complete and customizable content pipeline back then, and it was important when you are writing a new engine by a relatively small team.

PCGH: What are the visual differences between physics calculated by CPU and GPU (via PhysX, OpenCL or even DX Compute)? Are there any features that players without an Nvidia card will miss? What technical features cannot be realized with the CPU as “physics calculator”?

Oles Shishkovstov: There are no visible differences as they both operate on ordinary IEEE floating point. The GPU only allows more compute heavy stuff to be simulated because they are an order of magnitude faster in data-parallel algorithms.

As for Metro2033 – the game always calculates rigid-body physics on CPU, but cloth physics, soft-body physics, fluid physics and particle physics on whatever the users have (multiple CPU cores or GPU). Users will be able to enable more compute-intensive stuff via in-game option regardless of what hardware they have.

Pay attention to last paragraph – Metro 2033 will feature true multi-core implementation of GPU PhysX content – feature that most PhysX titles are lacking currently ? We are curious to see if this will really work, and since game has already gone gold, we’ll learn that very soon.