SOLVED CPU thread usage reaches maximum when using CSL DD >>> The cause was ReShade!

Daigo#47

Daigo#47

Registered
Recently, when I played rF2, the CPU thread usage rose to its maximum only when I connected CSL DD QR1 8Nm, and the FFB and AI car behavior became abnormal.
(The purple bar on Ctrl+C becomes full.)

When I turn off the CSL DD, the CPU usage drops back to normal levels.

I haven't made any changes to the rF2 settings.

I suspected that the issue might be caused by updates to the Fanatec driver or firmware, so I tried rolling back the updates, but it didn't improve the situation.

I also tried verifying Steam integrity, disconnecting and reconnecting the steering wheel, and changing the USB connection, but none of these resolved the issue.

After that, I changed the “use thread” setting in controller.json from true to false, and for some reason, the CPU usage dropped to around 60% and the system started functioning normally, though it's still high.

I am using a Core i9-14900KF.
Has anyone else experienced the same issue?
Are there any other solutions?
(I apologize for my poor English translation.)
 
Last edited:
Highlandwalker said:
There are new Fanatec drivers v469 and Fanlab v73, could help. Uninstall old driver before installing new driver.
Click to expand...
Thank you.
I tried updating to Fanatec drivers v469 (updated to wheel Base Firmware 1.5.1.1) and Fanalab v74 (the latest version), but the problem was not fixed.
The cause may be due to factors other than the wheel driver.
 
@Daigo#47 Which Build of rFactor 2 do you use?
If you use no Beta in the Steam Beta Selection of rFactor 2, try it with the Beta "previous-moddev", just to check if that changes something.
previous-moddev.jpg
 
DJCruicky said:
I don't have an answer for you, but does it happen with other racing games? or just rF2?
Click to expand...
Other than rF2, I haven't found any problems with connecting the CSL DD.
(However, I only own software with low CPU load, such as rF1, RBR, and KartKraft, so it may be that the problem simply hasn't surfaced.)
 
redapg said:
@Daigo#47 Which Build of rFactor 2 do you use?
If you use no Beta in the Steam Beta Selection of rFactor 2, try it with the Beta "previous-moddev", just to check if that changes something.
Click to expand...
That was a new perspective for me.
However, I tried “previous-moddev” and other betas, but the situation remained unchanged...
 
@Daigo#47 One Step, in such "unexplainable" Cases, should always be this:
Before you start the Game, rename the Folder ..\rFactor 2\UserData to Backup_UserData for Example.
Then start the Game, to get a fresh UserData Folder and check, if the Problem persists.
If yes, shut down the Game, delete the new UserData Folder and rename Backup_UserData into UserData, to get your original Settings back.
If the Problem is gone, you'll have some Work to do, to set everything as it was and also e.g. copy your stored Car Setups from the Folder ..\Backup_UserData\player\Settings to the new and empty Folder ..\UserData\player\Settings.
Good Luck, that you get it solved.
 
redapg said:
@Daigo#47 One Step, in such "unexplainable" Cases, should always be this:
Before you start the Game, rename the Folder ..\rFactor 2\UserData to Backup_UserData for Example.
Then start the Game, to get a fresh UserData Folder and check, if the Problem persists.
If yes, shut down the Game, delete the new UserData Folder and rename Backup_UserData into UserData, to get your original Settings back.
If the Problem is gone, you'll have some Work to do, to set everything as it was and also e.g. copy your stored Car Setups from the Folder ..\Backup_UserData\player\Settings to the new and empty Folder ..\UserData\player\Settings.
Good Luck, that you get it solved.
Click to expand...
Thank you for your perspective.
At first, it seemed that the problem was solved when I regenerated the UserData folder.
However, this was because CSL DD was no longer recognized due to the temporary loss of Controller.JSON and the Controller folder.
After restarting rF2 to make it recognize CSL DD and adjusting my button settings, the issue resurfaced…
Ultimately, the situation where rF2 recognizes CSL DD and causes CPU usage to spike remains unchanged.
The current workaround is to set “Use thread” in Controller.JSON to "false" and compromise with CPU usage at 60–70%.
This is not ideal, so I will continue to investigate further.
 
@Daigo#47
It's actually a "problem" with rfactor 2, it uses a lot of CPU for FFB on the racing wheels. I tested it with my G27 connected and disconnected, and the difference is huge!
Perhaps a possible suggestion would be to force/replace the FFB on the GPU?...
 
8Ball
Lethal

Thank you.
The fact that other steering wheels also have a very high CPU usage rate may be a problem specific to rF2.
In reality, I may not have noticed that my CSL DD had been operating at a high CPU usage rate until now, and it may have exceeded its limits due to some cause, causing the problem to surface.
 
Before this problem occurred, rF2 had not been updated, and rolling back Fanatec's drivers and firmware did not improve the situation, so the cause of the problem may be updates to Windows OS, BIOS, Java, or other applications. (Those were actually updated.)
 
Subsequent report.
Today, an update for my PC's BIOS was released (Alienware Aurora R16 System BIOS 2.18.0 > 2.19.0), so I updated it, but this BIOS update did not resolve the CPU overload issue caused by the racing wheel.
I will continue to investigate this issue.
 
You must log in or register to reply here.
Back
Top