Project Cars?

I'm still trying to find the right settings for my G27.

Kicking up the tire FFB all the way up made a big difference. Karts felt great after that, but I found cars to feel very odd, very floaty. I almost felt like I was driving a hovercraft. Dropping from 900 to 540 degrees of rotation helped a lot, but it still doesn't feel quite right. It's kind of annoying that even with the game out, the WMD forums are locked. I'm sure there is a lot of very helpful information there, and I can't read it.
 
Need to know basis only... Don't repost these and get me shot?
Some of this stuff no longer works. So if you don't get favorable results I apologize.


http://imgur.com/sqOPCrD
http://imgur.com/IRjOaSh
http://imgur.com/s3usBSd
How much Deadzone Removal you should use depends entirely on your specific wheel, which is why it's left at 0 by default for all wheel models. Watch the FFB signal ingame on the telemetry hud and slowly increase the Deadzone Removal until you can feel even the weakest forces.

Below's a list of all keyboard shortcuts available in Project CARS.

The list gets updated whenever new shortcuts are being added.

Ctrl-I: AI control of player car.
Ctrl-T: switch to trackside cameras. Once in this mode + and - cycle through the cams.
[ ]: decrease/increase FOV.
F1: display developer menu.
BACKSPACE: goes back a level in F1 menu.
Ctrl-P: cycle to next post processing filter.
Ctrl-Shift-P: switch post processing filters off.
Ctrl-F: free camera.
Ctrl-S: display FPS (but with renderer debug overhead).
Alt-K: display FPS in HUD (instead of timer).
W,A,S,D: move seat
TAB: cycle lap info
Ctrl-+ & - (Numpad): Full damage/repair damage of car
Alt-+ & - (Numpad): Full damage/repair damage of all cars
shift-alt-H: toggle dirt build-up on cars
ctrl+shift+L: to toggle driving line
F12: take a TGA screenshot (TGA because it has no compression artifacts)
ctrl-F12: take a JPG screenshot

Freecam (CTRL + F)
Left mouse button + mouse movement: change camera direction
D: right
A: left
W: forward
S: backward

PgUp: up
PgDn: down

F: Toggle Controller bar HUD
CTRL+Shift+F: go to Controller Freecam
R: Change Car View.
CTRL+PGUP/PGDN: Change Car
CTRL+T: TV Cam mode
NumPad +\- : ZoomIn ZoomOut
Enter : Slowmotion (during live race)
P: Freeze/pause (only working on live race)
U:rewind
I:fast forward
J:Rewind to the begining of the replay
Tild: debug menu (Actually conflict a lot with onscreen menu keys like Enter key)
Shift/CTRL: Speed modifiers.

Build 396 and up:
Y/H: camera up/down
Q/E: camera movement speed
Z/C: roll camera left/right
CTRL + M: mouse smoothing on/off
NumPad 0: mouse speed scaling (turn rate proportional to square root of movement speed)

Numpad key actions continue working when ctrl or shift is pressed.

Camera Edit Mode (Build 159+)
To enter the mode you press Ctrl-K.
Then the following keys become active:

Numpad 2: increase pitch
Numpad 3: switch lights on/off
Numpad 8: decrease pitch
Numpad 4: increase yaw
Numpad 6: decrease yaw
Numpad 7: increase radius
Numpad 9: decrease radius
Numpad 1: increase roll
Numpad 3: decrease roll
Numpad -: increase FOV
Numpad +: decrease FOV
D: forward
A: backward
W: up
S: down
Q: left
E: right
SHIFT key in combination with any of the above: slow down camera movement
Numpad 5: reset to original settings for current camera

save/load of attached camera state:
Ctrl + F11 - save camera state to current slot
F11- load camera state from current slot
Alt + F11 - move to next slot (wrap to first slot when on last one) and load camera state
Shift + F11 - move to previous slot (wrap to last slot when on first one) and load camera state

There are 100 slots available (0 to 99). Current slot can be displayed on HUD instead of Laptime, by pressing Alt+K three times. Individual slots are stored in:

[User's Documents]\CARS\cameras\camera_[slot].dat (e.g. camera_42.dat)

Known issues/limitations:
- only cameras attached to vehicle are supported
- helmet cam is not loaded correctly

Press Ctrl K twice to get to 'Attached Free Cam' mode - the usual free cam controls will be available but the movement will be relative to your car.


Custom DOF mode:

F3: on/off
F4: reset

Focus plane distance:
F5: decrease
F6: increase

Sharp field depth:
F7: decrease
F8: increase

Transit to blur depth:
Shift + F7: decrease
Shift + F8: increase

Blur:
Shift + F5: decrease
Shift + F6: increase


Startup parameters:

Auto log-in /USERNAME "????" /PASSWORD "????"
Launch 32bit -x86
Single threaded -dx11st
DirectX 9 -dx9
Disable VR headset support -novr
Access additional cameras -devcameras
Remove crowds -skipcrowds
Disable join in progress (multiplayer) -disablejip

Number of physics threads
-pthreads 1 / -pthreads 2 / -pthreads 3 / -pthreads 4

Custom downsampling -windowsize 3500,2500
Change values as required. Press alt+enter to maximise.
Resolution reference list: http://en.wikipedia.org/wiki/List_of_common_resolutions

• x64 is default and uses multi-threading by default, this can be overridden with: -dx11st
• Single threaded may provide higher frame rates.
• Default physics threads = 2
 
Last edited:
I really need to clean my office space so I can setup my wheel...
 
There are some FFB tweakers on the forums if you'll want me to not share those also.
 
Have the AMD performance issues been fixed? Thinking about getting this from GMG but if my 290 won't run it up to par I won't be getting it.
 
cageymaru said:
Need to know basis only... Don't repost these and get me shot?
Some of this stuff no longer works. So if you don't get favorable results I apologize.


http://imgur.com/sqOPCrD
http://imgur.com/IRjOaSh
http://imgur.com/s3usBSd
How much Deadzone Removal you should use depends entirely on your specific wheel, which is why it's left at 0 by default for all wheel models. Watch the FFB signal ingame on the telemetry hud and slowly increase the Deadzone Removal until you can feel even the weakest forces.

Below's a list of all keyboard shortcuts available in Project CARS.

The list gets updated whenever new shortcuts are being added.

Ctrl-I: AI control of player car.
Ctrl-T: switch to trackside cameras. Once in this mode + and - cycle through the cams.
[ ]: decrease/increase FOV.
F1: display developer menu.
BACKSPACE: goes back a level in F1 menu.
Ctrl-P: cycle to next post processing filter.
Ctrl-Shift-P: switch post processing filters off.
Ctrl-F: free camera.
Ctrl-S: display FPS (but with renderer debug overhead).
Alt-K: display FPS in HUD (instead of timer).
W,A,S,D: move seat
TAB: cycle lap info
Ctrl-+ & - (Numpad): Full damage/repair damage of car
Alt-+ & - (Numpad): Full damage/repair damage of all cars
shift-alt-H: toggle dirt build-up on cars
ctrl+shift+L: to toggle driving line
F12: take a TGA screenshot (TGA because it has no compression artifacts)
ctrl-F12: take a JPG screenshot

Freecam (CTRL + F)
Left mouse button + mouse movement: change camera direction
D: right
A: left
W: forward
S: backward

PgUp: up
PgDn: down

F: Toggle Controller bar HUD
CTRL+Shift+F: go to Controller Freecam
R: Change Car View.
CTRL+PGUP/PGDN: Change Car
CTRL+T: TV Cam mode
NumPad +\- : ZoomIn ZoomOut
Enter : Slowmotion (during live race)
P: Freeze/pause (only working on live race)
U:rewind
I:fast forward
J:Rewind to the begining of the replay
Tild: debug menu (Actually conflict a lot with onscreen menu keys like Enter key)
Shift/CTRL: Speed modifiers.

Build 396 and up:
Y/H: camera up/down
Q/E: camera movement speed
Z/C: roll camera left/right
CTRL + M: mouse smoothing on/off
NumPad 0: mouse speed scaling (turn rate proportional to square root of movement speed)

Numpad key actions continue working when ctrl or shift is pressed.

Camera Edit Mode (Build 159+)
To enter the mode you press Ctrl-K.
Then the following keys become active:

Numpad 2: increase pitch
Numpad 3: switch lights on/off
Numpad 8: decrease pitch
Numpad 4: increase yaw
Numpad 6: decrease yaw
Numpad 7: increase radius
Numpad 9: decrease radius
Numpad 1: increase roll
Numpad 3: decrease roll
Numpad -: increase FOV
Numpad +: decrease FOV
D: forward
A: backward
W: up
S: down
Q: left
E: right
SHIFT key in combination with any of the above: slow down camera movement
Numpad 5: reset to original settings for current camera

save/load of attached camera state:
Ctrl + F11 - save camera state to current slot
F11- load camera state from current slot
Alt + F11 - move to next slot (wrap to first slot when on last one) and load camera state
Shift + F11 - move to previous slot (wrap to last slot when on first one) and load camera state

There are 100 slots available (0 to 99). Current slot can be displayed on HUD instead of Laptime, by pressing Alt+K three times. Individual slots are stored in:

[User's Documents]\CARS\cameras\camera_[slot].dat (e.g. camera_42.dat)

Known issues/limitations:
- only cameras attached to vehicle are supported
- helmet cam is not loaded correctly

Press Ctrl K twice to get to 'Attached Free Cam' mode - the usual free cam controls will be available but the movement will be relative to your car.


Custom DOF mode:

F3: on/off
F4: reset

Focus plane distance:
F5: decrease
F6: increase

Sharp field depth:
F7: decrease
F8: increase

Transit to blur depth:
Shift + F7: decrease
Shift + F8: increase

Blur:
Shift + F5: decrease
Shift + F6: increase


Startup parameters:

Auto log-in /USERNAME "????" /PASSWORD "????"
Launch 32bit -x86
Single threaded -dx11st
DirectX 9 -dx9
Disable VR headset support -novr
Access additional cameras -devcameras
Remove crowds -skipcrowds
Disable join in progress (multiplayer) -disablejip

Number of physics threads
-pthreads 1 / -pthreads 2 / -pthreads 3 / -pthreads 4

Custom downsampling -windowsize 3500,2500
Change values as required. Press alt+enter to maximise.
Resolution reference list: http://en.wikipedia.org/wiki/List_of_common_resolutions

• x64 is default and uses multi-threading by default, this can be overridden with: -dx11st
• Single threaded may provide higher frame rates.
• Default physics threads = 2
Click to expand...

This should be very helpful! Thanks!
 
Loser_guy said:
Have the AMD performance issues been fixed? Thinking about getting this from GMG but if my 290 won't run it up to par I won't be getting it.
Click to expand...

Well it's still behind Nvidia, and I don't want to speculate that it's going to get better with a new driver. New drivers typically take 1 month to create. Hopefully the [H]ardocp review crew will break the game down soon and comment on the subject of Nvidia vs AMD performance.

I will say that it's not nearly as bad as it was some months ago when I complained about it.
 
Loser_guy said:
Have the AMD performance issues been fixed? Thinking about getting this from GMG but if my 290 won't run it up to par I won't be getting it.
Click to expand...

Word is AMD is now able to work through the Gameworks created issues with the devs on this game. Still unknown how well they will be able to work through this probable minefield though.
 
Alright I'm in. 45 min download.

Is there any word on future car/track packs? Japan needs more representation in this game. At least Suzuka Speedway.
 
I know this has been a work in development for several years, and that there have been many beta builds, but for me it still has a ways to go. Case in point, I'm driving along and suddenly there is a lot of red splatter on the screen almost like blood from where I hit someone. It keeps flickering off and on and it is even reflected in the ocean. Secondly, I come to a curve and it starts randomly flipping my car. I even try taking the curve at 20 mph to no avail. Finally, it flips my car so badly, it won't even right itself and I have to abort the session. Weird anomalies like this make me wish I'd waited for a more stable build. :(
 
I had that red splatter and it looks to me like it's a video card/driver issue. I think it's linked to MSAA and shadows as it seems to mainly appear in the shadows cast down by the trees along the track. I fixed it by turning off MSAA and using only FXAA. I am not sure about water cause I was mainly running the Nordschleife.

The car flipping might be because you are using a game pad controller. If you are using a wheel I am not sure, I haven't plugged my G25 in yet and am using a PS4 Dual Shock 4. But the initial sensitivity for turning is like 50 and if it's that, it is WAY to high. I set it to 5 and it feels just about right for me otherwise I was spinning out like mad on corners and nearly going to the other side of the track on a straight part when doing a minor steering correction cause even minor movements seemed to jerk the wheel all the way left or right.
 
Is this game for real. I can't drive worth shit in this game with X360 controller or the Keyboard. Dafuq!
Any tips welcome. Even the assists in this game make the game even more difficult. Haven't driven a straight line for more than 5 seconds lol.

Waste of my money imo. I am not going to buy a wheel for this game.
 
Last edited:
KickAssCop said:
Is this game for real. I can't drive worth shit in this game with X360 controller or the Keyboard. Dafuq!
Any tips welcome. Even the assists in this game make the game even more difficult. Haven't driven a straight line for more than 5 seconds lol.

Waste of my money imo. I am not going to buy a wheel for this game.
Click to expand...
You don't need a wheel, but you really need to adjust the controller sensitivity it is set way to high on default. I know exactly what you are feeling cause I had the same exact issue when I started the game up. Set steering sensitivity in the options menu to 5. If you don't it's nearly impossible to even drive straight cause if you make a minor correction the game thinks you jerked the wheel all the way left or right.
 
Ok will try, thanks. Also not impressed with graphics either. Rain effects are passable and overall track etc graphics are OK. Nothing spectacular.
 
cageymaru said:
Roy tosses some mud on Twitter. Grabbing some popcorn.
https://twitter.com/amd_roy/status/596195800616603648

Not so angry
https://twitter.com/amd_roy/status/596301847666642944

Holding hands singing Kumbaya.
https://twitter.com/amd_roy/status/596361439016685569?s=09
Click to expand...
Part of me believes AMD is lazy and incompetent, and lets shit like this slip through the cracks because they aren't aware of the impending backlash. Part of me believes AMD can't possibly be that stupid. Another part of me knows this is a GameWorks title and I should ignore everything those devs are saying. Wouldn't put it past Nvidia to trash this game for AMD cards and then have the devs blame AMD. We already know GameWorks is shady.

Half the community will blame Nvidia/Slightly Mad. The other half will blame AMD. In the end, everyone who owns AMD still can't play this game regardless of who is at fault.

Isn't it kind of silly that every game these days needs a game-ready driver on day one? What the hell is happening.
 
Last edited:
KickAssCop said:
Is this game for real. I can't drive worth shit in this game with X360 controller or the Keyboard. Dafuq!
Any tips welcome. Even the assists in this game make the game even more difficult. Haven't driven a straight line for more than 5 seconds lol.

Waste of my money imo. I am not going to buy a wheel for this game.
Click to expand...

You need to play better :p I can win races with all assists off, manual gears on xbox controller... It is tricky though... Waiting for my G27 to arrive :D If you cannot race at all try using some assists until you get better, no fun with assists tho.

As said before also adjust your sensitivities and deadzones it will make it easier. You bought it knowing it was a sim type racing game so why are you complaining when it has sim type handing!

This game is just amazing to be honest... Couple of issues which should get patched but this has potential to be best racing game on PC.
 
Anyone have detailed layout on how to adjust Xbox 360 controller in terms of sensitivities, deadzones etc?
 
TaintedSquirrel said:
Part of me believes AMD is lazy and incompetent, and lets shit like this slip through the cracks because they aren't aware of the impending backlash. Part of me believes AMD can't possibly be that stupid. Another part of me knows this is a GameWorks title and I should ignore everything those devs are saying. Wouldn't put it past Nvidia to trash this game for AMD cards and then have the devs blame AMD. We already know GameWorks is shady.

Half the community will blame Nvidia/Slightly Mad. The other half will blame AMD. In the end, everyone who owns AMD still can't play this game regardless of who is at fault.

Isn't it kind of silly that every game these days needs a game-ready driver on day one? What the hell is happening.
Click to expand...

This isn't a troll, more of a vent of frustration...but I'm beginning to not remotely give a damn who's fault it is. The bottom-line is AMD users are continually left with big titles they can't play. There have been 3 big name games that I've wanted to play over the last 6 or 7 months: Far Cry 4, Dying Light, and now Project CARS. All 3 have had serious performance issues on the AMD side. It took them 3 months to release an updated driver after Omega that included the Crossfire fix for FC4. Dying Light still had Crossfire issues even after that driver release. I purchased a wheel almost specifically for Project CARS, and here I am left waiting for a driver for God knows how long. Gameworks or no Gameworks I'm sick of this. Very seriously considering just dumping my 290's and grabbing a sing 970 or something. Potential performance wouldn't be as good but at least things would be playable...
 
Dr3amCast said:
This isn't a troll, more of a vent of frustration...but I'm beginning to not remotely give a damn who's fault it is. The bottom-line is AMD users are continually left with big titles they can't play. There have been 3 big name games that I've wanted to play over the last 6 or 7 months: Far Cry 4, Dying Light, and now Project CARS. All 3 have had serious performance issues on the AMD side. It took them 3 months to release an updated driver after Omega that included the Crossfire fix for FC4. Dying Light still had Crossfire issues even after that driver release. I purchased a wheel almost specifically for Project CARS, and here I am left waiting for a driver for God knows how long. Gameworks or no Gameworks I'm sick of this. Very seriously considering just dumping my 290's and grabbing a sing 970 or something. Potential performance wouldn't be as good but at least things would be playable...
Click to expand...

You're reaction is exactly what Nvidia wants. Get ready for the future of no competition and premium pricing. The consumers are the ones that will suffer in the end if/when AMD goes under.
 
NickJames said:
You're reaction is exactly what Nvidia wants. Get ready for the future of no competition and premium pricing. The consumers are the ones that will suffer in the end if/when AMD goes under.
Click to expand...
So those of us who are willing to sacrifice our performance to continue supporting AMD are just supposed to take one for the team so everyone else can buy Nvidia? I don't know what people expect from the free market. We're not going to be your martyrs just so we can come on forums like this one and be told how stupid we are for buying AMD and then be told by the same people we should buy AMD to support competition. You can't have it both ways.

AMD has been colossally screwing the pooch the last year or so, even more than usual. It doesn't really matter whose fault it is. The only thing that matters in the end is performance and functionality. That's what decides where people put their money. EVEN IF Project Car's issues are entirely the devs' fault, it reflects poorly on AMD. People see benchmarks where AMD is putting out half the fps of their Nvidia competitor, so people will buy Nvidia. Rhetoric and finger-pointing aren't going to save AMD.

AMD needs to stop making excuses, I'm tired of excuses.
 
KickAssCop said:
Anyone have detailed layout on how to adjust Xbox 360 controller in terms of sensitivities, deadzones etc?
Click to expand...
Here are the settings I use. You'll want to play around with the controller filtering more than anything, I think.

Steering Deadzone: 10
Steering Sensitivity: 15
Throttle Deadzone: 10
Throttle Sensitivity: 50
Brake Deadzone: 10
Brake Sensitivity: 50
Speed Sensitivity: 65
Controller Sensitivity Filter: 70
Advanced: On
Soft Steering Dampening: On
Visual Wheel Filtering: Off
Opposite Lock Help: Off

cageymaru also posted a link to a guide on Steam. Those settings are not very good, though, in my opinion.

cageymaru said:
How to setup your controller for Project Cars.
http://steamcommunity.com/sharedfiles/filedetails/?id=353272300
Click to expand...
 
There are a ton of guides on the locked part of the forums. I'll try and snag a few tonight and post for you'll. They changed how the steering locks work so it's really hard to find a good guide nowadays because that change made them all obsolete. The thread with the controller guides in it is thousands of posts long. But I really like you guys so I'll see what I can dig up. :)

Oh and also did everyone find the Force Feedback ok? There are some profiles that the guys made on the forums that I can upload if someone needs them.
 
Last edited:
Armenius said:
Here are the settings I use. You'll want to play around with the controller filtering more than anything, I think.

Steering Deadzone: 10
Steering Sensitivity: 15
Throttle Deadzone: 10
Throttle Sensitivity: 50
Brake Deadzone: 10
Brake Sensitivity: 50
Speed Sensitivity: 65
Controller Sensitivity Filter: 70
Advanced: On
Soft Steering Dampening: On
Visual Wheel Filtering: Off
Opposite Lock Help: Off

cageymaru also posted a link to a guide on Steam. Those settings are not very good, though, in my opinion.
Click to expand...

The ones cageymaru linked works good for me. Better than default, at least. I'll try yours a bit later.
 
Armenius said:
Throttle Sensitivity: 50
Brake Sensitivity: 50
Click to expand...

You should be going the opposite way for this. The higher the number the more digital it becomes. In other words, you will have a harder time feathering the accel and brake. Set these to 0, so you have full use of your analog range. So when you press 25% of the trigger, it really is 25% throttle and not 100%. You hardly ever want to be 100% throttle with the extreme cars, especially McLaren F1. That ass will spin with the slightest mistake... Remember gentle, smooth motions.

I'm using Dualshock4, BTW.
 
TaintedSquirrel said:
So those of us who are willing to sacrifice our performance to continue supporting AMD are just supposed to take one for the team so everyone else can buy Nvidia? I don't know what people expect from the free market. We're not going to be your martyrs just so we can come on forums like this one and be told how stupid we are for buying AMD and then be told by the same people we should buy AMD to support competition. You can't have it both ways.

AMD has been colossally screwing the pooch the last year or so, even more than usual. It doesn't really matter whose fault it is. The only thing that matters in the end is performance and functionality. That's what decides where people put their money. EVEN IF Project Car's issues are entirely the devs' fault, it reflects poorly on AMD. People see benchmarks where AMD is putting out half the fps of their Nvidia competitor, so people will buy Nvidia. Rhetoric and finger-pointing aren't going to save AMD.

AMD needs to stop making excuses, I'm tired of excuses.
Click to expand...

Actually, if these are true words of Ian Bell, then it shows incompetence of AMD. No contact with dev since few months, ignoring issues, while SMS devs were reaching to work the problems. I suspect now it happened with all the other AAA.
http://steamcommunity.com/app/234630/discussions/0/613957600528900678/

And despite AMD having breakthrough hardware, they really should start working with devs. Noone will care for hbm, water cooling or small factor card, if said card will be getting less fps than 980 ti. I won't spend money on inferior product, just to keep its manufacturer afloat.
 
MorgothPl said:
Actually, if these are true words of Ian Bell, then it shows incompetence of AMD. No contact with dev since few months, ignoring issues, while SMS devs were reaching to work the problems. I suspect now it happened with all the other AAA.
http://steamcommunity.com/app/234630/discussions/0/613957600528900678/

And despite AMD having breakthrough hardware, they really should start working with devs. Noone will care for hbm, water cooling or small factor card, if said card will be getting less fps than 980 ti. I won't spend money on inferior product, just to keep its manufacturer afloat.
Click to expand...

Here is the real quote from Ian Bell.
http://hardforum.com/showpost.php?p=1041593386&postcount=59

Let me quote Ian Bell directly from the private SMS forums since he gave us permission to do so.

Ian Bell's post verbatim. 5/7/2015

"Of course.

Looking through company mails the last I can see they (AMD) talked to us was October of last year. I'm holding an internal investigation now as I'm seriously pissed at this allegation.

Categorically, Nvidia have not paid us a penny. They have though been very forthcoming with support and co-marketing work at their instigation.

Edit - More info below. Lot's of communications with them around March and more yesterday.

Gains that were made with an earlier driver they released were lost in a later release. Our internal analysis shows only very marginal gains available from our side (around 1%) with an excessive amount of work.

We've had emails back and forth with them yesterday also. I reiterate that this is mainly a driver issue but we'll obviously do anything we can from our side."

Some great gains we saw from an earlier driver they released have been lost in a later driver they released. So I'd say driver is where we start.

Again, if there's anything we can do we will.

I've now conducted my mini investigation and have seen lots of correspondence between AMD and ourselves as late as March and again yesterday.

The software render person says that AMD drivers create too much of a load on the CPU. The PhysX runs on the CPU in this game for AMD users. The PhysX makes 600 calculations per second on the CPU. Basically the AMD drivers + PhysX running at 600 calculations per second is killing performance in the game. The person responsible for it is freaking awesome. So I'm not angry. But this is the current workaround without all the sensationalism.

The best advice I can give while we work with AMD is to reduce settings which influence CPU load. Specifically in this order:

Shadow Detail -> Medium
Reflections -> Medium
Environment Map-> Medium
Car Detail -> Medium or High
 
cageymaru said:
Here is the real quote from Ian Bell.
http://hardforum.com/showpost.php?p=1041593386&postcount=59

Let me quote Ian Bell directly from the private SMS forums since he gave us permission to do so.

Ian Bell's post verbatim. 5/7/2015

"Of course.

Looking through company mails the last I can see they (AMD) talked to us was October of last year. I'm holding an internal investigation now as I'm seriously pissed at this allegation.

Categorically, Nvidia have not paid us a penny. They have though been very forthcoming with support and co-marketing work at their instigation.

Edit - More info below. Lot's of communications with them around March and more yesterday.

Gains that were made with an earlier driver they released were lost in a later release. Our internal analysis shows only very marginal gains available from our side (around 1%) with an excessive amount of work.

We've had emails back and forth with them yesterday also. I reiterate that this is mainly a driver issue but we'll obviously do anything we can from our side."

Some great gains we saw from an earlier driver they released have been lost in a later driver they released. So I'd say driver is where we start.

Again, if there's anything we can do we will.

I've now conducted my mini investigation and have seen lots of correspondence between AMD and ourselves as late as March and again yesterday.

The software render person says that AMD drivers create too much of a load on the CPU. The PhysX runs on the CPU in this game for AMD users. The PhysX makes 600 calculations per second on the CPU. Basically the AMD drivers + PhysX running at 600 calculations per second is killing performance in the game. The person responsible for it is freaking awesome. So I'm not angry. But this is the current workaround without all the sensationalism.

The best advice I can give while we work with AMD is to reduce settings which influence CPU load. Specifically in this order:

Shadow Detail -> Medium
Reflections -> Medium
Environment Map-> Medium
Car Detail -> Medium or High
Click to expand...

fuark. I love my lightnings but sometimes I just want to see AMD fail HARD. maybe then they will wake up. and then if they do go under, at least everything will be gameworks optimized :D. ugh, damn hodor of a card.
 
Last edited:
Any [H] members playing this with a wheel? Thinking of buying one, though not sure which model (looking at the g27).
 
TaintedSquirrel said:
Aside from Roy's useless tweets, any official word from AMD yet on why this was such a mess at launch?
Click to expand...

No, SMS and AMD are only interested in getting it fixed so that the customers can be happy. How it gets fixed is irrelevant. The longer it stays broken, the more lost sales.
 
You must log in or register to reply here.
Back
Top