Please post your driver rosters for the third race in Fern Bay Black here.
Please use EXACTLY the following format (nationality field added for tracker reasons--please use ISO 3166-1 alpha 3 codes):
Team Name: Car Number: Drivers:
F.Name [lfsw] NAT
etc.
Remember, according to the rules a car's weekend drivers roster may include between 2 and 4 drivers from the team's overall roster, as posted and maintained in the signups thread.
Rosters must be confirmed by 17:00 UTC on the 4th June.
Confirmed Teams:
01 Scuderia Forza
02 Estonian Endurance Racers
03 Experion Racing Team
05 Lightning Racing
06 Sonicrealms Racing EDT
07 RaceSim Radicals - missed deadline
08 E-Team
09 Sim Racing Society
12 FUBAR Racing Team
13 Lublin Racing Team
16 ZION Team
17 Karma Racing
19 Serbian Chromed Pistons
20 Clockwork Motorsports
21 UER-Racing
22 SimRacing.lt Team
23 RAPTOR-GAMING
24 Xcite Racing
25 Gospel of Torque - missed deadline
30 Griffin SimRacing
32 Capo ARG
Teams missing event:
10 flash-racing
11 Guglhupf Racing Team
14 Qlimax Motorsport
15 SimRacing Klub PL
18 Advanced Drivers
26 Revolution Junkies Team
28 Factory Phantom Racing
29 Storm Racing
Guest Team:
- no Guest Team this race -
Waiting List:
31 Superfast
33 XFusion - miss event
35 Conedodgers - roster posted - missed deadline
36 Dinamo Motorsport - roster posted
37 ISR Team - roster posted - missed deadline
38 Windstyle Racing Team - roster posted
Waiting list drivers/managers prepare, post your rosters already now if you want to participate
According to rules (rule 2.4), the following cars will get a drive through penalty after racestart:
Car #07, Car #25
Because the problem was not our system, thats why we not restarted immediately.
We don't know what happend. Before we can restart the race we must know whats the problem und how we can fix that... do you understand that?
In this case, you raced the 10 minutes in which we search the problem. Otherwise you had to wait the 10 minutes. Whats better in this case?
Waiting people talk all the time to admins, when there will be the restart, whats the problem ... while all racing we hat enough time and privacy to find the problem and decide what is to do.
Well sorry, but if you planing your race to finish at point 23.00 german time, than this is your fault! If you decide to race in a league in the internet then don't be so green and calculate your time tight like this... thats not the fault of admins...
We have tried to do our best for everyone. This is the first time that i admining such a league i must learn such things... we couldn't know, that the connection lost was an bug in masterserver at this time...
Be sure, at 23.00 german time i had planned to drike a bottle of beer with my teammates and adminmates and not racing about 30 minutes longer
I think we didn't fail. We didn't restartet the race. We startet the race completly new.
The Problem was found about 10 minutes after start of the race. We tryed to fix the masterserver connection, but this was impossible without a server reboot and so we decided 10 mins later to start the race completly new.
Some racers would change drivers but couldn't this do, as result of this problem. We have decided to start the race completly new, to give all teams a fair chance.
Don't flame me now with posts like "but the other teams *whine*". Is completly wayne to me. We would avoid that the result will be forged by server problems, at point of restart the race, this was already the case for some teams.
NOTE: The "Trojan Horse" much Virus Scanners detected is a FALSE ALERT. This is a browser based filter list for LFSWorld names written in Java if you have special characters (Like @, _, ; , äöü , and so on) in it.
Well we have a live tracker system this time on our server.
But we will decide at saturday, whether we will publish the livestats for public-access or not.
We are using this system first time and do not know how the raceserver respond to much access on the webserver and tracker database.
But i think, the patch with scirocco will be never relased. shame on the devs, they don't call to their community and i'am sad about that thing, not about the delay...