Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I have seen it get as high as using 19-20gigs of system RAM while it was running, yet ive seen it as low as 8-9gigs as well, so im not sure what exactly calls for a 10gig variance, different tracks etc...
CPU never really gets above 25-30%.
No matter what settings i change in game, itll use MOST of the 11gigs on the video card, and this was something i noticed a lot of people found to be happening, that is no big deal and not causing the issue.
It is obviously set to utilise the cached memory for something, and seems to need a fair bit of it in my instance.
I found a heap of others complaining about this issue but no solution to it, so it isnt a one off, but id say it is one of those uncommon issues that 10% of players are seeing and will likely be a setting we have somewhere with something.
The only time it was occurring with me was when i would do a race at one track, then switch to another server after that race, and often it would crash within seconds of loading that next track. It would almost certainly do it if i went to a 3rd different track.
Whatever it is, so far, this seems to have stopped it occurring, and changing that setting did not impact anything else negatively anyway.
If i open up enough Chrome tabs i can fill the RAM up that way, no issues, or if i use OCCT i can test it and fill it that way, no issues, so whatever is going on this game seems to want to use cached memory for certain things.
OR if anyone knows WHY it is only happening to a small number of users and what is the cause, that would be helpful too.
I’ve had just one crash in ACC since it first came out in EA and, following some advice online, changed my virtual memory settings from manual to auto and it solved the problem. Auto was always seen as less than optimal in the past but, apparently, is much more efficient in Windows 10.
What screen resolution are you using? I use 1440p with 16GB of RAM and 8GB of VRAM and haven’t had a problem with either yet (mostly ultra or high settings in-game).
No screen resolution as such, i have the spectator mirror turned off as i am running in VR.
I have most settings on high and mid, some settings on epic, mirror res on low but increased the default range.
Rendered resolution is around 3416x3000 per eye. Occasionally get a bit below 80fps at the start of a race, usually sitting on a solid 90fps.
I have always set a fixed value, i like to know what is available space wise with that section allocated in case i need to adjust partition sizes later on.
Do you know what size your auto allocated amount reaches?
Just put together a new pc for ACC in VR with a 3080 so was not expecting any issues. It was constantly crashing with out of memory errors even thought it was not maxed out.
I manualy adjusted the page file and Bingo, no more crashing and epic vr settings.
I will post this on the Kunos forum as it should not be happening and will need a fix