• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Project cars benchmarks

Hud issue

Did a bit of a test on the HUD performance changing situation.

My specs.
AMD Phenom II X6 @ 4ghz, 8gb 1600 ram and an R9 280x @ 1100/1500.

It is indeed true (at least for me), the HUD does cause quite a massive FPS drop when its on - but only in certain views (in certain views you get the FPS drop no matter what). I did a few grabs comparing HUD on and off in 3rd person, complete clear view and 1st person (did this with and without mirrors - to see if they are the issue causing the drop when in in-car view).


The HUD is very clearly causing a massive hit in the framerate and GPU usage in 3rd person and clear view (again, at least for me), yet in 1st person (in fact any in-car view) you get the framerate hit and GPU usage drop aswell (so its not just the HUD, its the in-car model aswell, or at least something in it) - so to get the best FPS you need to play in 3rd person or clear view with no HUD - any other way/view seems to gets a major FPS/GPU usage hit.

http://www.neogaf.com/forum/showpost.php?p=163355431&postcount=66
 
So i have been reading from many sources and it seems that its the CPU Physx that is bring AMD to its knees, NV asked the developers to add more Physx at a later date which the consoles versions dont have and just to show its not all well it must be all AMD drivers fault.




http://steamcommunity.com/app/234630/discussions/0/613957600537550716/

So even with the highest realistically affordable NV setup the fps will tank if the PhysX runs on the CPU which AMD has no choice in.

Also a Physx poll running here and some good info.
http://forums.anandtech.com/showthread.php?t=2430693&page=12

So unless AMD can sort it out with their drivers then it is best if AMD owners avoid buying the game. Why reward the devs for providing a sub-par version for non-Nvidia cards?

I would personally wait until it hits the bargain basement before buying this crap.
 
So unless AMD can sort it out with their drivers then it is best if AMD owners avoid buying the game. Why reward the devs for providing a sub-par version for non-Nvidia cards?

I would personally wait until it hits the bargain basement before buying this crap.

Since when can AMD optimize GPU drivers for CPU PhysX ?, im sure that AMD can optimize other areas but CPU PhysX not a chance, the developer has to fix that.

And what you are quoting to is an NV user having the same issue because it was running on the CPU, if it bombs out on NV cards then it going to bomb on AMD when run on the CPU, so its clear that the GPU driver has nothing to do with the CPU PhysX.
 
Last edited:
Can someone else check running PhysX on the Cpu.

I'm noticing no real difference in performance.

2560x1440

Running [email protected] - TitanX SC@stock - 16Gb ram@ 2400

Settings used



I did that and recorded a session with GPU PhysX, then set the CP up for the CPU to deal with PhysX and ran the same lap with the same conditions. Everything is fully maxed out and at 1440P....


As you can see, there is no real difference between the 2 and by all accounts of what some are saying, performance should be tanking badly with the CPU handling the PhysX.
 
ndzlPXK.jpg


Conditions:
24 AI cars
Weather set to Clear
Map: Nordschleife
Pagani Zonda R
3:00PM

FRAPS benchmark log for one lap each. Though the max seems off.

My settings:
http://i.imgur.com/58QGrhy.png

Everything maxed besides motion blur off and SMAA was left on low. Honestly the game felt smooth both ways, but doesn't excuse the fps loss.
i7 3770k 4.5 GHz, MSI GTX770 4 GB
http://forums.anandtech.com/showpost.php?p=37389081&postcount=101

He has been asked to do it again with the Weather effects on as that uses Physx as well.
 
Last edited:
As you can see, there is no real difference between the 2 and by all accounts of what some are saying, performance should be tanking badly with the CPU handling the PhysX.


Thanks for running :)

I asked a few other to do the same and got the same result - little to no difference :confused:

Can't beat user results
 
Thanks for running :)

I asked a few other to do the same and got the same result - little to no difference :confused:

Can't beat user results

All my posts are user results and they are all NV users, everyone's setup is different and there are many factors to whether one setup is more effected than another including what OS its running on.
 
All my posts are user results and they are all NV users, everyone's setup is different and there are many factors to whether one setup is more effected than another including what OS its running on.

Hence why I asked others to check and post their findings. :)





But you did post this

So even with the highest realistically affordable NV setup the fps will tank if the PhysX runs on the CPU which AMD has no choice in.

These results prove otherwise.

The problem I see is, results will vary as no built in benchmark.
 
Last edited:
If a game has coded PhysX to run on the CPU, which I thought was the case for pCARS, can you really force it to run PhysX on an Nvidia GPU?

I know that option exists in the Nvidia Control Panel, but for it to have any affect an an app, doesn't the app have to be coded to allow the choice?
 
Hence why I asked others to check and post their findings. :)





But you did post this



These results prove otherwise.

The problem I see is, results will vary as no built in benchmark.

No your results dont prove otherwise, your results prove that its not a problem for your setup.
 
I don't even understand how the rain and other physx affects are that much of a performance hog. Driveclub on PS4 has much better physics and rain effects yet runs fine on an AMD apu .

It's obviously some gameworks features which affect AMD cards in a negative way are the problem. The devs are at fault here yet AMD gets the blame.

You have to be incompetant to fail to optimize the game for cpu physics when every other racing game in the past has had better handling and crash physics yet runs fine on old gen hardware. I'm sure the gran turismo series and Forza have better physics modeling.
 
If a game has coded PhysX to run on the CPU, which I thought was the case for pCARS, can you really force it to run PhysX on an Nvidia GPU?

I know that option exists in the Nvidia Control Panel, but for it to have any affect an an app, doesn't the app have to be coded to allow the choice?

No the game is not coded to only use the CPU for PhysX on the PC, by default any PhysX that can run on the CPU that can be GPU accelerated get GPU accelerated.
 
Last edited:
No the game is not coded to only use the CPU for PhysX on the PC.

Yes apparently in the past Physx was included as an option you could turn off bu twith gameworks it is usually always on. It only goes to cpu or gpu depending on what card you have.
 
I don't even understand how the rain and other physx affects are that much of a performance hog. Driveclub on PS4 has much better physics and rain effects yet runs fine on an AMD apu .

It's obviously some gameworks features which affect AMD cards in a negative way are the problem. The devs are at fault here yet AMD gets the blame.

You have to be incompetent to fail to optimize the game for cpu physics when every other racing game in the past has had better handling and crash physics yet runs fine on old gen hardware. I'm sure the gran turismo series and Forza have better physics modeling.

Hence why its not a problem on Consoles as they have to optimize all of the physics for the CPU.
 
Yes apparently in the past Physx was included as an option you could turn off bu twith gameworks it is usually always on. It only goes to cpu or gpu depending on what card you have.

Indeed, but there are some effects that can be turned off which use Physx, but you can avoid it entirely.
 
Last edited:
Back
Top Bottom