R.O.A.R. Before the 24 Jan 13-15

Aiming to enter the Fri 23:00 PST race with a Toyota GR86.

The plan was to run this the same way as the plan for the 2023 Daytona 24; track day comfortable pace, no risks, no incidents.

The race was going well enough until the pit stop. I'd been really careful on the start and opening laps with no incidents but a lost a lot of time to avoiding incidents ahead, especially T1 and Bus Stop and did rack up some Xs from minor wheel offs paying more attention the cars lapping me than car placement. Crew Chief Jim seems to be high much of the time with no clue what position I'm actually in but I think that I was P5 before the pit stop.

I knew within the 3 liters the perfect amount of fuel to add, I knew that tires were free with the fill amount, had practiced pit entries many times, had a safe braking marker and knew where my pit was, at least in official practice. Unfortunately, come race time, my pit was very close to the pit entrance and I blew right past it without enough fuel for another lap at race speed. At least two lessons learned there at the cost of P6 at worst. The extra stop and stretching 0.7 liters of fuel into a full lap put me down a lap but a comfortable if lonely P7.

That lasted for maybe 15 minutes when cars started disappearing, the "C" graphed maxed out in red and the "S" in the red as well. I maybe once have had issues with iRacing and overall very rarely do except whatever was going on with Windows 10 and rFactor 2 so I didn't reflexively know how to deal with it. I should have gotten off the racing line and pitted but instead I got plowed by a GT4 car right around start/finish, pretty much the fastest part of the track. Undriveable car but it often takes the next corner to be certain so another crash there to pad the incident count.

Tow + 11 minutes "optional repairs" + penalty for unsafe pit entry (mid-crash) gave me some time to try to figure out the WTF all of sudden. I declined a Windows update installation earlier (no thanks, my PC has no functional issues, thank you, fuck you and your updates that I can't turn off) maybe something with that. Started task manager looking for CPU and RAM useage. Fucking Windows Calendar @ 16% CPU use. The only calendar that I use the 2023 Mammoth Grid on my office wall, no clue WTF that app is running. I "paused" Windows update and uninstalled all the bloatware that I could and reduced some more graphical settings in iRacing, shut down Crew Chief and Teamspeak. Went back out, all systems golden until they weren't, got clipped by a TC car before T5 even though I moved as far to the right as possible. Another tow to go back to the pits and think. Between the relative display, watching the C meter and running on the apron when possible, I avoided any more incidents to at least cross the finish line. Very disappointing P12 in class, the last car running if I remember correctly. 

16X, -0.51 SR and -47 iR and I'm not doing the 24 this year, the 2.4 was too much wasted time and effort for basically zero fun nor sense of accomplishment.

As much as a race ender 1.5+ hours in is, I feel for you, it's worse to not even being able to race.

Do you have the "meter box" turned on, might help understand what's going on.




This is helpful:

boxthislap.org/framerate-matters/

My "C" was in the red as was probably the "S" when cars disappeared. The article above states that red S means imminent drop from the service.

C is CPU/GPU.


I, at the very least, probably contributed to the problem having turned up my graphics settings to see what that did to replay and overlooked the manual setting for number of cars which I think that I have had set to 10 since my last hiccups but it was 20 and I also had the RAM and GPU memory settings a little lower than optimum so that probably contributed some.


 I'll go back in today and ion addition to all of the low settings that I already have, turn off pit objects and somehow test, maybe with an AI race and the GT4 and TC cars which seem to be graphics intensive.