Содержание
- Assetto corsa cpu occupancy 99 что делать
- Assetto corsa cpu occupancy 99 что делать
- Kunos Assetto Corsa CPU Occupancy > 99% Warning Advice
- Assetto corsa cpu occupancy 99 что делать
- Cpu occupancy 99 assetto corsa что это
- Cpu occupancy 99 assetto corsa что это
- Assetto Corsa
- Kunos Assetto Corsa CPU Occupancy > 99% Warning Advice
- Paul Jeffrey
- Paul Jeffrey
Assetto corsa cpu occupancy 99 что делать
Other than that, either look into overclocking options or just update your CPU.
Pawgy
Bunkiester
Do you get the 99 percent warning all the time ? Are you running SOL and the Shaders patch ? I’ve started getting that warning whenever I’ve had an accident since and there’s smoke present. If I’m patient, and just sit and curse for a few minutes the warning will go away. I can reduce the smoke effects in CM and make it stop, but I like the enhanced effects so haven’t bothered to change anything.
Don’t know if this helps at all — yes, that warning is somehow very aggravating!
Assetto corsa cpu occupancy 99 что делать
I was playing single player and this popped up at the top of the screen. Never have this problem in multiplayer.
Does anyone know what it means and how to fix it?
Thanks in advance.
12 окт. 2015 в 0:26 I got the same error of 99% CPU occupancy. When I unplug my racing wheel it disappears. Can’t get my MS FFW to work with this game!
running an fx4100 and not seen that before. i didnt extensively experiment with AI numbers though *shrug*
Kunos Assetto Corsa CPU Occupancy > 99% Warning Advice
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 DocumentsAssetto Corsacfg» 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:
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!
Assetto corsa cpu occupancy 99 что делать
I downloaded Assetto Corsa on Windows 10 just 2 days ago and it ran fine. I then formated my whole HDD’s and installed Windows 7. I downloaded and ran AC and as soon as I got to the track, it says ‘CPU OCCUPANCY
Источник
Cpu occupancy 99 assetto corsa что это
I was playing single player and this popped up at the top of the screen. Never have this problem in multiplayer.
Does anyone know what it means and how to fix it?
Thanks in advance.
I got the same error of 99% CPU occupancy. When I unplug my racing wheel it disappears. Can’t get my MS FFW to work with this game!
running an fx4100 and not seen that before. i didnt extensively experiment with AI numbers though *shrug*
edit: oh so wheels could cause it? sounds odd 😛
assetto_corsa.ini (located in Steamsteamappscommonassettocorsasystemcfg folder) about FORCE_FEEDBACK?
[FORCE_FEEDBACK]
MAX_FF_RATE_HZ= 60(change 350 t0 60hz)
assetto_corsa.ini (located in Steamsteamappscommonassettocorsasystemcfg folder) about FORCE_FEEDBACK?
[FORCE_FEEDBACK]
MAX_FF_RATE_HZ= 60(change 350 t0 60hz)
in my assetto_corsa.ini there is no MAX_FF_RATE_HZ=60 this ??
Thats because you posted in a thread from 2015 and Assetto Corsa has been updated several times since then and some things have changed.
Источник
Cpu occupancy 99 assetto corsa что это
Assetto Corsa
Change the following line to this:
in the assetto_corsa.ini file located in your Steam foldersteamappscommonassettocorsasystemcfg
Change in assetto_corsa.ini (Steamsteamappscommonassettocorsasystemcfg folder)
Solution!
There are 3 options that can fix a problem:
1) USE_TIMER_PROCESS=-1 / [PHYSICS_THREADING] THREADS=0
2) USE_TIMER_PROCESS=0 / [PHYSICS_THREADING] THREADS=-1
3) USE_TIMER_PROCESS=0 / [PHYSICS_THREADING] THREADS=0
I chosen the first and now it works! For now at least. Cpu load 60-75% on my old E8400.
Try it!
Solution!
There are 3 options that can fix a problem:
1) USE_TIMER_PROCESS=-1 / [PHYSICS_THREADING] THREADS=0
2) USE_TIMER_PROCESS=0 / [PHYSICS_THREADING] THREADS=-1
3) USE_TIMER_PROCESS=0 / [PHYSICS_THREADING] THREADS=0
I chosen the first and now it works! For now at least. Cpu load 60-75% on my old E8400.
Try it!
What work now? If you mean that you can drive alone in practice mode than yes it’s work. Try to put 5 + oponent and you will expirience slideshow. I just wont to please people to stop tolking that simple .ini change solve the problem, becouse they dont.
Both on 0 works fine for me!
What work now? If you mean that you can drive alone in practice mode than yes it’s work. Try to put 5 + oponent and you will expirience slideshow. I just wont to please people to stop tolking that simple .ini change solve the problem, becouse they dont.
What work now? If you mean that you can drive alone in practice mode than yes it’s work. Try to put 5 + oponent and you will expirience slideshow. I just wont to please people to stop tolking that simple .ini change solve the problem, becouse they dont.
Both on 0 works fine for me!
Both on 0 works fine for me!
Look if you race with ai oponent with dual core procesor, you will expirience 99 procesor usage an your game will safer. Online multiplayer give you some comfortabiliti but still it’s worse then before1.3update. Even developer confirm that you need 4 cores procesor for complete experience. So stop to scribe nontrue statment please.
Do you decide whats true or false? stop being dumb dude. play what you want, ITS FINE FOR ME! if its not for you buy a better pc.
Look if you race with ai oponent with dual core procesor, you will expirience 99 procesor usage an your game will safer. Online multiplayer give you some comfortabiliti but still it’s worse then before1.3update. Even developer confirm that you need 4 cores procesor for complete experience. So stop to scribe nontrue statment please.
Do you decide whats true or false? stop being dumb dude. play what you want, ITS FINE FOR ME! if its not for you buy a better pc.
Look if you race with ai oponent with dual core procesor, you will expirience 99 procesor usage an your game will safer. Online multiplayer give you some comfortabiliti but still it’s worse then before1.3update. Even developer confirm that you need 4 cores procesor for complete experience. So stop to scribe nontrue statment please.
Do you decide whats true or false? stop being dumb dude. play what you want, ITS FINE FOR ME! if its not for you buy a better pc.
Источник
Kunos Assetto Corsa CPU Occupancy > 99% Warning Advice
Paul Jeffrey
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 DocumentsAssetto Corsacfg» 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:
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!
Источник
- Thread Status:
-
Not open for further replies.
-
AC Support
Official Support
Staff Member
KS Dev TeamEN — ITALIANO A SEGUIRE
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 DocumentsAssetto Corsacfg» 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.
In case you are using very old or cheap steering wheels 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=4This should solve any «CPU OCCUPANCY > 99%» warning 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!Please advise: for any further assistance, refer to our official support forum: www.assettocorsa.net/forum
——————
IT
PER GLI UTENTI PC/WINDOWS
Con il nuovo update v1.12, abbiamo introdotto una nuova sezione all’interno del file «controls.ini» che si trova nella cartella «DocumentiAssetto Corsacfg» chiamata «[FF_SKIP_STEPS]», che gestisce la frequenza di aggiornamento del force feedback. Il valore di default è ora «0» invece di «1» e questa nuova sezione sovrascrive la vecchia contenuta nel file «assetto_corsa.ini» (nella cartella Steam del gioco). Il nuovo valore offre un force feedback più dettagliato e quindi un miglior feeling di guida. Se durante il gioco ricevi un messaggio di warning «CPU OCCUPANCY > 99%», per favore seleziona «Half FFB Update Rate» nel menu Opzioni -> Controlli -> Avanzato e ciò riporterà il suddetto valore a «1». Non tutti i volanti possono gestire il massimo rateo di aggiornamento del force feedback, quindi non c’è da preoccuparsi.
Nel caso si utilizzino volanti molto vecchi come il Microsoft Sidewinder o il Saitek R440, o ancora volanti artigianali, c’è bisogno di aprire il file «controls.ini» e settare il valore di «FF_SKIP_STEPS» a «4». La sezione dovrà essere come segue:[FF_SKIP_STEPS]
VALUE=4Ciò dovrebbe risolvere i problemi di «CPU OCCUPANCY > 99%» legati alla frequenza di aggiornamento del force feedback.
Per favore, controlla sempre questo valore nel caso si usino profili volanti creati precedentemente all’update 1.12! Nel caso, crea un nuovo profilo controlli con il valore corretto!Ricorda: per qualsiasi necessità di assistenza tecnica, visita il nostro forum ufficiale di supporto: www.assettocorsa.net/forum
- Thread Status:
-
Not open for further replies.
Share This Page
-
News
-
Forums
-
Sim Racing Games
-
Assetto Corsa
You should upgrade or use an alternative browser.
Kunos Assetto Corsa CPU Occupancy > 99% Warning Advice
-
Thread starterPaul Jeffrey
-
Start dateFeb 15, 2017
-
58 -
128931 -
-
Tags -
505 games
assetto corsa
kunos simulazioni
windows pc
-
-
#1
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 DocumentsAssetto Corsacfg» 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!
Last edited: Feb 15, 2017
-
#2
Happens only with plenty opponents.
-
#3
-
#4
When i use MSI afterburner, it shows that only 18-20% of my CPU is used while Assetto corsa shows 3x as much.
-
#6
-
#7
When i run AC with 24 AIs on my i5 3550, all cores are pretty much melting
-
#8
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.
-
#9
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.
Same here.
-
#10
-
#11
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.
Thats the idea though. When you have more opponents the cpu is more stressed and the FFB calculation will take it over the top and give you a warning. So if you did what the article suggest you might get away with not having the warning even with many AI.
-
#12
-
#13
I’m getting the «CPU Occupancy > 99% issue» error using the AccuForce wheel, i7 6800K 8/16 core processor, GTX 1070 and 32gb of RAM. WTH?!
Yeah but that’s all low grade material, you need beefier specs.
-
#14
I’m getting the «CPU Occupancy > 99% issue» error using the AccuForce wheel, i7 6800K 8/16 core processor, GTX 1070 and 32gb of RAM. WTH?!
That’s a 6core/12thread cpu btw. Regardless, that’s really wierd. My i5 @ 4.5ghz is usually in the 60s even with a huge grid.
PicoBp
#26 | HSRC — Banzaaaiii Touring Car Crew
-
#15
-
#16
«Wow, thanks. No one ever told me, or even mentioned on the forums that you have to «enable» multi core processors in Windows? found a video telling «how to enable multi core processors in Windows 10.» Kind of begs the question though. Why do my other games work fine, and report all 8 cores being used in MSI Afterburner? 36 AI on road America now work smooth as glass.thanks However only in AC was it a problem?»
so its just a suggestion to try out which has worked for someone in the past.. not sure if it was just because he had an 8 core amd or not..
…
Last edited: Feb 18, 2017
-
#17
-
#18
«Wow, thanks. No one ever told me, or even mentioned on the forums that you have to «enable» multi core processors in Windows? found a video telling «how to enable multi core processors in Windows 10.»
WOW thanks from me to, didn’t know that either… does that mean AC (and other games) can now use all 4 cores? Does that mean that having 4 cores enabled and I am just in windows, all 4 cores are running too and will kill my CPU faster? Some more explanations would be nice, very hard to understand what google is showing me as results. THX
-
#20
-
News
-
Forums
-
Sim Racing Games
-
Assetto Corsa
#81
snovart
-
- Забаненные
- Сообщений 1 003
Информация
Забанен
Отправлено 02 Апрель 2017 — 17:12
установил тимвивер
Димон, пиши в чате как будешь тут
#82
Den_mech
Den_mech
-
- Забаненные
- Сообщений 4 497
Информация
Предатель, Крыса
Отправлено 03 Апрель 2017 — 07:11
Из сообщения Паши:
CPU OCCUPANCY > 99%
Это ошибка я так понимаю говорит о максимальной загрузке процессора. И полазив по офф. форуму АС пришел к выводу
В Файле — controls.ini —> DocumentsAssetto Corsacfgcontrols.ini
в разделе — [FORCE_FEEDBACK]
в строке — FF_SKIP_STEPS
поставить — 1
В Файле — assetto_corsa.ini —> Steamsteamappscommonassettocorsasystemcfgassetto_corsa.ini
в разделе — [FORCE_FEEDBACK]
в строке — MAX_FF_RATE_HZ
поставить — 60
Это всё отвечает за частоту обсчета ФФБ руля (обратной связи). Проверьте эти параметры. Не знаю как они стоят по-умолчанию. Если другие, то ставьте эти, а потом проедьте пару кругов и посмотрите как будет ехать машина, хужелучше… 
FAQ
Вам потребуется 7zip для правильного извлечения zip-файлов.
Не используйте WinRAR или другие программы, так как они могут повредить файлы.
Скачать с официального источника: https://www.7-zip.org/
Также можно установить 7zip непосредственно в Content Manager. Для этого перейдите в Настройки — Контент Менеджер — Плагины и установите необходимый плагин.
Чтобы включить чат:
- Во время игры уведите курсор мыши в правую сторону экрана.
- Появится панель приложений, нажмите первый пункт и найдите приложение Chat.
- Появившееся окно чата вы можете перетащить в удобное для вас место.
Если после установки SOL мода в игре становится невыносимо яркая графика, перейдите в Настройки — Custom Shaders Patch — Lighting FX и установите значение Brightness (яркость) на 100%.
Если во время игры ваша камера отображает непонятные объекты или вы вовсе ничего не видите, сделайте следующее:
Проверяйте после каждого выполненного пункта, если сработает, не продолжайте.
- Обновите CSP до самой последней, доступной версии.
- Включите эффект постобработки в Настройки — Assetto Corsa — Графика.
- Деактивируйте Origin shift в Настройки — Custom Shaders Patch — Graphic Adjustments.
Чтобы отключить красные стрелочки, которые отображают оппонентов вокруг вас, перейдите в assettocorsasystemcfg
Найдите файл proximity_indicator и измените значение Hide на 1
Не на всех серверах доступна возможность изменения цвета авто.
Если вы играете на нашем сервере, сделайте следующее:
- Откройте приложение чата
- Нажмите на значок лампочки
- Выберите «change car color»
Стоит отметить, что не все автомобили поддерживают данную функцию.
Советы по снижению загрузки процессора и помощь с предупреждением о загрузке CPU на 99%
1. Включить оптимизацию CSP Полезная функция, которая реально помогает и не несет в себе никаких побочек.
Включаем здесь: Контент Менеджер — Настройки — Custom Shaders Patch — General Patch Settings
2. Измените силу обратной связи Если вы используете руль, в настройках игры можно уменьшить частоту обновления информации обратной связи. Теоретически это снизит силу обратной связи, но большинство рулей не передают информацию полностью, поэтому вы не заметите разницу.
Перейдите в Настройки — Assetto Corsa — Управление и установите значение на 1. Если ничего не изменилось, попробуйте все значения до 4.
Подробно можно прочитать здесь — https://www.racedepartment.com/threads/kunos-assetto-corsa-cpu-occupancy-99-warning-advice.131882/
3. Установите приоритет для Assetto Corsa Откройте диспетчер задач, щелкните правой кнопкой мыши по acs.exe и задайте для него приоритет реального времени. Если игра вылетает, попробуйте установить приоритет высокий.
Следует знать, что приоритет нужно будет выставлять после каждого запуска игры.
Чтобы сменить свой никнейм в игре, перейдите в Настройки — Контент Менеджер — Вождение и в блоке Имя игрока измените данные.
Мы рекомендуем привязать клавишу телепорта на пит-стоп. В случае если вы вылетите с трассы или вас резвернет, вы быстро сможете вернуться, не помешав другим игрокам.
Перейдите в Настройки — Assetto Corsa — Управление — Система и забиндите необходимую клавишу в параметр Teleport to pits.
В зависимости от времени года, CSP дает возможность использовать сезонные корректировки. Таким образом зимой можно получить зимние текстуры.
Чтобы включить или отключить снег:
- Перейдите в Настройки — Custom Shaders Patch — Weather FX.
- Поставьте галочку на пункте Use seasonal adjustments, если хотите включить параметр, если вам это не нужно, снимите галочку.
Эта страница исключительно для разбора всех вопросов по установке, запуску и настройке игры/модов.
Постарайтесь описать свою проблему максимально детально, наша команда и остальные участники постараются помочь решить ваш вопрос.
Posts: 7
Threads: 6
Joined: Dec 2018
Reputation:
0
Country: 
02-03-2019, 10:37 PM
(This post was last modified: 02-03-2019, 10:39 PM by Charley Rocha.)
Hello fellow drivers,
I know SRS is not responsible for Assetto Corsa itself, but I thought that maybe someone has had the same issue and knows the solution for it.
When I joined SRS this issue didn’t happen. I think that is because as my rating was low, I was thrown in the last servers with a few drivers. But as my rating increased, now I start in servers with more than 20 drivers, and then I get the annoying message «WARNING >99% CPU OCCUPANCY».
Although my processor is quite old, I’ve seen people with very good CPU facing the same problem in previous researches. Therefore, I am looking for the exact cause of this problem before spending 500 dollars on a hardware update.
My Specs:
Intel core i7 870 2,93GHz
AMD Radeon RX580 8GB
8GB RAM
Please, help me.
Posts: 236
Threads: 12
Joined: Dec 2018
Reputation:
45
Country: 
02-03-2019, 11:05 PM
(This post was last modified: 02-03-2019, 11:07 PM by Igor Relja.)
Try turning off post processing. If it doesn’t work, lower details, AA, resolution…
EDIT: but it usually depends on car/track combo. Some mods (cars and tracks alike) are not correctly made, so they aren’t optimized as they should be. So maybe you just had a bad luck with combo.
Posts: 7
Threads: 6
Joined: Dec 2018
Reputation:
0
Country:
THanks for the reply. I have tried with everything on the lowest already. The issue remains.
Interestingly, I have this issue mostly in Seat Leon/Road America Races. In Ford Sierra/Donington it doesn’t happen at all. It has fewer drivers, though.
Posts: 236
Threads: 12
Joined: Dec 2018
Reputation:
45
Country:
IDK, some mods are really messed up. For some reason, my PC doesn’t like RS 01. I’ve had same problem in first week, and just now. 99% occupancy, and I can’t even get out of pit. Everything else always works fine. Even RS worked without problems at Monza and Le Mans. But Road America and Sebring… whole different story. Cost me 2 DNFs and 20 rating. Even though, I have much weaker PC than you, ran everything fine, full grid on all other races. Every now and then small hiccup, but nothing gamebreaking like tonight (and 3 weeks ago). Now I’m affraid to drive in last two races of this championship. Even if I don’t kill anybody, I’m losing rating.
Long stroy short: I feel you, bro 
Posts: 71
Threads: 8
Joined: Jan 2019
Reputation:
10
Country: 
(02-04-2019, 08:37 PM)Igor Relja Wrote: IDK, some mods are really messed up. For some reason, my PC doesn’t like RS 01. I’ve had same problem in first week, and just now. 99% occupancy, and I can’t even get out of pit. Everything else always works fine. Even RS worked without problems at Monza and Le Mans. But Road America and Sebring… whole different story. Cost me 2 DNFs and 20 rating. Even though, I have much weaker PC than you, ran everything fine, full grid on all other races. Every now and then small hiccup, but nothing gamebreaking like tonight (and 3 weeks ago). Now I’m affraid to drive in last two races of this championship. Even if I don’t kill anybody, I’m losing rating.
Long stroy short: I feel you, bro
I don’t know if it can help but i always try the mods in a 20 AI race in single player to see if the PC handles it, theoretically a single player race uses more resources than a multiplayer one since the CPU has to calculate the AI (i don’t know if it’s true but at least for me in multiplayer i can handle more cars than single player, and i think is for the AI reason more than graphics related problems).
Posts: 236
Threads: 12
Joined: Dec 2018
Reputation:
45
Country:
Yeah, this is good advice for everybody. Unless they have a high end PC, ofc. Your reasoning is correct. It is more demanding for your PC to run AI, because then it has to simulate drivers too, while in online races it only has to show models and their positions. It’s like that in majority of games (e. g. CS:GO). So my suggestion for everybody who is on the edge is: don’t be stupid like me and test everything before race. Just do few laps with 20-ish grid and see if you get the warning even after the field is little spread out, you should probably skip that combo. My guess is that these two mods (RS01 and Seat), are not fully optimized (or maybe are just more detailed than others) so when they run into like track mod (Road America for example was also in first week of RS01 and last week of Seat), your PC can’t handle it. With that being said, I ran Seat without warning the first week on Paul Ricard WTCC, full grid.
Posts: 365
Threads: 12
Joined: Feb 2018
Reputation:
71
Country: 
I’m getting the CPU occupancy warning again (happened last summer too). From a quick search it seems to be an error specific to AC, and it happens when the PHY stat (physics engine?) in Render Stats is >100%. This can be seen in my screenshot here.
![[Image: bptipye.jpeg]](https://i.imgur.com/bptipye.jpeg)
But if I look at my Resource Monitor and NZXT monitor it shows low processor usage, low temp, low clock speed.
Is it possible AC is mislead to believe my CPU is choking? Or are the monitors not showing me the relevant performance metrics? Or (most likely) do I have no idea what I’m talking about?
One thing to note is that this is a summertime problem for me, when my room temps are 24C. The rest of the year my room is 18-22C and I don’t get this warning. That seems to support the diagnosis of a temp issue but then why isn’t NZXT showing that? And why is Resource Monitor showing all cores at 25% usage? What does ‘usage’ mean?
If my CPU really is overheating what’s the best way to cool it? I have i7 7700 running on the stock Intel cooler, a GTX1060-3GB and 16GB RAM. no case fan that I’m aware of.
Posts: 365
Threads: 12
Joined: Feb 2018
Reputation:
71
Country:
Update:
I threw an aftermarket cooler on my CPU and it seems to have cooled the chip significantly but I’m still getting a CPU occupancy warning. So clearly temp was not the major issue, if at all.
I figure it can only be due to poor single-core performance of my chip, even though it’s a high-end non-OC chip from 2017 and the game is from 2014…? In combination with perhaps a poorly optimized game and mostly a poorly optimized mod, it ends up being too much for my CPU.
In the future I will monitor the PHY output of the Render Stats overlay to figure out in advance if I’m going to reach my CPU bottleneck with a given car/track combo (110% in the example above). On another car/track combo I tried yesterday that also had 18 AI like in the earlier test, the PHY value was around 50%, and it was totally stable.
Posts: 16
Threads: 4
Joined: Dec 2020
Reputation:
3
Country: 
Hi,
I experienced a similar issue a few months ago and my work-around is in this thread:
https://www.simracingsystem.com/showthre…hlight=CPU
There is a link in there to show the steps of how to delete an entry and worth watching the YT video at the start of the thread too for a bit of background.
In addition to deleting the entry in the registry, I added acs.exe to the exclusion list in ‘HKEY_LOCAL_MACHINESOFTWAREMicrosoftFTH’. Before adding to the exclusion list, I have had to delete from the registry a couple of times but since adding to the exclusion list I haven’t seen it reappear.
Posts: 365
Threads: 12
Joined: Feb 2018
Reputation:
71
Country:
08-07-2021, 06:54 PM
(This post was last modified: 08-08-2021, 12:43 AM by Martin Smith.)
FIXED! (for both AC and ACC)
I came across this post on the AC forums <LINK> that describes issues with USB devices.
After disconnecting every USB thing I possibly could, including my keyboard, but leaving my Logitech wheel connected, the problem is gone. I reconnected the keyboard and the problem hasn’t returned so that leaves at least one of these 2 devices as the problem: Either my Logitech Wingman joystick, or my HyperX Cloud II earphones (I have it connected by 3.5mm jack instead of USB now).
I’ll try reconnecting one or the other to try and narrow down the problem but the point is that if you have this problem then have a look at your USB devices and drivers.
Whereas before the fix I couldn’t run more than 12-15 AI on certain mod tracks without getting the CPU Occupancy warning, now I can run 35 and more without problem. The PHY value in Render Stats still ends up in the 80-90% range with than many cars, but it works! I figure there’s still a problem with those tracks, as the default tracks and top-notch mods by lilski and JohnR never provoke that problem.
However I had this same problem last night with a massive grid on ACC for the first time (obviously all default content) so I frantically started yanking USB cables before the race start, and it fixed it. After I testing the fix in AC this morning to confirm the problem is gone there too.