I would have two suggestions for the next events:
- reducing the total number of entries from 36 to a slightly lower number (30 or 32 maybe)
This could help both people who had performance issues (some reported to have CPU occupancy warnings, reducing in them lagging / warping on the track, making racing around them rather unpleasant).
Some (as myself) experienced never seen before connection issues possibly due to the larger number of attendees. This fluctuated during the race and always went back to completely normal values once the field had spread out a bit.
This is a concern NOT easily helped by the simple "upgrade your computer" argument I am afraid :-(
- maybe think about a rolling start with such massive fields
The number of unnecessary incidents during the first half of lap 1 was quite interesting.
Some back markers / midfield runners also went quite aggressive when in the pack during lap 1 resulting in off tracks and spins. I was pushed off track twice in lap one (no contact but I avoided contact resulting in an off track, completely compromising my race).
Some people also did clearly have connection / warping issues, were told several times about it by different people and still decided to race nevertheless.
For long times during the race I was stuck behind a slower driver who was warping substantially and a clean overtake was just not possible -> race ruined.
Given that I looked forward to this race all week long and got up at 3 am in the morning to attend the race that was frustrating to say the least.
Here is a possible solution for such people (sometimes I fall into that group myself, given that I have to connect through a rather elaborate connection):
Maybe in such big events people who are called out during practice and qualifying to have clearly visible connection issues (clearly warping, excessive ping times above 500+ ms) and these people together with all reserve drivers who choose to do so could have their own race in a split 2 on the practice server without admin attending (as to prevent additional workload apart from setting up the server cycle and a basic set of cars) ? This way such people do not have to loose to race completely but the main server stays save.
- reducing the total number of entries from 36 to a slightly lower number (30 or 32 maybe)
This could help both people who had performance issues (some reported to have CPU occupancy warnings, reducing in them lagging / warping on the track, making racing around them rather unpleasant).
Some (as myself) experienced never seen before connection issues possibly due to the larger number of attendees. This fluctuated during the race and always went back to completely normal values once the field had spread out a bit.
This is a concern NOT easily helped by the simple "upgrade your computer" argument I am afraid :-(
- maybe think about a rolling start with such massive fields
The number of unnecessary incidents during the first half of lap 1 was quite interesting.
Some back markers / midfield runners also went quite aggressive when in the pack during lap 1 resulting in off tracks and spins. I was pushed off track twice in lap one (no contact but I avoided contact resulting in an off track, completely compromising my race).
Some people also did clearly have connection / warping issues, were told several times about it by different people and still decided to race nevertheless.
For long times during the race I was stuck behind a slower driver who was warping substantially and a clean overtake was just not possible -> race ruined.
Given that I looked forward to this race all week long and got up at 3 am in the morning to attend the race that was frustrating to say the least.
Here is a possible solution for such people (sometimes I fall into that group myself, given that I have to connect through a rather elaborate connection):
Maybe in such big events people who are called out during practice and qualifying to have clearly visible connection issues (clearly warping, excessive ping times above 500+ ms) and these people together with all reserve drivers who choose to do so could have their own race in a split 2 on the practice server without admin attending (as to prevent additional workload apart from setting up the server cycle and a basic set of cars) ? This way such people do not have to loose to race completely but the main server stays save.