Usual overview of APEX framework and current modules (like Destruction and Clothing), which are already familiar to us from past GDC10 and SIGGRAPH09 sessions, is followed by topic never described in detail previously – Scalability and LOD features inside APEX (starts at 32:55).

In general, it’s devided into two components – scalable parameters for each of the modules (like number of particles or cloth vertices), that can be adjusted during authoring to fit into platform computing capabilities..

..and dynamic LOD system, that manages resources destribution between actors and modules, based on current situation and resources budget (for example, clothing on character closer to the camera will be simulated with higher fidelity).

Now, as we know almost everything about APEX, we just need to wait until it will be released to public (standalone, or integrated into popular engines like UE3).

]]> http://physxinfo.com/news/3471/siggraph-2010-nvidia-apex-and-scalability/feed/ 8 http://physxinfo.com/news/3285/physx-visual-debugger-2-0-6-beta-first-sdk-3-0-signs/ http://physxinfo.com/news/3285/physx-visual-debugger-2-0-6-beta-first-sdk-3-0-signs/#comments Sat, 26 Jun 2010 12:07:03 +0000 Zogrim http://physxinfo.com/news/?p=3285 New 2.0 version of PhysX Visual Debugger, object-based database application for analyzing captured data from PhysX engine, was updated to version 2.0.6. Beta.

Release Notes:

• Lots of optimizations during capture!  Capturing should be even quicker and more painless than it was with the first beta.
• Lots of UI bugfixing specifically to the tree views (All Objects, Selected Objects, Watched Objects).  They should be more stable and much more user friendly especially when selecting new objects.
• Navigation and selection were reversed.  So navigation is the default action while selection requires pressing ‘alt’.  You can quick select something by double clicking on it without pressing ‘alt’.
• Reversed the log file direction.  No more scrolling down; new errors at the top.
• New preferences dialog !  Much easier to use, no tabs.
• Got rid of the frames palette.  We are sorry it ever existed.  The playback controls got moved to the toolbar while the slider got moved to the bottom of the scene view.

And more interesting:

• Preliminary support for the 3.0 version PhysX !!!.  We are very excited about this.

Yep, we are excited about it too

You can download PhysX Visual Debugger 2.0.6 Beta via Developer Support Center.

If you are experiencing trouble with registration of PhysX Developer account, please refer to our registration guide.

• New: added support of multi-core CPUs (PhysX simulation is spread over several threads). New checkboxes are also available to control this feature.
• New: added a checkbox to set the number of particles.
• New: added a checkbox to force CPU PhysX.
• New: added Heavy PhysX mode: to make modern systems with GPU PhysX happy
• New: added point sprite based rendering for particles (keys F2, F3 and F4).
• New: added keyboard-based camera control in stability test mode.
• Change: compiled with NVIDIA PhysX SDK 2.8.3.21.
• Change: updated with the latest version of ZoomGPU for graphics hardware detection.

Update: limitations of GPU PhysX simulation

Update #2: Async mode details

We’ve already did more or less detailed features overview in our FluidMark 1.2 Beta preview article (in addition, more technical details are available from original post), so this time we will just point on certain changes in release version in comparison to beta one.

Main window haven’t underwent much changes..  (click to view full picture)

.. while benchmarking process was improved, to achieve results standardization. Every benchmarking sequence now starts with so called “Warming-Up” state, to ensure that all particles are emitted on the scene. In addition, default settings are now set to 60 000 particles and one minute timed run.

Moreover, new FluidMark 1.2 is now officially approved by Nvidia. According to JeGX, FluidMark developer, NV engineers have helped with bug fixing and overall optimizations, but have not influenced development process in order to give an advantage to GeForce GPUs or penalize CPUs.

And, of course, some tests (Note: since we are using different settings now, and other internal changes in FluidMark, these results can not be directly compared with our previous benchmarks)

System: C2Q 9400 @ 2.66 GHz CPU, Nvidia GTX 275 + GTX 260 (192 sp) GPUs, 4GB RAM, Win XP, PhysX System Software 9.09.1112. Default settings, # of emitters = 3.

In final version of FluidMark multi-core PhysX checkbox is related only to PhysX SDK simulation part, while main app (GUI) and rendering threads are separated all the time – thus  it almost does not affect GPU PhysX mode, like in Beta version.

As for much higher difference between GPU PhysX and multi-core CPU PhysX – it seems that beta version contains a bug, that results in abnormal low score for PhysX on single GPU (in general, it should be much closer to dedicated PhysX GPU).

Sum: Good old FluidMark, but now with true multi-core CPU PhysX support and enhanced benchmarking procedure. One of the best GPU PhysX testing tools becomes even better.

You can download PhysX FluidMark 1.2 from here (2.5 mb)

P.S. Thanks to Jerome “JeGX” Guinot for Release Candidate version of FluidMark, provided beforehand.

Update: PhysX Visual Debugger 2.0.6 Beta

Current release notes are unknown, but it seems that PVD 2.0 was completely rebuild from scratch (upd: confirmed, it’s complete rewrite) – just take a look at the main application window (click to view full picture), and compare it with previous PVD 1.1.9

You can download PhysX Visual Debugger 2.0 Beta via Developer Support Center.

If you are experiencing trouble with registration of PhysX Developer account, please refer to our registration guide.

If you have trouble with new account registration or existing account (dissapearing downloads, unable to log-in, etc) you can send your problem description to support@physxinfo.com – we’ll try to provide a shortcut to PhysX dev. team.

Jerome Guinot, FluidMark developer, was kind enough to provide us with latest beta-version of new Fluid-Mark 1.2, and we’ll try to answer finally, what is faster – GPU PhysX or properly optimized CPU PhysX.

But first, lets take a closer look at new FluidMark. (click to view full picture)

Main control panel now includes several additional options, like “Force PhysX CPU” – ability to switch between GPU and CPU PhysX, without necessity to use Nvidia Control Panel.

“Multi-core PhysX” checkbox enables all multi-threading optimizations, vital and most interesting part of new FluidMark.

“# of CPU cores” is used specify number of CPU cores dedicated to simulation (up to 32 in current version), however this option is no so transparent as it looks – increased number of cores adds additional fluid emitters to the scene (one emitter per core or two in general), and with equal number of particles, various number of emitters can affect performance.

Application window has also changed – benchmark is still based on SPH fluid simulation, built into PhysX SDK (latest version 2.8.3.21 is used), but scene includes additional static objects, particles appearance if different and, as mentioned earlier, several emitters can be used simultaneously. Nice addition – GPU temperature overlay, usefull for GPU stress testing.

Final Global score in benchmarking mode is calculated now in a different way, and can’t be compared with previous version of FluidMark. It consist of two components – GraphX score (graphics framerate per second) and PhysX score (physics simulations per second).

Thus, Global score = (GraphX_score * 0.3 + PhysX_score * 1.7) / 2

Now, lets do some testing.

The Wonder of Multi-Threading !

Take a look at the following graph:

[Three emitters were used (# CPU cores = 4) with fixed number of particles - 15 000. Timerange - 60 sec. 800x600 rendering window. System: C2Q 9400 @ 2.66 GHz CPU, Nvidia GTX 275 + GTX 260 (192 sp) GPUs, 4GB RAM, Win XP, PhysX System Software 9.09.1112]

When “Multi-core PhysX” option is off, PhysX simulation and scene rendering are done in the same thread and, more important, PhysX SDK multi-threading flags are not set.

But when “Multi-core PhysX” is enabled, all PhysX simulations are done in separate threads and since there is still a thread for the rendering, scene rendering is boosted because there is no longer PhysX in scene thread. Same situation with PhysX, one or several threads are completely dedicated for physics simulation.

While SPH fluid simulation is running on CPU with  “Multi-core PhysX” set to off, load is destributed through several cores (probably due to internal Windows threads management), but in sum that’s 26% – full one core.

But with multi-threaded optimizations enabled, application fully utilizes all four cores by 100%, what results in great speed boost.

In addition, one interesting detail was discovered – fluid simulation is running faster on GPU when one emitter is used, and opposite way – for CPU it prefers multiple emitters (with equal number of particles) – probably that’s peculiarity of PhysX SDK itself.

For example, with one emitter and multi-core PhysX switched to off, CPU simulation results in 36 global points (64 with 3 emitters – on graph above), while GTX 275 GPU – in 247 points (128 with 3 emitters). But since one emitter can’t utilize more than two cores,  number of emitters was increased to gain equality.

Therefore, bechmarking seems to be a little tricky in new FluidMark. We are curious if someone will come with solid method after app release.

P.S. Thanks to Jerome for beta FluidMark and detailed explanations

Update: main PhysX and APEX session are now available as slide decks and video records

APEX Clothing with 3ds Max by Gavin Kistner, Product Designer, NVIDIA

Gavin gives a quick overview of 2.0 PhysX plug-in for 3ds Max, and uses superhero character with cape to explaing full clothing authoring process. Personal love Gavin’s manner of talking.. funny guy

Physically Simulated Clothing By CCP (EVE Online) Using NVIDIA APEX by Vigfus Omarsson, Lead Technical Artist, CCP; Snorri Sturluson, Senior Software Engineer, CCP; Monier Maher, APEX Product Manager, NVIDIA

Include overall cloth sim benefits overview from CCP, clothing tools pipeline features demonstration with Maya, and, of course, authoring process with pretty female character. While authoring was done in Maya, actual simulation was running in “CCP engine” window, as stated by Vigfus.

APEX Vegetation with the SpeedTree Modeler by Michael Sechrest, President and Co-Founder, Interactive Data Visualization (IDV), Inc.; Lou Rohan, Senior Software Engineer, NVIDIA

Modelling, compiling and SDK pipeline overview related to APEX Vegetation integration with SpeedTree 5.1. Some trees get hurt and broken, all with physically correct behaviour

APEX Destruction using PhysX Lab by Bryan Galdrikian, Senior Apps Engineer, Physics R&D, NVIDIA

Detailed description of PhysX Lab Tool features and options. As in other APEX presentations, destruction authoring process is fully explained, using stanford bunny model and several other objects.

Update: Video demonstration available

Update #2: CCP presentation screencast from “Nvidia Game Technology Theater” at GDC now available.

Update #3: Full session video record available at GDC Vault

Led by Vigfus Omarsson and Snorri Sturluson from CCP, this talk was focused on APEX Clothing system integration with in-house engine, supposed to be used in Incarna add-on for EVE Online and, probably, new World of Darkness MMO.

Using a nice custom character as an example, full clothing authoring pipeline was demonstrated.

Several additional topics, including cloth sim optimizations under MMO specific needs, LOD system and debugging tools were discussed.

For dessert – real-time cloth simulation preview.

Too pretty for a capsuleer, huh ? Guess that’s how exotic dancers will looks like in Incarna

You can view rest of the article here.

P.S. usually, sessions in .pdf format or even in full video stream form are emerging soon after GDC, so stay tuned !

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

Recently, with help of David Legrand from PCinpact.com, Jerome “JeGX” Guinot was able to test new FluidMark 1.2 on setup with 16 CPU cores. (click to view full image)

And as you may see, CPU PhysX simulation with 48 000 fluid particles is 100 % utilizing all 16 Cores. Amazing work

New FluidMark is going to be available soon enough, after JeGx will catch and kill remaing bugs.

Update: JeGX is participating in “What Would You Do With 48 Cores ?” contest by AMD with new FluidMark (which already support up to 64 CPU cores). That’s going to be interesting 

Source: PCinpact | Geeks3D

PhysX Rocket was often used by Ageia to demonstrate SDK features and PPU computing capabilities in year 2005, and was included in SDK package as PhysX tool (till SDK 2.7.3.).

John Ratcliff, PhysX Rocket creator, has made a nice present recently – he revealed an updated legacy version of Rocket, which is based on latest PhysX SDK 2.8.3 and includes advanced UI options (unavailable in previous public versions), but is missing some vital demo scenes and object files. Fortunately, we were able to merge this updated Rocket with old one, from SDK 2.7.3 Tools – this means all demos like in regular Rocket, but SDK 2.8.3 solver and additional UI options from new one.

PhysX Rocket remains a nice physics playground even today, so if you’re ready to spend half an hour by throwing physical bricks, bending physical grass and kicking physical ragdolls, use download link provided below:

Download PhysX Rocket for SDK 2.8.3 from our server (75 mb – download currently unavailable). RAR archive, no installation required.

Note: Requires latest PhysX Systems Software to run properly.

And, by the way, Rocket supports multi-threaded CPU PhysX