Hawken is a promising online mech-based combat game, under development by indie company Adhesive Games. This upcoming title has already garnered enough fans among players, thanks to excellent level design and gorgeous visuals.

Recently, Hawken trailer, featuring additional physically simulated particle effects, was demonstrated during Jen-Hsun Huang Keynote at NVIDIA Gaming Festival (NGF 2012).

Later on, PhysX support was confirmed by Jason Hughes, producer at Adhesive Games.

According to our sources, game will not only include PhysX particle effects, but also have destructible environments.

Update: several screenshots were captured by Game Watch website.

Hawken is slated to be released at 12.12.2012.

Following trailer, showcasing hardware accelerated PhysX effects in upcoming Borderlands 2 title from Gearbox Software, was recorded on camera by one of the participants of Nvidia GeForce GTX Meet-Up event, which was held in San Francisco on March 28.

Update: alternative version

Now you can see all previosly mentioned effects – physical particles, tearable cloth and dynamic fluids – in action.

Some interesting technology prototypes, that might greathly enhance Eve Online visual look in the future, were demonstrated today during “CCP Presents” keynote at Fanfest 2012 event by Tony Tamassi, Senior Vice President of Content & Technology in NVIDIA.

Update: video available

Update #2: devblog from CCP & article from NVIDIA

First one – DX 11 support and tesselation. In a real-time demo scene (running on a GTX 560, btw – “most commonly used card in EvE” as Tony stated), tesselation was used to enhance relatively simple model of Revenant Sansha Carrier with incredible number of smaller details (all the spurs, cables and stuff – being real geometry, not plain normal maps), all properly lightened and casting real shadows.

Second – additionally physically simulated objects in the space. In the same demo, while fairing through massive asteroid field, carrier was colliding with smaller asteroids and debris, flying all other the field, crashing and fracturing them upon impact. All simulation was done through PhysX SDK.

We remind you that currently PhysX/APEX is already used to sumulate clothing and hair on characters in EvE Online.

And finally, innovative offer was presented – capsuleers will have an option to buy NVIDIA GPUs.. for PLEX. GTX 560 was priced at 20 PLEX (however, offer might be limited to this model only).

It is now official – Borderlands 2 will be the next game to support GPU accelerated PhysX effects.

Update: GPU PhysX trailer was caught on camera

At GeForce Kepler Editor’s Day (event, during which Kepler GPUs were presented to press), Borderlands 2 demo featuring GPU PhysX effects was demonstrated by Randy Pitchford, Gearbox Founder and CEO, running on a GeForce GTX 680 GPU.

Hardware accelerated content will include:

• Fully simulated tearable cloth which interacts with weapons, forces, weather, etc
• Persistent GPU simulated particles that interact with the world
• Fully-interactive fluids
• Maybe something more

Update: Some impressions from journalists who saw the live demo:

Gamespot:

The PC version of Gearbox Software’s upcoming Borderlands 2 is set to support many PhysX enhancements. These include water that reacts accurately to a player’s movements, rippling and splashing around the environment as you walk through it.

Borderlands 2 also makes use of PhysX to render destruction. For example, fire a rocket launcher into the ground, and huge chunks of earth and gravel fly into the air. The resulting debris settles on the floor, where you can kick it around by walking through it.

Eurogamer:

At NVIDIA’s press event we were treated to a demo of Borderlands 2 with PhysX enhancements including some impressive water simulation, enhanced (destructible!) cloth physics and volumetric smoke trails from rockets, which animated beautifully.

Destructoid:

At NVIDIA’s Editor’s Day, Gearbox Software CEO Randy Pitchford showed off Borderlands 2 and how it implemented PhysX. Fluids pooled and flowed in complete real-time, and even reacted to explosions — splashing about into numerous smaller puddles.

Cloth materials reacted accordingly to foreign objects, and could even be torn and shredded when fired at.

It was quite incredible how these effects could be handled with such relative ease in real-time, when just five years ago it took me several hours to render them for 3D animations on a high-end PC.

We hope that Gearbox will provide more detailed information, including screenshots or video, soon enough.

Borderlands 2 is slated to be released in September, 2012.

QQ Dance 2 is a sequel to ultra-popular (over 2 million concurrent users, 100 million registered users) Chinese online dancing game called, obviously, QQ Dance.

Build on proprietary H3D engine, QQ Dance 2 will not only provide significant improvement in visual fidelity, but also feature fully simulated clothing and hair on characters using PhysX SDK 2.8.4 and APEX Clothing module.

Presented demo is containing 50 000 simultaneously simulated cloth vertices (for example, even most intense scene in Mafia 2 has no more than 15 000 cloth vertices).

QQ Dance 2 is supposed to be released in Q4 2012. This game will not only support GPU acceleration, but also have a CPU path for non-NVIDIA systems.

Ever since the existence of Unreal Engine 4, next-generation game development platfrom from Epic Games, was revealed, one question was bothering us – will it still rely on PhysX SDK integration for physics sumulation, like UE3 and UDK?

And it seems the answer is “Yes”.

During presentation of PhysX and APEX features, that NVIDIA employee was giving to Gametrailers at GDC 2012, following words were said:

So here we are showing some of our technologies that are already incorporated in the games and game engines.

In this case all three of these demos are in Unreal Engine.. we are integrated in both Unreal 3 and upcoming Unreal 4.

NVIDIA has released APEX SDK 1.1 (Build 112), next version of NVIDIA APEX – scalable dynamics framework, oriented on complex physical simulations.

In comparison to APEX 1.0 Beta, new version includes many bugfixes, several additions to underlying framework and various new features, like ability to calculate rigid body physics on GPU.

APEX 1.1 contains only Destruction and Clothing modules, and is still based on PhysX SDK 2.8.4.6 – first version with PhysX 3 support is going to be APEX 1.2 (that is supposed to be released in a few months).

We must also note that APEX 1.1 requires corresponding authoring tools – PhysXLab 1.1 and 2.71 DCC plug-ins.

NVIDIA APEX SDK 1.1 is available for download at Developer Support Center.

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

Release Notes:

APEX DESTRUCTION 1.1

New Features

• GPU Rigid Bodies: the NxModuleDestructible has settings to enable calculation of Rigid Body physics on GPU.

Highly anticipated feature. While using same assets and same settings, GPU Rigid Bodies are showing significantly higher performance – 70 fps for 5000+ rigid body chunks on single GTX 580 vs 10 fps on Core i7 2600K.

One-way interaction with dynamic CPU actors is also supported (via transfer of momentum). GPU accelerated rigid body physics requires NVIDIA driver 270.81 or later, PhysX 2.8.4 RC6 or later and a CUDA capable GPU.

• Chunk instancing: (when authored to instance) correponding chunks between different destructible actors will be rendered using an instance buffer. This is advantageous if there are many destructible actors which reference the same asset.
• Chunk tiling: (when authored to tile) matching chunks created from cutout fracturing will be instanced within the same actor, as well as other destructible actors which reference the same asset. This can drastically reduce the memory size of the asset.
• NxDestructibleActor:
  • LOD setting sets the maximum chunk depth which can be fractured, implementing forcePhysicalLOD interface.
  • getChunkLinearVelocity and getChunkAngularVelocity API in the actor.
  • Per-actor materials in the actor descriptor.
  • Can specify a separate render mesh for static chunks which gets drawn in a single draw call, using the renderStaticChunksSeparately field in the actor descriptor
  • Can set a separate set of static materials used by the static mesh if renderStaticChunksSeparately is set.
  • minimumFractureDepth added to destructible parameters, to limit the size of the pieces that can be broken free.
  • Implements applyTransformation interface to geometrically transform an asset.
• Fracture event callback now consolidates chunk information to reduce the number of fracture events reported.
• NxActor (chunk island) FIFO can now be sorted by “benefit” (takes into account screen size and age of the chunk), so that less-beneficial chunks are removed first.
• NxShape count limit can be set in addition to NxActor count.

Improvements

• Chunk creation can be amortized over many frames.
• Fracture processing can be amortized over many frames.
• Conforms to new LOD system.
• Removed the per-chunk thread locks, for better performance and resource usage.
• SimpleDestruction has multiple sample scenes, loaded using the keys 1-7.

Bug Fixes

• Damage reports are no longer issued when a destructible is set free using setDynamic().
• Several crash bugs fixed.

Authoring Improvements

• Ability to have multiple collision hulls per chunk.
• Can cancel the fracture operation.
• “Trim face hulls” option in cutout fracturing.
• Ability to use multiple UV channels and color channels from FBX meshes
• cookChunks does not use the internal ExplicitHierarchicalMesh any longer, only information passed in from the descriptor.

APEX CLOTHING 1.1

New Features

• Per-Actor scaling. Each actor can have an individual scale and simulates properly.
• Asynchronous cooking. When several actors with different per-actor scale are created, cooking will be delayed if another actor already started cooking. While waiting, actors will not be simulated.
• Manual substepping: A PhysX scene that will run multiple substeps is now handled properly by clothing. Interpolated simulation meshes will be generated for each individual substep to remove simulation artifacts caused by substepping.
• Teleport without reset: Clothing Actors can now be teleported without all the vertices being reset to the animated positions. This will only lead to good results if only the pose of the actor and not the state of the animation is changed.
• Frozen state: Clothing can be frozen in a given state and will cease simulation. It can then be woken again in the same state. This contrasts the regular way where re-enabled clothing starts from the animated state instead.
• Velocity Callback: A user callback that allows to read and write the velocity values of every simulated vertex. Can be used to play sound depending on certain changes in velocity or to implement i.e. a wind effect.
• Support for morph targets (also known as blendshapes): At actor creation a set of vertex displacements can be used to modify the mesh.
• Platform Tags: Each graphical LOD can have a list of strings attached. When converting the .apx/.apb files to a given platform, LODs that don’t match a certain pattern can be removed based on this.This allows for reducing asset size by removing LODs that are unsuited for a particular platform.
• Correct Simulation Normals: Vertices that are on the border of the simulated and non-simulated part of the physical mesh can have wrongly calculated normals. This setting will try to correct for that.
• Adaptive Target Frequency: Reduces the high frequency jittering that happens due to slightly varying timesteps.
• Pressure: Closed cloth meshes can be filled with pressure.
• Vertex Velocity Clamp: Adds a maximum velocity in all 6 major axis and clamps all velocities to those.

Improvements

• Switching of graphical LoDs has been improved in respect to copying position and velocity from the old to the new simulation mesh.

Removed

• Legacy serialization is gone. Any old .aca file cannot be loaded anymore. They need to be converted to .apx/.apb using the 1.0 ParamTool instead.
• Some API marked as deprecated has been deleted such as NxClothingActor::setFlags().
• Removed separate NxClothingMaterialLibrary (.acml files) as an asset type. Materials are now integrated into the Clothing Asset file directly.
• Parallel physics mesh skinning and parallel mesh-mesh skinning. The frame delay that was introduced by this feature made it useless to most applications.

APEX FRAMEWORK

NxParameterized

• New method Interface::clone.
• Handles which are constructed from const Interfaces do not allow to change those Interfaces via setParamXxx.
• Generic reference visitor NxParameterized::getReferences.
• Streamed non-inplace binary deserialization.
• Fixed handling of defaultValue in structs.
• Fixed detection of hint types.
• Automated versioning of legacy classes.
• Customizable order of legacy objects upgrade instead of fixed bottom-up.
• Custom alignments of struct fields.
• ParamTool can now print summary of file contents.

Serialization

• ParamTool does not support legacy asset formats anymore.
• Changed some error codes.

Render Mesh Asset

• setOverrideMaterial was added to allow switching of material directly at runtime.
• Debug rendering vor vertex normals and tangents.

Use of Cuda 4.1

• Necessary for supporting latest hardware.

P.S. We expect APEX 1.1 integration with UE3/UDK to be available in February 2012 release.

Certainly, many of you will agree that the addition of GPU PhysX effects to PC games has a positive influence on overall gaming experience and immersion in such titles. But how difficult is to attach hardware accelerated physics effects to a game?

Today, with the help of David Schoemehl, Manager of GPU PhysX Content in NVIDIA, and Johnny Costello, Technical Artist, we will try to give you a brief “behind the scenes” view on the process of enhancing games with extra PhysX content.

PhysXInfo.com: Hi, Johnny and David. Can you please introduce yourself?

Johnny Costello: My name is Johnny Costello, I’m 29 years old and am a native to the Midwestern United States. I went to college at Savannah College of Art and Design and received my B.F.A. in game development. I have been a technical artist at NVIDIA for about two and a half years. During that time I have worked on several GPU PhysX titles such as Batman: Arkham Asylum, Batman: Arkham City, Mafia II, Dark Void, and Alice: Madness Returns.

David Schoemehl: My name is David Schoemehl, I joined AGEIA in 2006 as an applications engineer and was the project manager on Warmonger. Since the purchase of AGEIA by NVIDIA in 2008 I have led or supported several shipping GPU PhysX titles and demos including Batman: Arkham Asylum, The Samaritan Demo, Sacred 2, The Great Kulu Demo, and Alice: Madness Returns.

My current title is Manager of GPU PhysX Content and I am responsible for aligning NVIDIA’s engineers and artists to support developers on GPU PhysX engagements. I also work closely with Epic Games to ensure a solid integration of GPU PhysX/APEX features in UE3.

PhysXInfo.com: Johnny, what is your task as a PhysX technical artist?

Johnny Costello: My tasks can change a lot from day to day, but usually I’m working on a game title in some capacity. Our goal at NVIDIA is to provide the tools that developers need in order to add great GPU features to their games. So I spend much of my time working with developers to help guide them as they use our technology to create exciting content.

Depending on the structure of a particular engagement I may also work alongside the developer to create GPU PhysX content. Then there are other days where I help design and review our tools and production workflows.

PhysXInfo.com: So what is in the process of adding GPU PhysX effects to a game?

Johnny Costello: We usually start by getting a build of a game and playing through it in its current state. We also read any available design and art documents to familiarize ourselves with the gameplay mechanics and the aesthetic style. From there, we identify any story events, environment locations, special effects, characters, etc. that could be enhanced with our feature set and make the game more fun to play.

From there, we work with the developer to refine this list and plan out a timeline. After that, it’s all about creating content with our tech that players will enjoy.

Once the content gets in the game, it starts getting reviewed by QA. We usually spend our time at the end of a title engagement addressing any bugs that QA has found and making minor content adjustments.

APEX Toolset helps artists to create content more easily

PhysXInfo.com: Users are often complaining that extra PhysX effects are not optimized properly for CPU execution (not using multiple cores, for example). What is the reason behind this?

David Schoemehl: This is a legacy issue regarding PhysX versions prior to 2.8.4. With proper setup it is possible to achieve some threading on PhysX 2.8.4, for instance running multiple cloth simulations in parallel. However, the overall threading performance issues have been addressed in PhysX 3, which is available today. With PhysX 3 we have improved the rigid body, clothing, and particle pipelines to take better advantage of multiple CPU cores.

PhysXInfo.com: Also, there is an opinion that with disabled GPU PhysX option, minor effects (like sparks or cloth banners) are omitted from the games on purpose, while they can be easily calculated on CPU or substituted with non-physical objects. What can you say about this?

David Schoemehl: When NVIDIA engages with a developer to work on a GPU PhysX title we will offer suggestions for enhancing existing effects and adding entirely new effects. For the existing effects that are enhanced by PhysX you will see original version of the effect with GPU PhysX disabled. For effects that are created new as part of the GPU PhysX effort you will not see a fallback, because it did not exist in the original game.

Our goal is to work with developers to enhance their original game to take advantage of the latest hardware NVIDIA has to offer. We want to provide gamers that select NVIDIA a superior play experience for these games. We would not want to raise the min recommended specs for a game determined by the developer by adding additional default effects to the original game.

PhysXInfo.com: You work closely with developers – is exclusivity of GPU PhysX content to NVIDIA some kind of a barrier for PhysX adoption? In other words, are developers interested in OpenCL / DX Compute version of PhysX engine?

David Schoemehl: No, we have not seen this as a blocker for PhysX adoption in general. PhysX provides a strong set of core physics engine functionality across a wide array of platforms including PCs, consoles, and mobile devices. PhysX powers game engines such as UE3 and Unity, and can be found in many of the AAA titles that are shipping today.

PhysX 3 addresses memory, threading, and performance concerns, which should further increase the adoption rate of PhysX. In addition to this core functionality, PhysX and APEX offer hardware acceleration for certain features, such as particles, cloth, rigid bodies, and turbulence, through CUDA. This is a powerful value add but does not interfere with developers using core PhysX and APEX features.

PhysX engine can be found in many AAA titles

PhysXInfo.com: What is your impression on NVIDIA APEX toolset? Is it really simplifying process of adding PhysX effects to games?

Johnny Costello: I definitely think so. For example, look at where we’re heading with APEX tools like PhysXLab and the Clothing plug-in for 3dsMax and Maya. They are becoming more robust with each release and are definitely making it easier to create APEX content for games.

One of my favorite things about PhysXLab is the Playground Mode where you can preview how your mesh is going to fracture in real time before bringing it into a game engine and placing it into a map. This saves valuable time between making parameter changes and seeing those changes visually affecting the fractured mesh.

PhysXInfo.com: You have probably already worked with the new clothing simulation engine, introduced in PhysX 3. How well does it performs in comparison to current one?

Johnny Costello: The PhysX 3 clothing engine gives us a stronger set of features. More attributes allow the artists and animators to make better aesthetic choices regarding their cloth. One of these new features is the ability to created tapered capsule collision shapes. These shapes allow the artists and animators to create a collision representation that is more true to the characters silhouette.

The new system also allows for more reliable behavior during intense, fast-moving, animation sequences. In addition to these features, overall performance has been improved allowing developers to use clothing across more platforms.

PhysXInfo.com: What additional features you would like to see in APEX, as a technical artist?

Johnny Costello: As a technical artist, I spend a lot of time trying to decompose exciting artistic ideas down into their components so they can be created in games. What I’m looking forward to in the future with APEX is seeing various features come together for a combined effect.

What happens when turbulent dust is spawned when a destructible is fractured? Can a character’s clothing move when it gets hit with particles? I can’t wait to see all these things come together to make games even more dynamic and intense for players to experience.

Unreal Engine 3 includes robust PhysX Particle System

PhysXInfo.com: We have noticed that recent GPU PhysX titles, like Alice: Madness Returns or Batman: Arkham City are not using APEX Particles but built-in PhysX particles system instead – why is that? Isn’t the Particles module more effective?

David Schoemehl: Both of these games are built using UE3, which already had a robust particle editor using NVIDIA’s GPU PhysX particles. APEX provides some great features for particle systems but for these cases UE3 was already providing the functionality we needed.

APEX Particles are a win if you are stepping into project that doesn’t already have an existing PhysX particle pipeline or if you are interested in doing some simulations, such as turbulence, which require a great number of particles that don’t require the high-fidelity collision of PhysX particles.

PhysXInfo.com: Dark Void was the only title to impress us with awesome Turbulence smoke, why much newer games are still using good old SPH method for smoke and fog simulation?

David Schoemehl: The turbulence in Dark Void was added as a one-off feature for that specific game so that we could see how it would show in a game. While we feel that turbulence was an awesome feature we have been focused on improving APEX Clothing and Destruction, because that is what developers were telling us they needed.

However, we are pleased to say the APEX Turbulence module is now scheduled for the APEX 1.2 release in Q2 of this year. So we hope to see it appear in many games in the future.

PhysXInfo.com: Mafia II was the first title containing APEX Clothing engine. Do you think this “benefice” was successful? What difficulties have you faced during development?

David Schoemehl: Yes, the work done in Mafia II was invaluable for clothing. We learned so much about how to improve the tools and features for clothing from the work done on this game. The payoff was visible in later titles such as Batman: Arkham City where the time to create clothing and get it in game was drastically reduced.

Mafia II: first game to utilize APEX Clothing module

PhysXInfo.com: Batman: Arkham City also seems to be using APEX Clothing pretty extensively. Is it true that Clothing module is utilized not only as part of PhysX effects, but also for non-GPU accelerated clothing simulation, even on consoles?

David Schoemehl: It is true that clothing can be run on the GPU, CPU, and even consoles. However, for Batman APEX Clothing can only be seen on the PC running on either the CPU or GPU. It should be noted that APEX Clothing was also used for some hair simulation in the pre-rendered cutscenes that can be seen across all platforms.

Clothing performance on consoles is something which we have been focusing on improving with the PhysX 3 and APEX Clothing effort. We are seeing an increase in the number of developers wanting to get APEX Clothing into their console games so I would expect to start seeing this soon.

PhysXInfo.com: One of the most vibrant effects in both Batman titles – scenes containing GPU Rigid Bodies. How has this technology evolved since Arkham Asylum?

David Schoemehl: To be clear, GPU Rigid bodies were only featured in Batman: Arkham Asylum. They were not used in Batman: Arkham City. However, we have been making great progress with GPU Rigid Bodies with regards to performance and simulation stability.

They were last featured in the APEX Art Gallery demo [link] at GDC 2011, and they will be available to the public in APEX 1.1 very soon.

PhysXInfo.com: Another interesting scene – physically simulated banknotes in a bank vault. Are those all individual cloth pieces? How many of them are there?

Johnny Costello: Yes, those are all APEX cloth. During production, that was a really neat scene to watch come together. Initially we weren’t sure if the player would be able to see the characters interacting with the dollar bills since they are so small, so we added forcefields to Catwoman’s animations, and then the scene came alive in a big way.

It is definitely one of my favorite fights in the game. There were about 500 individual bills in that scene, which adds up to approximately 10,000 simulating vertices of APEX cloth.

Around 500 bills are scattered on the floor

PhysXInfo.com: You have worked on many GPU PhysX games, but which one is your favorite?

Johnny Costello: I have great memories of all of the game engagements that I’ve been involved with, but working on the Batman series has probably been the most memorable experience for me. I’ve been a Batman fan since I was a little kid, and I basically joined NVIDIA in 2009 and immediately started working on Batman: Arkham Asylum. That was pretty amazing.

And then I had the opportunity to work on Arkham City! I feel very lucky to have been involved with both.

PhysXInfo.com: We bet you are already working on PhysX content for future games. Will they be able to surprise us?

David Schoemehl: Yes, we are constantly on the lookout for upcoming titles that can be enhanced with PhysX and APEX features. On each title we work with developers to do something new or better than in previous titles. In addition, we are seeing a growing number of developers independently experimenting with APEX tools. This is particularly true of the UE3 APEX integration.

Our job on the PhysX Content Team is to show developers and gamers what NVIDIA technologies can bring to games and we measure our success by the ease at which developers can add the features and the response we see from gamers when they play games with PhysX effects enabled. We look forward to continuously improving tools for developers and helping them bring more cutting edge PhysX enhanced games in the future.

Our big thanks to PhysX Content Team for the interview !

It is time to summarize what PhysX Technology has achieved in year 2011, recall the most memorable events and releases.

. GAMES

GPU physics acceleration still can not gain enough momentum – only two games with support for GPU PhysX effects were released this year, this is the lowest result since Ageia was aquired.

One may call this an agony, but NVIDIA has told us that it was “conscious decision” – time was taken to develop and improve underlaying technology (PhysX SDK, APEX, DCC tools), thus sacrificing ability to create content and  integrate it into many games.

It was promised that we will see “more GPU PhysX games next year than you did this year” and even “a lot more in 2013″.

Meanwhile, both GPU PhysX titles released this year were pretty interesting by themselves:

• Batman: Arkham City, one of the best games with hardware PhysX support.
• Alice: Madness Returns, which is a decent game too and is certanly worth more than two Darkest of Days.

PhysX SDK as physics engine is still widely adopted by developers – over 45 PC console and games were released this year, according to our database.

. PHYSX SDK & TOOLS

Looking on the SDK Development you can say where all resources were spent – brand new PhysX SDK 3.0, rewritten from scratch, optimized and enhanced with new features, was released in Q2 2011, followed by SDK 3.1 and SDK 3.2 Beta. 6-months release schedule was introduced and so far is impeccably fulfilled.

PhysX 3 is a strong technological foundation, that will ensure further expansion, evolution and success of PhysX as physics engine.

NVIDIA APEX 1.0, high-level scalable framework build on top of PhysX SDK, was also revealed for public along with UDK integration, however it can not boast with same release dynamics – new APEX 1.1, promised to be delivered this autumn is now postponed till 2012. APEX 1.2, fully based on PhysX SDK 3, is also supposed to be released next year.

DCC PhysX plug-ins went throught three versions – 2.6, 2.61 and 2.7 – but during this period several compatibility problems and significant delays of releases were faced.

. MISCELLANEOUS

MassFX – new physics simulation solution, using PhysX SDK engine, was introduced in Autodesk 3ds Max 2012, thus replacing Reactor system, which was based on Havok physics. Rigid Body simulation functionality of MassFX was pretty strong along with better performance, however many users were unhappy with reduced functionality set in comparison to Reactor.

According to yearly survey by Game Developer Magazine, PhysX SDK is preferred physics middleware solution for traditional (big-budget) developers.

PhysX Research Team has showcased some new interesting technologies and prototypes. Some of them will appear in future versions of PhysX engine.

After a long break, new 1.05 version of Hybrid PhysX mod was released to support recent drivers and GPU PhysX games in AMD + NVIDIA configurations.

. . .

Well, that is all for now.

Happy New Year to everybody !

We have added a set of comparison PhysX screenshots for Batman: Arkham City, which in pair with previously released comparison video are completing our GPU PhysX Profile for this title.

You can view comparison screenhots, video and additional info at Batman: Arkham City – GPU PhysX Profile page .