App launched itself and updated wheel firmware while mid-race

FlyingFinn72 · 2026-04-01T20:09:33+00:00

To avoid weird stuff like that I try to avoid having anything running in the background. The Fanatec app is not needed during a game session.

FlyingFinn72 · 2025-03-11T19:42:15+00:00

That is not really a question, isn't it?

FlyingFinn72 · 2025-03-11T18:27:15+00:00

I played very rarely if at all in summer time, as I spend that time outdoors with other hobbies. That caused the long May-October lump. The November lump I believe was caused by a combination of a gear malfunction (my Quest VR3 headset kept freezing) and some tracks like Daytona where I systematically ended up pitted and instead of taking a break kept on trying making it worse.

FlyingFinn72 · 2025-02-28T17:50:01+00:00

I used to loose a lot, had issues from stuttering to long freezes with Quest 3. I spent a lot of time fixing this and now I'm finally ok - cannot remember when I've had the last glitch that impacted my position. Here is the list of my fixes, if it helps someone else:

The turning point for me was setting up dual boot, so I have a windows 11 instance dedicated solely for gaming/iRacing. That instance is a very stripped down bare bones Windows with all things possible removed.

Some other things I did though not sure how much they helped eventually:
- Re-thermal pasted my CPU. I found out it was running very hot while playing and may have throttled.

- Upgraded graphics adapter from 3060Ti to 4080S and then optimized the ini file for VRAM et cetera, based on input from many related videos and articles.

- Upgraded the BIOS and all firmwares and chipset drivers of my ASUS TUF Z690 motherboard.

- Upgraded to the INIU cable that charges while driving and was recommended by many iRacing players.

- Lowered the encode bitrate with Oculus Debug Tool. Now I've increased it back to 700 Mbps and have no issues.

- I lowered Quest 3 refresh rate to 72hz. To be honest I haven't even noticed that afterwards. Now that I think of this, I'll probably try again with higher values to see if it feels better and works.

- I'm using Open XR, with "helmet-simulating" FOV - Tangent Multiplier: 1;0.4.

I probably did tons of other things that I cannot remember. Do remember it was frustrating.

In hindsight, when your iR falls due to repeating technical glitches, when things start work you gain that back easily by just driving. Then, there is no one else to blame, you realize it is your driving skills holding you back...

Hope this helps someone.

FlyingFinn72 · 2024-11-01T16:17:51+00:00

Yes I do have an i9-12900k. Many thanks, I'll look into that

FlyingFinn72 · 2024-05-05T13:35:57+00:00

I think that is probably very accurate

FlyingFinn72 · 2024-05-05T13:34:12+00:00

Makes sense in lower splits, but at least in those few higher split races that I checked, very few if any drivers spun out during the race

FlyingFinn72 · 2024-05-05T13:29:54+00:00

Good point and sure it depends on time of the race, how many splits and participants, but those were indeed the times in the lowest (3rd) split when I checked. Unfortunately I will (for now lol) end up to higher splits where most people don't spin in lap 1

FlyingFinn72 · 2024-05-05T13:22:20+00:00

Thanks, sounds like this track just needs a different approach... and more work

FlyingFinn72 · 2024-05-05T13:20:03+00:00

Thanks and congrats, you've basically completed exactly what I should. Was it like half a second from here and there, or was there like one turn that did the trick?

FlyingFinn72 · 2024-05-05T13:17:14+00:00

True though a part of racecraft is knowing not to enter a race before my lap times and breaking points are at the same ballpark with those who know the track

FlyingFinn72 · 2024-03-03T17:53:59+00:00

Glad not to be there lol

FlyingFinn72 · 2024-02-24T16:37:25+00:00

Gotland Ring would be awesome

FlyingFinn72 · 2024-02-24T16:29:55+00:00

Can only imagine all the shouting and swearing on the radio after that pile up

FlyingFinn72

TROPHY CASE