CORE N24 VLNFinished 

  • Thread starter memto89
  • 1,505 comments
  • 59,935 views
TDZdave
Its against team rules to "friend the enemy" :P I shall have a better look,

Edit: Is this a standard lobby or in the core community lobby?
Click to expand...

It is a standard friends only lobby. We have added all late requests, restarted the lobby and cleared the cache again so try again and see if you find it!
 
Hi. Nightfire is the one scheduled to be in today's race for TMR. I was the backup. So far he didn't say anything to me about not being able to race so i'm confident he can make it. Good race for all the participants...
 
Bichux
Hi. Nightfire is the one scheduled to be in today's race for TMR. I was the backup. So far he didn't say anything to me about not being able to race so i'm confident he can make it. Good race for all the participants...
Click to expand...
Might be worth sitting in the lobby just in case, the leave as soon as he shows up
 
Bichux
Hi. Nightfire is the one scheduled to be in today's race for TMR. I was the backup. So far he didn't say anything to me about not being able to race so i'm confident he can make it. Good race for all the participants...
Click to expand...

If Nightfire is driving tonight he needs to friend request the_proffs as soon as possible, only 8 minutes left.
 
Bichux
Hi. Nightfire is the one scheduled to be in today's race for TMR. I was the backup. So far he didn't say anything to me about not being able to race so i'm confident he can make it. Good race for all the participants...
Click to expand...

Nightfire's not here, come now if you're showing up
 
For the N24, I'm honestly thinking that the best places to start the race are either all the way at the front or all the way at the back. The cars in the middle going into the first chicane are going to cause some carnage...
 
Mike458
For the N24, I'm honestly thinking that the best places to start the race are either all the way at the front or all the way at the back. The cars in the middle going into the first chicane are going to cause some carnage...
Click to expand...
Well I'm pretty sure we're right in the middle.....
 
Confirming that as at yesterday all 3 GHH driver reports are in 👍
 
Final Round Results
Z96vfi.jpg


Stewarding
Race 1
GTPL_Plotnik - Non-submission of an incident report
Verdict: +30s

Lap 1 - jonnyb1990 - False Start
Verdict: +90s

Lap 3 - xNikodemusx - Pit-out line (non-controlled)
Verdict: NFA

Lap 3 - Glen-Alz-81 - Pit-out line (non-controlled)
Verdict: NFA

Lap 3 - xNikodemusx - GTPL_Plotnik - Accident
Verdict: NFA - Niko has made an early switch onto slick tyres. On home straight he pulls off the racing line onto still damp track to pass Plotnik, as he attempts to straighten the car, he loses traction and spins into into Plotnik, causing a large accident. Since he was not in control of the vehicle at the point the contact ensued this is not avoidable contact, however, we would like to raise all driver's attention to the possibility of this occurring on slick tyres on a drying track and to take suitable precautions.

Lap 4 - jonnyb1990 - Pit-out line (non-controlled)
Verdict: NFA

Lap 4 - xNikodemusx - Pit-out line (non-controlled)
Verdict: NFA

Lap 4 - Romisagon - Pit-out line (non-controlled)
Verdict: NFA

Lap 4 - Glen-Alz-81 - Pit-outline (non-controlled)
Verdict: NFA

Lap 4 - Romisagon - cobra75 - Rejoing Blocking
Verdict: Romisagon +30s, Driving Standards 1/3 - Romi, having spun at Pflatzgarten I, correctly turns into the inside of the circuit, off of the racing line against the barrier. He then rolls into the center of the circuit for no reason, leaving Cobra no-where to go.

Lap 5 - Romisagon - Pit-out line
Verdict: +30s

Lap 10 - Romisagon - Pit-out line
Verdict: +30s

Lap 12 - Romisagon - MINT_GTR - GTPL_Plotnik - Rejoin Blocking
Verdict: Romisagon +30s, Driving Standards 2/3 - MINT_GTR Driving Standards 1/3 - GTPL_Plotnik Driving Standards 1/3 - Romi, in his efforts to move out of the way, pulls off the circuit onto the grass. Unfortunately with the damage he has he loses control and spins across the circuit. The penalty is given because having spun, he then rolls back into the path of MINT_GTR and Plotnik. To all drivers, unless you are certain there are no cars near you, if you have an accident, sit with your brakes on until you can be sure it is same to return to the circuit. While MINT has less time to react, Plotnik has time to flash his lights, demonstrating sufficient reaction time, yet barely lifts as he passed through the wreck. As was stated last round this is not acceptable, all drivers should be checking the mini-map and prepared to slow to crawling pace if necessary to avoid accidents.

Lap 13 - Romisagon - Pit-out line
Verdict: +30s

Lap 13 - Romisagon - Dangerous Driving
Verdict: Warning - Romisagon collides with the pit-wall sending him towards the middle of the circuit outside of the pit barrier. He then does a J-turn, drives backwards up the circuit and turns into the pit-lane, again getting caught on the barrier, at which point Batista collides with him. Cars should always be pointing in the direction of the circuit, he should have simply reversed up the circuit while there were no cars around, then gone forwards again to re-enter the pit lane.

Lap 14 - Romisagon - Pit-out line
Verdict: +30s

Lap 15 - Romisagon - Pit-out line
Verdict: +30s

Lap 16 - jm-batista - Use of the pause menu glitch
Verdict: Disqualification - This was raised earlier in the VLN where the consequences were very clearly stated. Batista uses it multiple times to not only escape damage but also regain control of the vehicle. This is unacceptable.

Multiple incidents - Romisagon - Excessive use of the pause menu
Verdict: Driving Standards 3/3 +120s

Race 2

Lap 1 - jonnyb1990 - attrapp - GTPL_oldboy1957 - Racing Incident
Verdict: NFA - There appears to be some confusion over the start, the race goes green when the lead car is beneath the scaffold gantry. This leads to the three cars being very close going into the first chicane however there is only a couple of nudges none of which result in damage.

Lap 1 - bichu_mau - Use of the pause menu glitch
Verdict: Disqualification - Bichu runs wide into Flugplatz and pauses having left the track. While it is not clear if contact would have ensued otherwise, it still seems to be fairly obvious the intent of this action. To top it off Bichu then executes a very dangerous rejoin into the pack on a very high speed area of the circuit. If any doubt remained over his intent, he repeats this towards the end of the lap where heavy contact with the barrier does occur.

Lap 7 - attrapp - Pit-out line
Verdict: +30s

Lap 11 - attapp - Pit-out line
Verdict: +30s

Lap 13 - bichu_mau - Heathenpride - Accident
Verdict: NFA

Race 3

GTPL_Lubek7 - Non-submission of an incident report
Verdict: +30s

Pre-start - Play117 - CodDemon101 - Avoidable Contact
Verdict: Play117 +90s Driving Standards 1/3 - Contact on the parade lap should never happen, especially so close to the start line more attention should have been given. Play is also out of position for the start. The odds left, evens right rule does not include the safety car, make sure you are aware of your correct position during the parade lap

Lap 1 - LordZ1978 - TDZ-4-12-14-88 - Racing Incident
Verdict: NFA - TDZ does leave the door open to an opportunistic move by LordZ. While no damage ensues as LordZ runs slightly wide it does almost force TDZ into the wall. All drivers are reminded to be very careful during race starts since there is always time to make up positions later on.

Lap 4 - Play117 - TDZ-4-12-14-88 - Accident
Verdict: NFA - Both drivers react as they should, TDZ holds position as best he can once his car comes to rest and Play slows appropriately. Unfortunately due to the darkness and tyre-smoke it is not possible to see where TDZ's car is and so small contact ensues.

Notes:
There has been far too much use of the pause menu autopilot; the reason teams run in this event is that they wish to get as close to experiencing real endurance racing as is reasonably possible. Use of this autopilot undermines the spectacle of the event, is a danger to all other teams due to the distraction is causes and is completely against the spirit of the event. For this reason its use during the N24 while out of the pit-lane is completely forbidden. Any team using it for more than 3s (allowing for accidental button presses) will be given a 120s penalty. Any team using it for more than 60s will be instantly disqualified. Please not that this is in addition to the instant disqualification that will result in use of the pause menu to avoid damage.

Drivers are still far too willing to drive flat out into potential incidents, if you can see that you're approaching another car on the mini-map, especially if it is at a significant rate, you should be prepared to come to a stop. A yellow flag rule will be applied in which cars in battles may not pass one another if there is another car suffering from an accident nearby. The pursuing car will have to slow with the leading car and wait until the leader returns to racing speed before attempting a pass.

On a final note, the quality of racing we have seen this year is impressively high, and it's great to see that teams, both old and new, are demonstrating some real front-running pace. Let's make good use of the remaining practice sessions and have a fantastic race this year.

Championship Results:
y55Chy.jpg
 
Last edited:
Can I please get clarification on the following:

From the OP, taken now:

The screen shot attached shows that a single disconnect is viewed as mechanical failure and the race shall not restart.

7.3 details the mass disconnect procedure and it is under 7.3 that the 70% rule is covered. It does not apply to a single disc.

Surely this means that any disconnections that are not a mass DC are not covered by the 70% rule?
 

Attachments

  • Screenshot_2015-02-13-17-44-17.png
    Screenshot_2015-02-13-17-44-17.png
    103 KB · Views: 11
This is something that should have been updated but has not, early in (in the CSS) it was quickly apparent that applying the 66% rule (that was used for the VLN last year) was not feasible since it would have meant the majority of teams not scorring.
The interpretation has since been that completing a single lap in just one of the races in a round made a team eligible to score points, but being disqualified or not attending would result in a score of zero.
The 70% rule is I believe an erroneous carry over from single driver championship rules and has not been applied at any point during either the CSS or VLN this year.
 
I appreciate that, but it's in the event rules as they stand (2 weeks out from the race) yes? Would that not make them applicable?

I would have thought after the BoP fiasco that we'd be dealing with up to date rules?

When I go to the "rules" section in the OP of an event, any event, it stands to reason that they'd be current surely?

I respect that you both do a great job despite having limited time, and I've acknowledged such publicly a few times, but not having the rules for such a big event up to date is definitely not good.

With all due respect the drivers and teams who invest half a year (or more) in the N24 definitely deserve to have such vital things as the rules up to date at all times.
 
What?

"Non-submission of an incident report" - what is this?

We never sent this if race was clean and haven't any situations.

+30 secs. penalty for nothing (not sporting situation). None sense.
 

Similar threads

Famine
Microsoft Streamlines Xbox Game Pass: New "Core" Tier Introduced with Game Library Including Forza Horizon 4
Replies
7
Views
2K
sirjim73
sirjim73
Waheedos
Gran Turismo 1 v1.1 & v1.0 Widescreen 16:9 and Stable 60 FPS for Retroarch Swanstation Core Settings
Replies
0
Views
3K
Waheedos
Waheedos
HP
The 2022 Green Hell Online N24
Replies
11
Views
2K
HP
HP
Eunos_Cosmo
Can somebody recommend me a PC?
Replies
7
Views
569
Tornado
Tornado
Kobayashiiii
Help plz guys! I can't upload decals. [Repost to the correct subforum]
Replies
12
Views
1K
MatskiMonk
MatskiMonk

Latest Posts

Back