Kunos Assetto Corsa CPU Occupancy > 99% Warning Advice

[Paul Jeffrey]

Kunos Simulazioni respond to recent CPU Occupancy > 99% issue with new advice for PC owners.

Following the popular update to build 1.12 of Assetto Corsa on Windows PC, Kunos Simulazioni have quickly realised a small proportion of users are suffering from a return of the CPU Occupancy > 99% issue that plagued many players during early builds of the game.

The return of the issue, attributed to amendments to the controls.ini file received in the latest build, has been acknowledged by the developers and advice has been issued on how to resolve this problem for the vast majority of players. With the update to the controls.ini file Kunos have brought to the game a more detailed FFB feeling for a number of wheel users, unfortunately this has caused problems for some players, especially those with older or home made wheel solutions. With the below advice issued today by Kunos the Italian team are confident any remaining CPU Occupancy issues will be resolved.

It is advisable to contact the official Assetto Corsa PC support forum if you still experience this issue after following the below steps.

FOR PC/WINDOWS USERS
With the new v1.12 update, we have introduced a new section in the "controls.ini" file located in your "Windows Documents\Assetto Corsa\cfg" path called "[FF_SKIP_STEPS]", that manages the force feedback update rate. The default value is now "0" instead of "1" and it overrides the old value located in the "assetto_corsa.ini" file (in the Steam game folder). This brings a more detailed force feedback and a better driving feeling. If you experience "CPU OCCUPANCY > 99%" warnings, please tick "Half FFB Update Rate" in the the UI Options -> Controls -> Advanced and this will bring the value back to "1". Not all the steering wheels can manage the maximum update rate, so no worries.

If you are using a very old steering wheel like the Microsoft Sidewinder or Saitek R440, or other hand-made ones, you need to open the "controls.ini" file, and set the "FF_SKIPS_STEPS" value to "4". It should look like this:

[FF_SKIP_STEPS]

VALUE=4

This should solve any "CPU OCCUPANCY > 99%" warnings related to the force feedback refresh rate.

Please always double check this value if you load controls profiles created before v1.12 update! In case, please create a new controls profile with the proper value!


Assetto Corsa is a racing simulation built for PC, Xbox One and PlayStation 4. The game is available to purchase now with a number of additional DLC packages available depending on the chosen platform.

The Assetto Corsa sub forum here at RaceDepartment is the place to go for Assetto Corsa news and community discussion. We have a whole bunch of mods to download, a specific area for modders to discuss their WIP projects and of course our epic Racing Club and League events. Head over and join in today.

Have you experience the 99% Occupancy issue? Does the above suggestion resolve your issues? What do you think of the 1.12 update? Let us know in the comments section below!

 

[M111555]

Also try this:

Assetto Corsa 1.3 brings a multithreaded physics engine which takes great benefit from multiple cores CPUs.

Unfortunately dual core CPUs might have performance issues with a high number of opponents and there is no easy workaround about that. We just recommend to upgrade to a multicore CPU even if it has a lower single core speed.

If you still have a dual core CPU, try setting

[THREADING]
USE_TIMER_PROCESS=0

in the assetto_corsa.ini file located in your Steam folder\steamapps\common\assettocorsa\system\cfg

For dual-core cpus users - please read

Assetto Corsa 1.3 brings a multithreaded physics engine which takes great benefit from multiple cores CPUs. Unfortunately dual core CPUs might have...

www.assettocorsa.net

 

[jeroenalmere]

Also try this:

For dual-core cpus users - please read

Assetto Corsa 1.3 brings a multithreaded physics engine which takes great benefit from multiple cores CPUs. Unfortunately dual core CPUs might have...

www.assettocorsa.net

this doesnt work, a new pc will.

 

[Deleted member 1578763]

i tried but nothing worked for me still saying WARNING CPU OCCUPANCY 99%

 

[MrAluminum]

i tried but nothing worked for me still saying WARNING CPU OCCUPANCY 99%

Did you ever figure this out? I have an i9 intel base clocked and RTX3070 and Fanatec DD1 system. I've had to give up on Assetto Corsa because of this dumb problem.

 

[Deleted member 1578763]

uuuuuhhhhh i don't know ?

 

[Stan]

Did you ever figure this out? I have an i9 intel base clocked and RTX3070 and Fanatec DD1 system. I've had to give up on Assetto Corsa because of this dumb problem.

never have seen that message yet on my actually computer, I have seen it with my old system often (i7 860, 16GB RAM, GTX970, Windows 7. On my new system I9 9900K, 32GB Ram and still the GTX970, Windows 10. It started with 10 opponents on the Nordschleife. Now I can run full Grid with 90 fps on start with all cars, when the field gets expand I'm back to 110- 120. My system runs stock, not overclocked. I run everything on max with an fps of 120- 130 fps in single driving.

Sometimes overclocking can cause really big problems like in Flight Simulator 2020, Arma 3 I run with overclocked GPU which gives 3-5 fps, sometimes it crashes with an green screen, but it never happens on stock settings.

 

[GARY B]

View attachment 173436
Kunos Simulazioni respond to recent CPU Occupancy > 99% issue with new advice for PC owners.

Following the popular update to build 1.12 of Assetto Corsa on Windows PC, Kunos Simulazioni have quickly realised a small proportion of users are suffering from a return of the CPU Occupancy > 99% issue that plagued many players during early builds of the game.

The return of the issue, attributed to amendments to the controls.ini file received in the latest build, has been acknowledged by the developers and advice has been issued on how to resolve this problem for the vast majority of players. With the update to the controls.ini file Kunos have brought to the game a more detailed FFB feeling for a number of wheel users, unfortunately this has caused problems for some players, especially those with older or home made wheel solutions. With the below advice issued today by Kunos the Italian team are confident any remaining CPU Occupancy issues will be resolved.

It is advisable to contact the official Assetto Corsa PC support forum if you still experience this issue after following the below steps.

FOR PC/WINDOWS USERS
With the new v1.12 update, we have introduced a new section in the "controls.ini" file located in your "Windows Documents\Assetto Corsa\cfg" path called "[FF_SKIP_STEPS]", that manages the force feedback update rate. The default value is now "0" instead of "1" and it overrides the old value located in the "assetto_corsa.ini" file (in the Steam game folder). This brings a more detailed force feedback and a better driving feeling. If you experience "CPU OCCUPANCY > 99%" warnings, please tick "Half FFB Update Rate" in the the UI Options -> Controls -> Advanced and this will bring the value back to "1". Not all the steering wheels can manage the maximum update rate, so no worries.

If you are using a very old steering wheel like the Microsoft Sidewinder or Saitek R440, or other hand-made ones, you need to open the "controls.ini" file, and set the "FF_SKIPS_STEPS" value to "4". It should look like this:

[FF_SKIP_STEPS]

VALUE=4

This should solve any "CPU OCCUPANCY > 99%" warnings related to the force feedback refresh rate.

Please always double check this value if you load controls profiles created before v1.12 update! In case, please create a new controls profile with the proper value!


Assetto Corsa is a racing simulation built for PC, Xbox One and PlayStation 4. The game is available to purchase now with a number of additional DLC packages available depending on the chosen platform.

View attachment 173438 View attachment 173439
View attachment 173440

The Assetto Corsa sub forum here at RaceDepartment is the place to go for Assetto Corsa news and community discussion. We have a whole bunch of mods to download, a specific area for modders to discuss their WIP projects and of course our epic Racing Club and League events. Head over and join in today.

Have you experience the 99% Occupancy issue? Does the above suggestion resolve your issues? What do you think of the 1.12 update? Let us know in the comments section below!

Hi how do I find this half FFB update rate , CPU OCCUPANCY > 99%" warnings, please tick "Half FFB Update Rate" in the the UI Options -> Controls -> Advanced and this will bring the value back to "1". Not all the steering wheels can manage the maximum update rate, so no worries.

 

[Dethrone1427]

Maybe this might help?

 

[RFBmwNZ]

i just started getting this is there any other fix? reinstalled csp changed ffb to 0 etc still not work. was working fine yesterday

 

[bryanguyend]

I don't trust the assetto corsa fps counter.

When i use MSI afterburner, it shows that only 18-20% of my CPU is used while Assetto corsa shows 3x as much.

mine shows like 15% cpu usage while AC keep pushing 100%. like what???

 

[Pfalzdriver]

And the one core AC uses will show near 100% too! You cant just check your overall cpu usage, bc AC uses only one core.

 

[Dethrone1427]

I've noticed using the 4gig patch that was floating around back in the day of RF1 works a treat with FPS, it seems to help as well with this issue

 

[Jempy]

Sure it's not rather a process manager ( Bill2's or Lasso ) than the 4gig patch ?
Those 2 are also helping GTR2 for the same kind of problem with 1 only core used for Fps ... so it might also do the trick for AC, I think.

 

[Alexandre Rain]

View attachment 173436
Kunos Simulazioni respond to recent CPU Occupancy > 99% issue with new advice for PC owners.

Following the popular update to build 1.12 of Assetto Corsa on Windows PC, Kunos Simulazioni have quickly realised a small proportion of users are suffering from a return of the CPU Occupancy > 99% issue that plagued many players during early builds of the game.

The return of the issue, attributed to amendments to the controls.ini file received in the latest build, has been acknowledged by the developers and advice has been issued on how to resolve this problem for the vast majority of players. With the update to the controls.ini file Kunos have brought to the game a more detailed FFB feeling for a number of wheel users, unfortunately this has caused problems for some players, especially those with older or home made wheel solutions. With the below advice issued today by Kunos the Italian team are confident any remaining CPU Occupancy issues will be resolved.

It is advisable to contact the official Assetto Corsa PC support forum if you still experience this issue after following the below steps.

FOR PC/WINDOWS USERS
With the new v1.12 update, we have introduced a new section in the "controls.ini" file located in your "Windows Documents\Assetto Corsa\cfg" path called "[FF_SKIP_STEPS]", that manages the force feedback update rate. The default value is now "0" instead of "1" and it overrides the old value located in the "assetto_corsa.ini" file (in the Steam game folder). This brings a more detailed force feedback and a better driving feeling. If you experience "CPU OCCUPANCY > 99%" warnings, please tick "Half FFB Update Rate" in the the UI Options -> Controls -> Advanced and this will bring the value back to "1". Not all the steering wheels can manage the maximum update rate, so no worries.

If you are using a very old steering wheel like the Microsoft Sidewinder or Saitek R440, or other hand-made ones, you need to open the "controls.ini" file, and set the "FF_SKIPS_STEPS" value to "4". It should look like this:

[FF_SKIP_STEPS]

VALUE=4

This should solve any "CPU OCCUPANCY > 99%" warnings related to the force feedback refresh rate.

Please always double check this value if you load controls profiles created before v1.12 update! In case, please create a new controls profile with the proper value!


Assetto Corsa is a racing simulation built for PC, Xbox One and PlayStation 4. The game is available to purchase now with a number of additional DLC packages available depending on the chosen platform.

View attachment 173438 View attachment 173439
View attachment 173440

The Assetto Corsa sub forum here at RaceDepartment is the place to go for Assetto Corsa news and community discussion. We have a whole bunch of mods to download, a specific area for modders to discuss their WIP projects and of course our epic Racing Club and League events. Head over and join in today.

Have you experience the 99% Occupancy issue? Does the above suggestion resolve your issues? What do you think of the 1.12 update? Let us know in the comments section below!

In my case it didn't solve it I keep having this CPU OCCUPANCY 99% problem. My processor is a Ryzen 3 2200G and my PC has 16GB of memory and an RX580 8GB video card

 

[Vintagedriver01]

In my case it didn't solve it I keep having this CPU OCCUPANCY 99% problem. My processor is a Ryzen 3 2200G and my PC has 16GB of memory and an RX580 8GB video card

And 1 core is reaching 90% ?

 

[CptEinsicht]

I have it from time to time. But i think that this is a Hardware problem on my side because my cpu really sucks.
Happens only with plenty opponents.

 

[Ricoow]

I want to rage so much. Freaking snowbanks.

 

[Stereo]

CPU at >99% in AC just means a single core is completely occupied, other programs (like windows task manager) report all cores combined so it would be 25% on a 4-core or 12% on 8-core.

 

[xnorb]

AFAIK Assetto Corsa, in contrary to most sims, uses actual physics calculation for AI, so the first advice should be to lower the number of AI drivers on the road.

When i run AC with 24 AIs on my i5 3550, all cores are pretty much melting

 

[Epistolarius]

I don't trust the assetto corsa fps counter.

When i use MSI afterburner, it shows that only 18-20% of my CPU is used while Assetto corsa shows 3x as much.

Because the one in AC doesn't show total CPU load/occupancy in the first place...

http://www.assettocorsa.net/forum/i...ics-and-ff-frequency.31453/page-4#post-667481

CPU value is for the graphics thread. It shows the relationship between the time spent in the application (CPU) and the time spent to complete a frame (FRAME TIME). Values of CPU near 100% indicate a CPU-bound system graphically.
EX... if a frame took 16ms to complete and CPU is 50% it means that AC was able to prepare the frame in 8ms.. and the GPU took 16ms to render it. (GPU bound).. if CPU is 100% then it took the CPU 16ms to prepare the frame and the GPU is probably capable to go faster (CPU bound).
No relationship whatsoever with the value read in task manager.

PHY is relative to the physics thread, values above 100% indicates that the system is not able to calculate the physics in time (3ms per step) and that the game is now running slower than realtime (slowmo). Practically means there are too many AI and the CPU is not able to handle it.