Welcome, Guest
Username: Password: Remember me
"City Car Driving" general discussion forum for English users
  • Page:
  • 1

TOPIC: Low frame rate (15 fps) with driving wheel

Low frame rate (15 fps) with driving wheel 11 Mar 2020 09:20 #113951

Hey, all.

I've been trying to figure out how to get CCD to run at higher than 15 fps for the past week, upgrading from my R9 390 to an RX 5700 XT and overclocking my i7 4790k to 4.7 GHz. Neither of these seemed to improve the frame rate at all. Then I ran free driving with just the monitor and VR as output, no wheel plugged in, and saw that the game ran smoothly at 57-60 fps! I tested this variable by plugging the wheel into a usb port and unplugging it and seeing how the frame rate changes. Sure enough, when the wheel is connected to my pc, the frame rate drops to an average of 15 frames per second while driving, and from 1-7 fps inside the menus, and when the wheel is unplugged, the fps ranges from 56-60 frames per second in both driving mode and inside the menus. I tried doing this with all the usb ports at the top of my case and directly connected behind the motherboard. The firmware for my wheel and driver for my video card are also updated to their latest versions.

I looked around to see if anyone else had this issue where the frame rate dropped for their game when a driving wheel was plugged into their pc and found several cases with logitech, microsoft, and thrustmaster wheels:

So, when I was playing F1 2015 I had this problem where if I plug my G27 in I would loose fps and the game started this micro stutter thing just like Dirt rally. So I did the same thing, I unplugged my G27 and MAGIC! Without the wheel plugged in to my computer I have a stable 60+fps with no micro stutter, not even once! Then i plugged my controller in to the same game without quitting or changing anything and there it goes again , micro stutter and fps loss.

I just noticed that everything runs "normal" if I changed the input method to keyboard only. But when I choose the Wheel, then the game runs in "slow motion".

Plugged in my trusty old Microsoft Sidewinder Forcefeedback Wheel and started the game. Everything went well until I touched the wheel to turn: My FPS started plummeting faster than a plane without wings.

I have a Microsoft Sidewinder ForceFeedback Wheel and it worked great with The Crew 1 after a xml WaitRate edit (details below).

Sadly the Crew 2 does no longer Provide the ExtraConfig.xml in the Documents Folder to Setup the FFB driver refresh rate.

This causes massive FPS drops to max 1 FPS as soon an I move my Steering Wheel.

As I was lowering graphics settings, trying to prevent the FPS from dropping below the refresh rate of my monitor (75), I discovered that there was a significant difference with and without my steering wheel connected (Logitech G920). I tested it multiple times using Fraps in identical scenarios (standing still at a race start) with identical graphics settings. With the wheel connected the average fps was 64 and without the wheel it was 80. It would also drop further, by 2-3 FPS, when I would rotate the wheel.


The following sums up the cause of the problem pretty well:
Too much in form of signals per second is correct. Not too much FFB strength, this is irrelevant. If the strength is to high then the FFB simply clips, which is although annoying but you'll get no stuttering i quess, because the game could send the signals

You can configure the refresh rate with
Tire physics is refreshed at 300hz, so a rate of 1 will update the FFB at 300hz too, a rate of 2 with refresh at 150hz. etc..
Some FFB driver can’t handle high refresh rate, if you experience frame rate issue with FFB wheel, increase this value to reduce the Refresh Rate.

the slow down is this anti lag technology which i cant remember the name of for the life of me. Basically when the cpu gets overwhelmed it will reduce the rate of simulation hence slowing the game physics down, the physics are drawn from the wheel hence the wheel animation isnt effected. this means that instead of getting slapped down from 200 fps to 10 you get a smooth transition from slowdown to standard speed. it works extremely well in some games like AC or minecraft for example however in extreme cases with constant <99% cpu usage it doesnt really help.


For Assetto Corsa, there is a config file that allows for the modification of the force feedback rate:

update: setting ffb to 120 did "fix" the problem! Thanks for this tip. Never would have found it on my own

MAX_FF_RATE_HZ=120 ;350


tl;dr The frame rate for CCD drops to a max of 15 fps when my Thrustmaster T300 is plugged in, and it seems like the reason this happens is the force feedback refresh rate being too high. Is there any configuration file or setting that allows for setting the FFB rate for CCD?
The administrator has disabled public write access.

Low frame rate (15 fps) with driving wheel 13 Mar 2020 08:51 #113956

  • Kivlov
  • Kivlov's Avatar
  • Developer
  • Posts: 262
  • Thank you received: 32

Have you tried updating your wheel driver?

Also quite often perfomance problems may be result of the game configuration files overflow and sometimes – third-party mods also may ruin the performance too.

Therefore, first of all try these steps:

1. Unsubscribe from all mods.

2. Uninstall the game in Steam.

3. Manually delete the folder, where the game has been installed (it will remain after uninstallation) – …\Steam\SteamApps\common\City Car Driving

4. Turn off the Steam cloud profile synchronization for City Car Driving – open your Steam client, click on City Car Driving with right mouse button and choose “Properties” from the context menu. Then open the tab “Updates” and there turn off the option “Enable Steam Cloud synchronization for City Car Driving”.

5. Delete the folder "Forward Development" from your "My Documents" folder.

6. Install the game again.

7. After all above turn off Vertical Sync in both places - the game settings and your video card settings.
The administrator has disabled public write access.

Low frame rate (15 fps) with driving wheel 14 Mar 2020 15:34 #113961

Alright, I will be trying your suggestions.

I have updated my wheel to its latest driver and firmware versions.

1. I have no mods installed, so this was easy.
2. Uninstalled from Steam.
3. There was no City Car Driving folder in …\Steam\SteamApps\common\ after the Steam uninstall.
4. Already turned off Steam cloud synchronization
5. Deleted Forward Development folder in My Documents
6. Installed the game again.
7. V-synch is set to off in the game settings and in my Radeon settings.


The game still caps at 15 fps with the Thrustmaster T300 wheel plugged in.

When I unplug the wheel I get up to 177 fps.

It really seems like the problem is with the way the game interacts with the wheel. I found a page on the Thrustmaster site which says the way games and wheels interact is based on the way the game developer scripts the game: support.thrustmaster.com/en/kb/6030-en/

When I play Assetto Corsa with the wheel plugged in, I get a max of 381 fps.

Note that Assetto Corsa has an option to halve the FFB update rate.

Last Edit: 14 Mar 2020 16:38 by WakerDrives.
The administrator has disabled public write access.

Low frame rate (15 fps) with driving wheel 16 Mar 2020 08:53 #113969

  • Kivlov
  • Kivlov's Avatar
  • Developer
  • Posts: 262
  • Thank you received: 32

Please email our technical support team to This e-mail address is being protected from spambots. You need JavaScript enabled to view it and in your email please send us the following information:

1. Your order ID or serial number to identify you as our customer. Or your Steam account name (if you purchased the game in Steam).

2. Send us your settings files. To send us these files, you should compress the whole folder with game settings ("My Documents\Forward Development" folder.) in archive file and send us.

3. Your wheel drivers version# and your wheel firmware version#.

4. Attach a DirectX diagnostic file from your PC, where the problem occurs. To create this file, please, follow these steps:

● From your Windows click the "Start" button and use the search box field.
● Type DXDIAG in the field and hit Enter.
● DXDIAG will start, and may display a prompt that begins "Do you want to allow DxDiag to check if your drivers are digitally signed..." Answer "Yes" to this query if it appears.
● A window entitled "DirectX Diagnostic Tool" appears, and in the lower left corner, a progress meter begins to advance towards the right as DXDIAG collects information relating to the system's hardware and Windows component configuration.
● When the progress indicator disappears, hit the "Save All Information" button. Then save this file as DXDIAG.TXT where it can be easily located. By default DXDIAG will place this file on your Desktop. Then send this file to us.

We will research all this information and then will advise you next steps.

Note: If you do not see a button that allows you to save the information, you will need to log on to Windows as the Administrator.
The administrator has disabled public write access.

Low frame rate (15 fps) with driving wheel 19 Mar 2020 10:24 #113979

Email with all info sent. Hope you figure it out.
The administrator has disabled public write access.
  • Page:
  • 1
Time to create page: 0.121 seconds