The place where the car gets teleported to is the place where the car was when the substitute driver joined the server. Or at least somewhere near.
6h of Westhill - Date
Ok, here's a little poll for you. At the current date of the Westhill event, some countries have carnaval. We ask every team to place one vote. What date do you prefer to have the 6h of Westhill race?
1. February 25 (old date)
2. March 4
3. March 11
Please post a reply containing the team you represent and the team choice. Please use IRC or so for discussion, to keep it tidy
EDIT: reply, not replay
1. February 25 (old date)
2. March 4
3. March 11
Please post a reply containing the team you represent and the team choice. Please use IRC or so for discussion, to keep it tidy
EDIT: reply, not replay
Last edited by Frankmd, .
What happens is this:
Player A is driving on lap 200
Player B connects as Player A is in the second split
Player A goes into the pit (still on lap 200)
Player B takes over, and gets teleported to somewhere in the second split. The ingame tracker goes to 201
Player B starts to drive, and as he crosses the line for the first time, the counter stays on 201. This it the moment our tracker will get a message 'driver B crossed the line', and then our tracker will also go to 201.
So all that is lost is the distance from 2nd split to the line. That is not a full lap, so will not be counted as such.
Player A is driving on lap 200
Player B connects as Player A is in the second split
Player A goes into the pit (still on lap 200)
Player B takes over, and gets teleported to somewhere in the second split. The ingame tracker goes to 201
Player B starts to drive, and as he crosses the line for the first time, the counter stays on 201. This it the moment our tracker will get a message 'driver B crossed the line', and then our tracker will also go to 201.
So all that is lost is the distance from 2nd split to the line. That is not a full lap, so will not be counted as such.
We have decided that, the teams will not get an extra lap. They were set back (not forth) about two-third of a lap back (maximum) and that is not a full lap. The tracker was not affected by this bug.
24h results
Attached are the unofficial results for the 24h race.
Why are they still unofficial?
Because we want to give every team the opportunity untill wednesday evening 23:59 to apply against these results. Every team that wants to check the results themselfs, can send me a PM. I will then send you a document with the full tracker-logfile for your team only. Please do consider that I've spent several hours comparing the two trackers that were running during the race, and they both agree on the current standings. Please do not look at the red boxes on the 'Full stats'-tracker, some teams appear to have received a penalty, but in fact the tracker counted one lap double. Also some teams who got an official penalty might not have a red box, if the tracker missed 1 packet. I used the penalty possibility to correct these errors.
I will spend some time recoding the tracker, so we will have a self-correcting tracker for the next race.
Why are they still unofficial?
Because we want to give every team the opportunity untill wednesday evening 23:59 to apply against these results. Every team that wants to check the results themselfs, can send me a PM. I will then send you a document with the full tracker-logfile for your team only. Please do consider that I've spent several hours comparing the two trackers that were running during the race, and they both agree on the current standings. Please do not look at the red boxes on the 'Full stats'-tracker, some teams appear to have received a penalty, but in fact the tracker counted one lap double. Also some teams who got an official penalty might not have a red box, if the tracker missed 1 packet. I used the penalty possibility to correct these errors.
I will spend some time recoding the tracker, so we will have a self-correcting tracker for the next race.
The red +1 can also be a lap that was double counted by the tracker. If your penalty isnt listed in the penalty thread, no penalty was counted.
As for the replays of shock.fx:
The first replay posted timed out before the finish line.
The second set of replays. Only moe_24h_sazea_2.mpr showed a full lap that was not counted by the tracker, so they will get that lap back.
As for the replays of shock.fx:
The first replay posted timed out before the finish line.
The second set of replays. Only moe_24h_sazea_2.mpr showed a full lap that was not counted by the tracker, so they will get that lap back.
Reviewed the replay, but the driver did not cross the line. I am sorry, but I cannot count that. There were more cases of people who timed out 150m before the line, but we have to draw a line somewhere.
If you can provide me replays of the following laps, you might get some laps added to your overal number.
Lap 48 after about 2h45 and the 15 minutes after that (the point where you had a few disconnections in a row)
Lap 124 after about 12 hours.
If you can provide me replays of the following laps, you might get some laps added to your overal number.
Lap 48 after about 2h45 and the 15 minutes after that (the point where you had a few disconnections in a row)
Lap 124 after about 12 hours.
I have been trying to hunt down lost and double packets for the last 3 hours. This results in a slightly different standing, especially at the rear of the field. However, we will not congratulate anyone until we checked the data of both trackers (we have the one you are all looking at, and one backup).
It is however important that (if possible) you send us a replay when you timed out after just crossing the finish line. If you can show you did a full lap, we will include this in the standings.
We will try to come with the official standings as soon as possible.
It is however important that (if possible) you send us a replay when you timed out after just crossing the finish line. If you can show you did a full lap, we will include this in the standings.
We will try to come with the official standings as soon as possible.
IMPORTANT: Please report pit bug here
IMPORTANT
We have recieved reports about cars that were placed somewhere on the track after a driver swap. Some cars were (for example) placed near the second split line, instead of in the pits. This would mean that one lap is not counted.
Please report WHEN and WHO, this would help me fix the tracker.
Thank you.
We have recieved reports about cars that were placed somewhere on the track after a driver swap. Some cars were (for example) placed near the second split line, instead of in the pits. This would mean that one lap is not counted.
Please report WHEN and WHO, this would help me fix the tracker.
Thank you.
The last two penalties have not yet been processed in the tracker.
24h - Going into the night
Hello dear racers.
We are heading into the night and this is where it gets exciting There will be an admin online untill 3 and then probably from 5 again. If something happens between 3 and 5 you will have to wait untill 5. If something really serious happens (think: servercrash) there are people who will try to wake us up so we can assist as soon as possible.
Thanks in advance.
We are heading into the night and this is where it gets exciting
There will be an admin online untill 3 and then probably from 5 again. If something happens between 3 and 5 you will have to wait untill 5. If something really serious happens (think: servercrash) there are people who will try to wake us up so we can assist as soon as possible.Thanks in advance.
24h - Issues concerning the tracker
Hello all.
The tracker sometimes doesnt show the right standings. This is because some packets get lost. We dont know how this is happening, it might be the number of cars on the track or the number of people watching LFSSpectator. We will try to keep it as accurate as possible, but especially during the night it may happen that it will go a bit out of sync. We will make sure that we check the database for errors before we make the results final.
Thank you for your understanding.
The tracker sometimes doesnt show the right standings. This is because some packets get lost. We dont know how this is happening, it might be the number of cars on the track or the number of people watching LFSSpectator. We will try to keep it as accurate as possible, but especially during the night it may happen that it will go a bit out of sync. We will make sure that we check the database for errors before we make the results final.
Thank you for your understanding.
The stream isnt supposed to be up. But you can follow it using lfs spectator.
All start racers are asked to connect to the server before 15:50cet, so we can start on time. This is 12 minutes from now. Thank you.
The video of yesterday is now up for download here: http://www.gamer-fm.de/v4/index.php/news/view?id=2219
Scroll down to
NSV-Mitschnitte:
Freitag:
Race will start in about 1.5 hours, so head for the supermarket to get some snacks and be back in time for the start!
Scroll down to
NSV-Mitschnitte:
Freitag:
Race will start in about 1.5 hours, so head for the supermarket to get some snacks and be back in time for the start!
The starting grid for tomorrow.
I think this fixed it:
Edit: Messed with options, now ok; Removed Allow hardware video overlay from Video options
Edit: Messed with options, now ok; Removed Allow hardware video overlay from Video options
The stream for the second qualification is running now.
http://www.gamer-fm.de/v4/index.php/streams?id=4
http://www.gamer-fm.de/v4/index.php/streams?id=4
Could you please give the correct LFSWorld name for Shark? Cause the Shark that is on lfsworld is not french.
Are the tyre forces merely produced by friction? Or could some of the forces be generated by elastic contact-patch effects? Just guessing here, it is quite some time ago I read some stuff about tyres. Or maybe by the side-wall of the tyre?
Masters of Endurance 24 hour race this weekend
This weekend 15 of the finest LFS teams will compete 24 hours at the Aston Grand Prix track. You will be able to follow this event live on the Gamer-FM VideoStream. Follow this link to go to the stream.
The startinglist:
No. 1 - masterblasters e.V. Clanshells Motorsport
No. 5 - Pedal To The Metal Racing Team
No. 7 - n!faculty racing
No. 8 - teamnic
No. 9 - Shock.fx
No. 10 - Ocrana Racing 1
No. 11 - Ocrana Racing 2
No. 16 - Cyber Racing
No. 17 - n!faculty racing 2 FXR
No. 18 - tHUNder Racing
No. 19 - pod - virtual gaming
No. 20 - dRagonality LFS Team
No. 21 - Estonian Endurance Racers
No. 22 - Team ITEK
No. 23 - HighFiDelity Racing
The story so far
The 24 hour race is the fourth race of the Masters of Endurance season. During the first two races Pedal To The Metal Racing was unbeaten, and took two wins. At Blackwood they only scored a fourth place, which allowed the other teams to come closer. teamnic is one of those teams, currently second in the championship. They have not scored any win yet, but did make it to the podium every race. Currently third in the championship is the XR GTR team of Ocrana Racing, who beat teamnic in the last race by just 5 seconds. They are only two points behind teamnic and three points ahead of the XR GTR team of n!faculty racing. n!faculty won the last race and aims to get into the top three in the championship.
Newcommers such as pod-virtual gaming, tHUNder racing, dRagonality LFS Team, HighFiDelity Racing, Team ITEK and Estonian Endurance Racers will take up the challenge and give the other teams a run for their points.
Live VideoStream by Gamer-FM.de
Gamer-FM.de will broadcast three times:
Friday 13th, 21:00cet (Stream starts at 20:30cet) - Second QualificationSome links
Saturday 14th, 20:30cet (Stream starts at 20:00cet) - First race report
Sunday 15th, 10:30cet (Stream starts at 10:00cet) - Second race report untill the finish at 16:00cet
Live tracker, will automatically update every 30 seconds and shows all kinds of statistics about the race.
http://moe.lfs-tracker.de - Powered by lfs-tracker.de
Live Stream showing the race, including interviews etc.
http://www.gamer-fm.de/v4/index.php/news/view?id=2219 - Powered by Gamer-FM.de
Masters of Endurance website, with renders of the competing cars (so you know who you're looking at) and the current championship standings.
http://moe.mm2c.com - Powered by mm2c.com
ESL website, provides the server.
http://www.esl-europe.net/eu/
Ok thank you all for posting the information.
It just crossed my mind that since we are doing a 24h race, we will also be racing at 12pm. I am not sure, but I believe some DSL connections get reset at a certain time of the day? At least I heard about that. It might be wise to think about this when you are making a schedule for your team.
It just crossed my mind that since we are doing a 24h race, we will also be racing at 12pm. I am not sure, but I believe some DSL connections get reset at a certain time of the day? At least I heard about that. It might be wise to think about this when you are making a schedule for your team.
Updated list
No. 1 - masterblasters e.V. Clanshells Motorsport
No. 2 - Twister-Racing
No. 3 - Triso Racing Team
No. 4 - ghostaholic racing team
No. 5 - Pedal To The Metal Racing Team
No. 6 - FDB Racing
No. 7 - n!faculty racing
No. 8 - teamnic
No. 9 - Shock.fx
No. 10 - Ocrana Racing 1
No. 11 - Ocrana Racing 2
No. 12 - Mercury racing team
No. 14 - dE Racing
No. 15 - teamnic blue
No. 16 - Cyber Racing
No. 17 - n!faculty racing 2 FXR
No. 18 - tHUNder Racing
No. 19 - pod - virtual gaming
No. 20 - dRagonality LFS Team
No. 21 - Estonian Endurance Racers
No. 22 - Team ITEK
No. 23 - HighFiDelity Racing
No. 1 - masterblasters e.V. Clanshells Motorsport
No. 2 - Twister-Racing
No. 3 - Triso Racing Team
No. 4 - ghostaholic racing team
No. 5 - Pedal To The Metal Racing Team
No. 6 - FDB Racing
No. 7 - n!faculty racing
No. 8 - teamnic
No. 9 - Shock.fx
No. 10 - Ocrana Racing 1
No. 11 - Ocrana Racing 2
No. 12 - Mercury racing team
No. 14 - dE Racing
No. 15 - teamnic blue
No. 16 - Cyber Racing
No. 17 - n!faculty racing 2 FXR
No. 18 - tHUNder Racing
No. 19 - pod - virtual gaming
No. 20 - dRagonality LFS Team
No. 21 - Estonian Endurance Racers
No. 22 - Team ITEK
No. 23 - HighFiDelity Racing
Last edited by Frankmd, .
As long as every driver has read this before the race, the chaos should be limited to the regular shouting etc. I just hope that every team has at least 2 people following the race at any point, so that they can tell each other what to do.
IRC is very important in this case. So yet again, I ask everyone to be connected to the IRC channel #moe at GameSurge during the race.
FGED GREDG RDFGDR GSFDG