It’s likely that the OSW is refreshing at a higher rate than your g25, meaning it uses more CPU so you run out of CPU power. That or the simuCUBE open source firmware/software is using enough CPU to put you at the limit.
You could put
[FORCE_FEEDBACK]
FF_SKIP_STEPS=
to 1 in \Steam\steamapps\common\assettocorsa\system\cfg\assetto_corsa.ini
This would be the same as ticking the box, it will fix the problem, but obviously I don’t want to do it
I’m pretty sure my CPU is not running out of power, it’s a 6 core 4.4 GHz monster
I might send you a special build at the same time as I release the next version. For that, I will reduce the usb update rate to much lower value, to see if the issue is with that.
However, can you test one more thing:
Does the problem happen with this? In the “waiting for faults to clear” state, SimuCUBE is not sending any HID report updates to PC at all.
Edit: another way to test is to put the system to IONI Granity Configuration Mode and then launch a game - no usb reports are sent that way either.
Hello Emmett_Scully
I had that problem with Mmos too, it is not a problem related to simucube, my pc is also a beast and I also got the message: Warning CPU occupancy> 99%, I solved it by checking the box: Half ffb update rate
but I see that it does not work for you. It does not really affect your CPU, it’s a false message.
It seems that it really affects Emmett’s driving as he will get false starts etc.
To me only the message came out on the screen, but it did not affect me to the driving, maybe it is not related, or different errors, I hope that I solve it soon, sorry for the intromision.Cheers
To be clear, the half ffb rate option DOES work, but then I won’t have the same information, & can’t drive as fast
OK Mika, I’ve done exactly as you said.
I still get the message
Then its not related to SimuCUBE’s USB update rate either.
I and other people also had Mmos.
The CPU occupancy> 99% error message problem appeared for some wheels, including some OSW and Bodnar wheels, after the Assetto Corsa version 1.12 update. Many OSW owners had it. And this was long before the SimuCUBE beta Firmware was released.
The problem is solved, as you have found, and as recommended by Kunos, by ticking the half ffb rate box. For me, after a few months and before I went over to the SimuCUBE firmware, it resolved itself. I do not know how, but I no longer get the message if I do not tick the box.
I had that 99% CPU warning msg as well. I solved mine by updating my graphics card driver. You can give it a try.
I have everything up to date.
I hope this gets sorted out. I’d spend money to get it sorted, if I knew it would work.
Anyone for whom this is not a problem, maybe you could post your Simucube hardware version?
99% CPU warning is known and well documented in the AC forum and it is related to the force feedback refresh rate:
[FF_SKIP_STEPS]
VALUE=4
This should solve any “CPU OCCUPANCY > 99%” warnings.
There are no functional differences between each SimuCUBE hardware revision. Your issue seems to be just related to USB things, and those are exactly the same in all hardware versions.
That was the fix for very old or cheap steering wheels like the Microsoft Sidewinder or Saitek R440.
For OSW, ticking “Half FFB Update Rate” in the the UI Options -> Controls -> Advanced should do the job. It brings the “FF_SKIPS_STEPS” value back to “1”.
And not something I will do. There is way more noise with the lower rate.
Much more enjoyable with the full rate, and faster
Edit: And thanks to everyone who has helped with suggestions.
Hopefully we find out what’s going on
I have some problems stuttering with my triple screen SLI setup that have been getting worse.
It to some extent, seems to be related to nvidia driver update, but going back to older version makes it bit better but not all god. Yesterday I did an benchmark inside the came with this result:
AC VERSION: 1.15.2 (x64)
POINTS: 22237
FPS: AVG=151 MIN=32 MAX=263 VARIANCE=23 CPU=75%
LOADING TIME: 14s
GPU: NVIDIA GeForce GTX 1080 Ti (7680x1440)
OS-Version: 6.2.9200 () 0x100-0x1
CPU CORES: 8
FULLSCREEN: ON
AA:4X AF:16X SHDW:4096 BLUR:0
WORLD DETAIL: 5 SMOKE:3
PP: QLT:5 HDR:1 FXAA:1 GLR:5 DOF:5 RAYS:1 HEAT:100:
During this benchmark, the game play was very smooth with not even a slightest of stutter and got me thinking of alternative cause of the stutter.
Would it be possible for the SimuCube to cause stutter in-game or is that not even possible?
It shouldn’t be possible, but you can test by putting SimuCUBE into a state where it does not send any data to PC.
This can be accomplished by either
In either of these states, no USB reports are being sent to PC. Of course, you can’t drive with this, but it should be enough to see if there is stuttering or not.
ok thank you, now when i think about it, I have an old formula gt wheel i can plug in test if it changes anything.