UKGPL Season 32 (2017-18) Joe Shaw Memorial 2018 - Adelaide - Mar 20

[Cookie]

For this race I had set the bandwith more loose, so the clients-server traffic should have less load...

I don't think this was track related...

Leader of the race starts lap 19

30m24.660s
Tristan Bot gets disconnected while racing in position 1.

30m24.660s
Andreas Gebhardt gets disconnected while racing in position 7.

30m24.660s
Jack O 'Ferrall65 gets disconnected while racing in position 8.

30m24.660s
65 Clive gets disconnected while racing in position 6.

[EvilClive]

OK Axel.

It seems that 4 cars were dropped together at exactly the same moment. But I also had a CTD during qualifying and I think one or two other members had similar probs.

Do you think these problems were as a result of the changes to the bandwidth Axel ? or was there some other reason?  We have used this track in the past and had the occasional random disco, but we could get that at any circuit, so to have 4 cars knocked out in a single incident plus one or two others is worrying.
It would be a disaster if we had similar probs in Sunday's race.

[Doni Yourth]

Kinda ominous that we had so many checkouts.  I had a CTD in qualifying after about two laps as I came off the last corner.  I won't cry if we frag this venue.  Not on my shortlist of favourites.

As for the race, it was fun up til about half distance when the eyeballs started to whither.  I have some very useful medications for treatment but their cost is prohibitive.  I'll only use them prior to championship races.  Dean had fallen off and got behind me for a bit but with the vision fading, putting up a fight was more bravado than smart.  Grats on the win, Axel!

[Cookie]

Those BW settings (every 5th frame) should have been more save... normaly I use a higher rate (every 4th frame)

IMO it has to do with single drivers bad connections.
When the lag adds too much discrepance the server disconnects him and takes some others with it

The server pc in use has enough power (i5 2520 with 8GB of RAM) running stable on manjaro Linux.

Yes the track seems to have some known problems, but not for mass discos.

[EvilClive]

I am guessing that there is no way to discover which client PC triggered the discos?