Full course yellow game slow down

Whenever there is a full course yellow the game runs at 50% speed while frames per second seems to remain the same.
Is there a lot of pit logic processes going on that would cause this? I only have pit crews on for myself and this issue is consistent across every car and track option.
Keep up the good work. This game is amazing.

 

After FCY it runs normal again?
This is something I experienced several times. I use only pit crew for myself, too.
Curious:
This weekend, on oval with StockUSA at Gateway there was not this issue but with LMP1/GT1/GT2 on a road course at LagunaSeca it happened.

 

Yes, as soon as the FCY ends the game resumes at normal speed and smoothness.
Latest example was a dry/wet/dry race at Virginia with the GT1s.

 

Hello. I do have mods installed, but even classes without mods are affected by this issue. I do not use any career-application or other programs with AM2. I will verify cache in hopes this provides a solution. This issue was first experienced with the roll out of Version 1.6.9.5.

 

Hi, no, no mods or any app. Just the original unmodified AMS2.
I had this once at Nurburgring 2020 and last time at LagunaSeca.
I try to reproduce and make a more detailed report as soon as it happens again.
By the way, I reported it already when it happened the first time, see:
Bug Reports - Automobilista 2 (Read the Opening Post)

 

Seems my computer is too much of a potato, but the problem persists even after clearing cache.
Every FCY the game runs in slow motion while pit logic is being processed en masse. Green flag pit stops are unaffected, so it appears to be a bottleneck processing issue. My guess is that this issue arose as a consequence to ya'll implementing varied pit strategies to the field of cars (which is a must for variety's sake.)

I run all graphic settings on low for high frames with max grid. Tri Filter, 1 frame ahead, etc. (and the game still looks and runs amazingly, but I am an old time gamer.) I do use TAA (some clouds will have flickering, stagnant, black squares), but will try something else when I run again later with all mods removed using a class with fewer cars. I can run on medium, but the game will stutter, house lights will flicker, and the neighbor's dog will start barking.

 

by this do you mean verify game files through the Steam options?

 

I did some testing of this over the weekend, and I found that I got the FCY slow down issue only when I was running a large number of AI drivers.

With 32, for example, it didn't happen. With 48 it did.

My CPU is an older workstation CPU with 8 cores and 16 threads, but it likely doesn't have very good per core performance by current high end / gaming CPU standards. So I think what is happening is that the AI are pushing one or more of the threads close to using all compute resources available, and something extra that runs during the FCY pushes it past that point. That said, it's an intuition as no CPU core in the Windows Task Manager graph is shown as reaching 100%, but also there's no appreciable difference in GPU usage or other obvious metrics between normal running and FCY.

I tried this in the current non-beta build (V1.6.9.96) and an older build that was available on one of the beta branches (V1.6.9.81, which is from June). The issue happened in both builds, I don't have a build older than that available to try with. I feel like it was perhaps fractionally worse on the current build, but then there have been AI enhancements in those few months so it might make sense if the AI code required slightly more resources. Or it could just be an artefact of doing the test only once in each build - who knows what Windows background processes were off doing whatever they do during each of the tests *shrug*.

I've shared videos privately already.

Anyway, other people with the issue might want to try again with fewer AI drivers.

 

There is no need for a single core (or multiple ones) to be at 100% for a game to be CPU limited. It can become CPU limited way before reaching 100%, often at 50-60% for the core running the main thread.

 

Indeed, I guess my point is that there was no super obvious smoking gun like one or more cores going to solid 100% would have been.

Another thing in support of it being a CPU resource limitation - that I forgot to mention when I wrote up the above - was that I also found that I couldn't run as many AI without the issue when I was using the custom FFB file I usually use ("GWiz anti-float AMS2 Custom FFB file 1.1"). With that in use it was slow motion mode with 47 AI right from the off - without FCY. That's a fairly long file, so evidently it's relatively heavy to process.

 

So, this time with FCY after 50% race distance.
Track: Santa Cruz do Sul
Cars: P1 Gen2, GT3 Gen1, GT4 (no preset)
Race distance: 20 Minutes
Rain
(Above just for information because it happends with other cars/tracks/weather the same way)
During FCY, everything what is seen in yellow zone seems to slow down like under drugs. Its more unsharp and a bit of stucking, like missing frames or something like that. It's not smooth anymore.
But everything in red zone (cockpit) like the steering wheel, looking left/right/up/down, is smooth.


As soon as the FCY ends, everything is ok again, frames are smooth and clear.
At the end of the race there was a FCY again. Then it was unsharp and stucking again.
BUT: The race ended under FCY. As soon as I (myself) crossed the S/F line, the stucking and unsharpness passed and everything OK again.
Here my settings:



My system:

No apps are used instead of MoTeC i2 and the AMS2 logger v1.8.6 for MoTeC

 

This reminds me Marius, you asked me much the same question elsewhere: does the issue still happen after deleting the custom FFB file?

The answer is yes. For me the "heavy" custom FFB file only makes a difference if it is activated. If it exists in the documents folder but Default is in use then the behaviour is the same as if it is deleted before launching AMS2.

The only difference that particular custom FFB file makes is that it makes things worse when it's activated. The FCY issue (with enough AI) happens either way.

In short the custom FFB file thing doesn't seem to be related to the FCY issue.

 

Another race with GT1 (1998) at Interlagos 1993.
Scheduled FCY at 50% of race.
AI 31, => 32 cars with player
During FCY no issues, everything kept smooth.
The only difference beside the carset and track: Number of opponents instead of 47 now 31.
No custom FFB, Def+ is used.

 

This time:
-39 AIs at Hungaroring 2025 with GT3 Gen2 and FCY at 50% race distance. Everything perfect.
-43 AIs at RoadAtlanta Short 2005 with TVR (identical) and FCY at 50% race distance: Everything perfect
-47 AIs at RoadAtlanta Short 2005 with TVR (identical) and FCY at 50% race distance: stuttering, blurry, no clear view
Maybe a further test with 44, 45, 46 AIs