Slightly Mad Studios may seem to be having a tough time facing accusations that they have sabotaged performance yield when their latest racing Sim ‘Project Cars’ is played and AMD Radeon GPU. This started out when it was indicated that Project Cars yielded the same amount frame rate with AMD Radeon R9 290X in the same lines of Nvidia GTX 760. Ouch!!

It escalated a bit when rumours started to circle that the sim is made using Nvidia ‘GameWorks’ and PhysX Technology.

For the past few days, erroneous information posted on Reddit and other websites has spread misinformation with regards to Project CARS’ performance on systems using AMD GPUs.

To correct the wrongful assumptions regarding Project CARS’ performance on AMD GPUs, the MADNESS engine and the degree of involvement from our third-party technical partners, Slightly Mad Studios feel compelled to point out the following facts:

Project Cars is not a GameWorks product. We have a good working relationship with nVidia, as we do with AMD, but we have our own render technology which covers everything we need.

NVidia are not “sponsors” of the project. The company has not received, and would not expect, financial assistance from third party hardware companies.

The Madness engine runs PhysX at only 50Hz and not at 600Hz as mentioned in several articles.

The Madness engine uses PhysX for collision detection and dynamic objects, which is a small part of the overall physics systems.

The Madness engine does not use PhysX for the SETA tyre model or for the chassis constraint solver (our two most expensive physics sub-systems).

The Madness engine does not use PhysX for the AI systems or for raycasting, we use a bespoke optimized solution for those.

The physics systems run completely independently of the rendering and main game threads and utilizes 2 cores at 600Hz.

The physics threading does not interact with the rendering, it is a push system sending updated positional information to the render bridge at 600Hz.

Any performance difference with PhysX would not be reflected with differences in comparing rendering frame rates. There is no interaction between PhysX and the rendering.

Overall, PhysX uses less than 10% of all physics thread CPU on PC. It is a very small part of the physics system so would not make a visual difference if run on the CPU or GPU.

Direct involvement with both nVidia and AMD has been fruitful in assisting with the game performance at various stages of development. Both AMD and nVidia have had access to working builds of the game throughout development, and they have both tested builds and reported their results and offered suggestions for performance improvements.

Testing of the game with different driver versions has produced a variety of performance results on both nVidia and AMD hardware. This is entirely to be expected as driver changes cannot always be tested on every game and every card, and this is the reason why both companies produce game-specific driver profiles, to ensure that they can get the best out of the game.

Project CARS does not use nVidia specific particle technology – the system we use is a modified version of the same technology we used on the Need for Speed: Shift and Shift Unleashed games, and was entirely developed in-house. The reason the performance drops when there are a lot of particles on screen is simply because processing a large number of particles is very expensive.”

Since then, the Reddit article is labelled as ‘misleading’. The Question now remains if AMD Radeon would release a new set of drivers. It’s has been more than 160 days since AMD released any new WHQL drivers, but it did release two BETA drivers since. The last updated one was Catalyst 14.12 Omega WHQL drivers which released on 09.12.2014. The BETA driver was made for optimizing Grand Theft Auto V and to add AMD Free Sync support.

But, on the other hand, many would question if Slightly Mad Studios should have even used PhysX engine in the first place. Would AMD release new drivers during/after AMD R9 390X launch? Your guess is as good as mine!

You can find out more about which cookies we are using or switch them off in settings.

Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Strictly Necessary Cookies

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.

disable

If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.