Mandatory Pit Stops and Min Tyres (Singleplayer)

I have the same problem, pretty much every car and track.

 

I noticed that the setting for the number of mandatory tyres rests back to 1, I can set it to 0 but it resets if I race (and get DQ'd) and go back in.

Going to put it out there that the issue is in the way that setting is saved (or not) over an in-race issue, where it's manifesting.

 

Hi mandatory pitstop seems to work fine now. Thanks Reiza

 

Not for me at Argentina 8 with the Inters.

 

Same here; Custom Championship; setting 1 mandatory pit stop; refueling allowed; 16 rounds; race 30 mins. First race Buenos Aries 15. Pitted after 8 laps, refueled, & got DSQ on the last damn lap, for not having completed a mandatory pit stop, which of course I did, on lap 8. Severely upset

 

Hi, hope you're well. Just want to say I got disqualified today in 45min race for not taking mandatory pitstop. I did pitstop however on lap 16, added some fuel and changed tyres. This is frustrating!

 

Same problem here! This is really frustrating and I don't need to say how disappointed I was!

 

Hi, hope you're well. Can we please get some advice on the progress of the work being done to fix this issue? Is there any workaround? Best regards

 

Same here

 

I think this problem was already fixed, no?

 

Just had same DQ issue in single player race with mandatory pit stop and tyre change set to 1.
I was DQ at start of last lap, AI not DQ’d.

Can someone from Reina please advise when this will be fixed and/or how to avoid it happening with mandatory pit stops?

 

Same here. I tried various options with ICM and button request including just arriving in the pit, with the same result, DQ'd on the last lap. What I did notice is even though I set min tyre/s to 1-4 in-game the race setting shows 0(zero) tyre/s required.
Edit: It feels like it is in the saving of the configuration of the championship. I start a new custom Championship and make it one race five laps only for each track ie Adelaide, Bathurst, Cadwell and Kyalami. First track mandatory pitstop with zero minimum tyres, second track mandatory with 4 tyres and so on. When I start the championship the first track is fine the second and thrid track shows all default setting with practice and qualifying selected and default race lengths

 

Same issue here. Single player against the AI. This is killing the fun for me. Sign says Pit In with no time left then DQ’d even though I pitted halfway through the race - and again at the end which destroyed the entire race anyways. I’m not at my PC, can we disable penalties and leave mandatory pit stops enabled? [EDIT]I have automatic pit stops enabled at the moment. And am not requesting a pit in any way. Just going in.

 

It’s a travesty, that this has still has not been patched; it’s an absolute immersion/game killer. I love this sim, I really do, but getting DSQ although you’ve pitted is a joke. Seriously, come devs, at least give us a heads up, that you’re looking into this!!!

 

My workaround:
Gameplay -> Flags & Penalties -> OFF
It ain’t a perfect solution, but it works.

 

I've been enjoying doing some spec races with both the Classic Mini Cooper as well as the JCW, and have had no issues with mandatory pit stops.

They've all been single races, not part of a championship. I've done races so far at Barcelona and Curitiba, 35 minutes in duration, 1 mandatory stop w/ 0 minimum tires. I have Pit Stop Request mapped to my wheel, and have used that each time prior to coming in. So clearly it is working in some situations. ‍

 

Don't think I have ever been dq'd in this manner before in a single race or championship

 

Same problem here... I think it worked just fine a few days ago... Pit stop always ends after 0,4-0,6s. Before the race pit stop was calculated in the menu with 900+s???
Few days ago pit stop times were just fine with 5-6s and i never got DQed. I didnt changed anything in pit stop strategys since then.

 

Got a workaround today. If i set a manual pit strategy with tire change to "all" everything works fine.
Didnt change anything there before... Maye a bug since 1.5.5?!