Quote from Makao :

I know it's a difficult question, but when we can expect results?

It all depends on the data and how easy it is to integrate. Then we have to verify the outcome. Be assured we're aiming to resolve this issue asap.

Due to connection issues, we've red flagged the race. We are currently looking into the replay to determine positions and looking into the stability of the server.

This thread will be updated with the next steps to be followed.

Quote from xenoa :

Protest against car #4, assraped #14 in braking at the end of lap 3 and caused us to spin....

New version of the rpl...should work now...i checked it myself

After reviewing the replay, the admins have come to the following verdict:

There is contact between #05 and #12 resulting in a spin for #12. #12 standing on track, #14 can't avoid crash with #12. #04 hits #12 due crash with #12. The time in which it happened is very short. #04 did not get a Yellow flag by LFS and did brake full and shift back all the way back to 1st gear in order to reduce as much speed as possible.

Based on the replay #14's protest against #04 has been deemed as a race incident. No penalty.

Quote from xenoa :

Protest against car #4, assraped #14 in braking at the end of lap 3 and caused us to spin....

Your replay does not show any of this, please attach correct replay.

Race
DT - 09 - Drive through due to chat

Quote from BenjiMC :

Lap: 1
Teams: 05, 06, 16
Sector: 1

spdo hit #16, #16 went into us(#05) we started on the grass effectively and dropped way back into the GT2 field. This has ruined our race tbh.

Investigating

45% rule

GT1: 152 laps
GT2: 141 laps

On a side note: The tracker records individual lap time starts for most racers at lap10, this means that the % provided by the tracker is slightly off.

Replay of the start can be found here. Ideal for retrieving all the necessary skins!

Last edited by AppiePils, Sat, 4 Oct 2008 09:29.

41 just timed out.

working on it

State your protest here:

Include the following in your protest
• The correct lap,
• The cars (/teams) involved
• The lap/sector/time
• And a short description from your point of view.

Include a replay with at least 10s before and 10s after the event for which you protest (link). Additionally a movie of the incident may be useful as well, but protests have to include a replay. Link to MPR edit to cut out the part of the mpr the protest is about.

Free sites to upload movies are: http://www.mediafire.com
http://www.rapidshare.com

Last edited by AppiePils, Sat, 4 Oct 2008 09:41.

Occasion: Added Rule
Where: 9. Penalties.
What:

Quote :

* It is mandatory to follow the yellow pit exit lines to ensure a safe reentry the track, those who cut the yellow pit exit lines may be given a DT. For some events restrictions may apply for the pit entry as well, but this will be announced by the admins beforehand.

Reasoning:
To ensure a safe reentry on the track it is mandatory to follow the yellow pit exit lines. Restrictions regarding the pit entrance will be announced by the admins before the start of an event.
Outcome: Failure to do so can be protested against, and if declared valid, is subject to receive a DT.

Could you please attach those files instead of linking to it as an image? Nice render!

Occasion: Rule clarification
Where: 2. Numbers of drivers during a race weekend.
What:

Quote :

* During a race weekend a minimum of 3 and a maximum of 4 drivers must race for a team. In the 12hr and 24h race, a maximum of 6 drivers can race.

Reasoning:
To be more clear about what we consider a race weekend: a race weekend includes both the qualifications and the actual race. People who qualify for a team are part of that team's group of racers that is performing for that particular weekend for that particular team. We also upgraded the number of racers for a race weekend for the 12h race to a maximum of 6 racers. Do take into consideration that the 45% rule for the actual race still applies (ergo a minimum of 3 racers for the actual race is required).
Outcome: Having more than the maximum amount of drivers race during a race weekend, will lead to the removal of drivers till the allowed amount of participating drivers is reached. Any laps driven by this driver (/these drivers) will be removed from the teams total driven laps.

Last edited by AppiePils, Wed, 1 Oct 2008 19:43.

Common sense has been applied to stick to 1 uniform marking for GT2, not a bunch of random markings per team which supposedly should be identifiable. Simply put, racers don't have the time to discriminate every different marking and as so, it has to be clear at once, thus uniform.

Also to support that uniformity, GT1 teams are requested not to use Yellow marking on their bumper.

Last edited by AppiePils, Tue, 30 Sep 2008 20:15.

Quote from Dragonmen :

Sorry, but we really must object this ruling!

I ask you kindly to look at the braking point of car #38 in that lap! He missed it for whole 50meters!!! Hey, we are talking about 50 meters, do you know how much is that?!

If he did apply his brakes on time he would pass clearly with out interference, on the inside, because our driver [car #40] when he saw fast car went for a late braking (even latter than car #38) to go to outside of the corner to give room for car #38 to have a clean run through the corner... If he [car #40], in that time, swept across the track on the right side it would be dangerous and reckless, and there would be a possibility that none of the cars would make the corner! This was very reasonable decision from our driver!

As I personally see it "very dangerous and rather poor driving" was on the other side

Don't be scared when you see other cars on track when you are on your quick one... this is qualifying and not hotlapping

#40 enters the track without checking who is coming from behind. When #40 gets blue flagged by #38, based on the sudden car movements, #40 suddenly realizes that #40 is in the path of the faster car of #38 (while being blue flagged). Instead of taking the inside lane, and leaving the race line open for the faster car, #40 still picks the race line while slowing down. Yes, #40 brakes later, but all harm is done already. This is an example of lack of situational awareness.

Protest denied, penalty sustained.

Quote from nesrulz :

Hm..., where is my time for SERT?



EDIT: Warm up lap (YouTube)... Not fair...

Quote from DeadWolfBones :

nesrulz, I'll re-watch it when I get home tonight, but I'm pretty sure you also had contact with a pole on your hotlap.

Confirmed, lap is void. Regardless if the pole is still standing, you did had contact with the pole, which btw was not in your warm up lap, but in your qualifying hotlap, Nesrulz.

Last edited by DeadWolfBones, Mon, 29 Sep 2008 18:32.

Quote from CSF :

Your team number: 38
Protested team's number: 40
Time of incident: 20mins in Turn one.
Description of incident: #40 comes out of the pits and proceeds to drive slowly on the racing line. #38 comes up behind on flying lap and 40 does not move off line causing 38 to swerve around and hit the wall. Very dangerous and rather poor driving in our eyes.

#40's fastest lap from Q1 will be removed due to careless entry of the track after leaving the pits.

Last edited by DeadWolfBones, Mon, 29 Sep 2008 18:13.

Use the above format only.

Deadline is Friday October 3rd, 2008 at 21:00 UTC.

Teams with provided drivers list

GT1
#01 Mercury Racing
#02 #low-racing
#03 F1RST Racing
#04 n!faculty.seasonic
#05 My3id Gaming
#06 spdoRacing
#07 mb.racing
#08 Infinity Skills
#09 Serbian Racing Team
#10 LFSLA
#11 CoRe Racing
#12 Team High Fidelity
#14 XFusion Racing
#15 n1Racing
#16 Team Inferno
#17 Speed Core Racing Team
#18 The Danish Racing Team

GT2
#30 CoRe Racing
#31 Mercury Racing GT2
#32 XFusion Racing
#33 prodrive' Racing
#34 spdo Racing
#35 F1RST Racing
#36 GVR Team
#37 Infinity Skills
#38 Sonicrealms Racing
#39 Conquest Racing
#40 AutoMotoTrke.net Sim Racing
#41 Serbian Racers


Driver names should be announced the Friday before the start of the race by 21:00 UTC. Teams who fail to meet this deadline will start at the rear of their respective class grid.
On a second note, currently the tracker cannot deal with symbols like: Đ,đ,ć and will read out that information differently. For those with special symbols in their name (other than utf8), please provide your names without the special symbols if you don't want your name to be messed up on the tracker. We're in the process of fixing this issue.

The maximum amount of racers to be participating in the 12h of KY GP race weekend is 6 (see here for more info).

Last edited by DeadWolfBones, Fri, 3 Oct 2008 14:35.

Occasion: Rule added
Where: 4.Racing modus - Qualifying
What:

Quote :

* No more than 2 members of the same team are allowed to be on the server on the same time. Team is in this case defined as GT team, meaning that 2 members of a GT1 team and 2 members of a GT2 team are allowed on the server. In addition, GT2 drivers may not be present on the server while a GT1 qualifying session is ongoing, and vice versa.

Reasoning:
a) Too many connections may cause unnecessary stress on the server, which may lead to an increased chance of disconnects.
b) Teams who have to qualify cannot connect due to other teams spectating.
c) Teams should only join the server when it is their class specific time to qualify.
Outcome: Admins will reduce a team's server presence to 2 drivers by kicking inactive (spectating) drivers. If a driver reconnects and as a result brings his team's server presence to more than 2 drivers, that team will lose its fastest lap for that session. If a team's drivers repeatedly connect during the wrong class's qualifying session, that team will have +1s added to their fastest lap for their session.


Spectating can be done by LFS remote & LFS world.

Last edited by AppiePils, Thu, 30 Oct 2008 19:31.

Whether it's boring or not, these "boring" rules are a guideline, it wouldn't hurt to read the in total from time to time. As for you request regarding a highlight of the rules, we'll post what we've changed in a new post in this thread, while also updating the rules provided in the OP.

Last edited by AppiePils, Mon, 29 Sep 2008 03:42.

As always KY GP has the controversy of the chicane and two other corners related to cutting. Especially the chicane part is where it is possible to cut with little to no negative side effects (suspension damage).

Last year's first qualification became void to those issues, and resulted in the right attached image. For this season we elaborated on that outcome and created a layout for the track to ensure that cutting is restricted to a minimum.

As you can see in the left image, T1 and the two chicanes have poles. Poles don't cause damage or any other hazard to the teams' car, nor will interfere with the overview of a corner and will therefore not be an obstacle in the event someone has to go wide in order to prevent an accident (or any other reason). Based on the contact of the cars with the poles the admins can determine whether someone is cutting or not. In addition the poles can be used by the drivers to visually see what their allowed space is on the track.

To clarify how these poles are used in our decision making as admins:
1) If a team hits one of the poles during qualification, that lap will be void and removed from their fastest lap.
2) During a race the poles will be used to determine whether a team is guilty of 'aggressive cutting'.

Layout is attached and is also loaded on the Masters of Endurance server.

Finally, an PM with all the relevant data (server password etc) will be send to each team this weekend.

Last edited by DeadWolfBones, Mon, 29 Sep 2008 14:12.

o/

Any applications received after the final date will be dealt by using a waiting list.

GT1 balance is determined by LFS.

Last edited by DeadWolfBones, Thu, 11 Sep 2008 17:02.