PLZ do better Schedule in dailys

Thanks for your support on the matter!

Regarding your suggestions:

Beginners:
I’ll stick with my proposal of 2/6/20 min (practice/qualy/race),
except for Le Mans and Spa, where I agree with your timing — 2/7/18.
That still keeps the total around 30–35 minutes, as you mentioned.

Intermediate:
  • LMHY (solo): I agree — more driving time is good for this class.
    If they stick with solo runs, the times above (2/6/20 or 2/7/18) should work fine.
  • LMP2 + GTx multiclass: I’d say 2/10/40 works well — gives you that ~58-minute format.
As for scheduling, I’d suggest something like:
  • Start 12:00 – LMHY
  • Then 12:45 – LMP2+GTx
  • Then again 13:50 or 14:00 – LMHY
Basically: two races every 2 hours — one of each type.
(Assuming the 35 + 58 minute durations you mentioned.)

Advanced:
Nothing to add there — fully agree.
 
llisep said:
except for Le Mans and Spa, where I agree with your timing — 2/7/18.
Click to expand...
At Le Mans this wouldn't change anything - it would still be a 5-lap race
At Spa you are reducing the total event time against my proposal by 1 minute, and reducing the race distance by one lap, so gaining around 82 seconds in total. Not sure if that it's really worthwhile complicating things. It's not as if it would be really tight to make the next race. Even finishing 60sec behind the winner with the leader averaging 2m25s you would complete the event in under 36 minutes.

Chuck in some wet weather and it maybe could get a bit messy at the longer tracks though!

20, 30 or 40 mins would work for LMHY Intermediate without really affecting race-hoppers. In fact 30 mins would mean aligning all Inter races onto the 00 or 30 min mark which would leave approx 15 mins between events. I just kept everything at 40 mins for simplicity. There's no reason not to put a LMHY into Beginners once in a while (not that you will find me there!)
 
I reduced 1 min from practice because, in my opinion, 3 min is too much.

I understand and even agree with your use of the 40 min for simplicity. However, I tried to base my timings on what's currently implemented in the game, and adjust accordingly. Just to clarify, I never suggested LMHY should be in the Beginner tier — the 35 min duration I mentioned is simply the existing event length.

Regarding Spa, I may have misread your post — if so, my apologies. I actually used your suggested times without cutting anything from your qualifying or race durations.

Also, we must consider that tracks like Spa and Le Mans require an additional ~6m20s and ~9m30s respectively, due to extra qualifying and race laps, plus the formation lap.

I know we're now micromanaging the scheduling — but I think it's good we're considering the practical implications.
 
llisep said:
I reduced 1 min from practice because, in my opinion, 3 min is too much.

I understand and even agree with your use of the 40 min for simplicity. However, I tried to base my timings on what's currently implemented in the game, and adjust accordingly. Just to clarify, I never suggested LMHY should be in the Beginner tier — the 35 min duration I mentioned is simply the existing event length.

Regarding Spa, I may have misread your post — if so, my apologies. I actually used your suggested times without cutting anything from your qualifying or race durations.

Also, we must consider that tracks like Spa and Le Mans require an additional ~6m20s and ~9m30s respectively, due to extra qualifying and race laps, plus the formation lap.

I know we're now micromanaging the scheduling — but I think it's good we're considering the practical implications.
Click to expand...

How long does it take to load into a server on average? 1 minute? maybe 90 seconds? So what you are proposing is that unless a user presses the join event button the exact moment it is active and has the fastest SSD/internet they won't be getting in till qually. This will cause join lags and disrupt drivers that are going out on the their outlaps or in extreme circumstances starting their fast lap.

The length of practice is for server joins. Presumably drivers would have been making use of the practice servers before the race to get warmed up. Use it to get yourself settled, check you have your setup loaded, tweak if necessary for qually or see what other drivers are in the server.
 
Woodee said:
How long does it take to load into a server on average? 1 minute? maybe 90 seconds? So what you are proposing is that unless a user presses the join event button the exact moment it is active and has the fastest SSD/internet they won't be getting in till qually. This will cause join lags and disrupt drivers that are going out on the their outlaps or in extreme circumstances starting their fast lap.

The length of practice is for server joins. Presumably drivers would have been making use of the practice servers before the race to get warmed up. Use it to get yourself settled, check you have your setup loaded, tweak if necessary for qually or see what other drivers are in the server.
Click to expand...
Yes. Practice session should be 3 minutes in any series, to connect, check setup, try to drive at least in pits. Sometimes I have my wheel/pedals not functioning (even on starting grid) and I have to disconnect/connect them, and if it takes place on grid, then I am being kicked to pits before start.

I would point to one more issue. When I go to Beginners races, I mean 20 minutes races (of 3 different kinds) starting every 20 minutes, I can do same races having some ~20-minutes break, or I can mix them, so I finish one race and immediately register for different one. In this case it takes time to wait for 1st race to be finished on server. Results are generated, everybody disconnected from session, but event is still underway. Sometimes only couple seconds are left to register for next race.

Also 1.5 minutes for gridding time can be cut to 1 minute. In iRacing gridding time is 2 minutes and it's enough for toilet if needed, but 1.5 minutes here is not enough for that I think, and it's too much for gridding itself (check setup and tires, put enough fuel) 😎
 
Last edited:
I would like to conclude all discussion with this: all races must be fitted into some cycle and waiting time must be minimized.
We have standard time before any race to do practice, qualifying and gridding. So we can just add this time to race length (+/-) and races will be cycled one after another.
Two 20-minutes races should be repeated every 40 minutes, not 30.
Three 20 minutes races repeating every 20 minutes is ideal example. 40 minutes also acceptable here.
Two 40-minutes races should be repeated every 60 minutes, to make them raced one after another and so on.
Only long (60 minutes and more) races should have special schedule (not cycling), because it's not common to drive them one-after-another. Usually it's one race per day.
All we want is more racing in limited time. We all have to work, spend time for family etc. And when we have time for hobby (simracing) we want to get most of this time.
 
Last edited:
It’s not about being “strapped for time” — it’s about proper scheduling. Every second matters when trying to ensure smooth transitions between sessions and events.

We’re genuinely trying to contribute constructively and help improve things, not nitpick for the sake of it. Dismissing it with a joke may seem harmless, but it reflects the kind of mindset that leads to overlooked issues in the first place.

I realise my tone may come off as blunt, and for that I apologise. Still, I believe this is a topic worth discussing with the seriousness it deserves.
 
Thank you.

I see now updated. Sadly 2 times spa. I don’t get it why they take the same track twice in one week.
 
Why cant i run the daily races back to back anymore? when i leave the last race ill end up having to wait 20mins+ for the next session
 
You must log in or register to reply here.
Back
Top