The online racing simulator
Searching in All forums
(918 results)
Jonathon.provost
S3 licensed
The stewards reviewed the following during the event

Qualifying
Incident involving car 61,64 - No further action

Race
Car 28 - Drive Through Penalty - Causing an avoidable incident (Lap 1 - T13)
Car 8 - Drive Through Penalty - Causing an avoidable incident (Lap 2 - T1)
Car 14 - Drive Through Penalty - Causing an avoidable incident (Lap 4 - T2-3)
Car 71 - Drive Through Penalty - Causing an avoidable incident (Lap 10 - T13)
Car 71 - Drive Through Penalty - Unsafe Rejoin (Lap 14 - T8)

Car 88 has been disqualified from the results of the race for multiple incidents of causing a collision and unsportsmanlike behaviour. As S. Lee is on active NDR probation, his conduct has also been referred to the NDR board for further discussion.
Lap 34 T17
Lap 35 T12
Lap 35 T13
Lap 35 S/F Straight
Last edited by Jonathon.provost, .
Jonathon.provost
S3 licensed
Quote from cocom36 :I contest my drive through penalty the sanction is too high in view of the fault committed

As this is a decision of the stewards, this would have to be an appeal. Details on how to appeal and the timeframes that this must be within are detailed in the NDR Sporting Code section VI.4.

The NDR Sporting Code can be found here: https://newdimensionracing.com/sportingcode
E-Challenge 2022: Round 1 - Protests & Penalties
Jonathon.provost
S3 licensed
Please provide the following in your protest:

Session AND SERVER of Incident (Official Sessions: Free Practice, Qualifying, Super-Pole, Race; Servers: Main)
Lap AND MPR timecode of incident (or session time or UTC Time of Day):
Car(s) involved:
Location of Incident:
Brief Description of Incident:

Protests are due by 12:00 UTC on Monday, 17 January 2022

Penalty Log
Free Practice

Qualifying

Race
Car 28 - Drive Through Penalty - Causing an avoidable incident (Lap 1 - T13)
Car 8 - Drive Through Penalty - Causing an avoidable incident (Lap 2 - T1)
Car 14 - Drive Through Penalty - Causing an avoidable incident (Lap 4 - T2-3)
Car 71 - Drive Through Penalty - Causing an avoidable incident (Lap 10 - T13)
Car 28 - Drive Through Penalty - Causing an Avoidable Incident (Lap 10 - Pit Entry)
Car 71 - Drive Through Penalty - Unsafe Rejoin (Lap 14 - T8)
Car 21 - Drive Through Penalty - Chat
Car 21 - Warning - Causing an Avoidable Incident (Lap 16 - T8)
Car 21 - Warning - Spectating from the outside of the pitlane (Lap 17 - T8)
Car 95 - 5 Place Grid Penalty - Interfering with the leaders (Lap 23 - T16)
Car 10 - Drive Through Penalty - Overtaking before S/F line on SC restart (Lap 27 - S/F Straight)
Car 41 - Warning - Causing an Avoidable Incident (Lap 27 - T16-17)
Car 44 - Warning - Causing an Avoidable Incident (Lap 27 - T16-17)
Car 51 - Drive Through Penalty - Overtaking before S/F line on SC restart (Lap 27 - S/F Straight)
Car 88 - Disqualified from the results of the race - Causing an avoidable incident, Moving under breaking, unsportsmanlike conduct (Lap 34,35 - Multiple)


Car 88 has been disqualified from the results of the race for multiple incidents of causing a collision and unsportsmanlike behaviour. As S. Lee is on active NDR probation, his conduct has also been referred to the NDR board for further discussion.
Lap 34 T17
Lap 35 T12
Lap 35 T13
Lap 35 S/F Straight
Last edited by Jonathon.provost, .
Jonathon.provost
S3 licensed
UPDATE to SC & VSC speed and calculation for SC
Safety Car Maximum Speed: 80 kph / 49 mph
Virtual Safety Car Maximum Speed: 80 kph / 49 mph

11. Adding Time to the Race
The race is scheduled for 45 minutes, plus one lap. In the event of a Safety Car or Virtual Safety Car, time will be added to the race time, up to a maximum time of 60 minutes plus one lap.

Safety Car:
For each complete lap of SC: 115 seconds will be added to the race time.
For the lap of deployment, (approximate %age of lap left to run115s)0.5 will be used to divide the full lap, and added to the complete lap total. Example, Leader is at split 1 when SC is called, (115x0.66)x0.5=76s (rounded down)
Last edited by Jonathon.provost, .
Jonathon.provost
S3 licensed
Quote from MandulAA :Attached is BF1 regs pdf Smile

No I didn't...I would never do that... Smile
MRc E-Challenge 2022: Rules
Jonathon.provost
S3 licensed
E-Challenge 2022 - Rules


Attached are the rules for the MRc E-Challenge 2022. Please review them. The NDR Sporting Code is in effect with this series.

E-Challenge 2022 Round 1 used E-ChallengeRegulations
E-Challenge 2022 Round 2 onwards used E-ChallengeRegulations_Rev1
Last edited by Jonathon.provost, .
Jonathon.provost
S3 licensed
LFSW Name: jonathon.provost
In-game name: NDR.Provost
Full team name: New Dimension Racing
Jonathon.provost
S3 licensed
I’m in! This should be interesting
Jonathon.provost
S3 licensed
Quote from NumberTwo :Firstly I apologize for being a bit late, hopefully this protest can still be counted. I started typing it 4 hours ago but had problem with baby screaming so couldnt finish it.

I protest the decision to give DT to car 02 for a crash with car 9 on lap 1.

I can offer my client side race replay to prove following:

1. I lift from throttle before my car comes close to car 9
2. In my replay two cars dont touch
3. In my replay it is clearly shown that a packet update caused a "lag hit" and speared car 7 into the wall, not according to power of possible hit from behind (as speed difference was minimal between two cars, so crash like that would not be possible).

I feel like i should not be punished for game's deficiencies. Server has been laggy whole week (The green bar was jumping all the time) while my ping (and cars 9 ping) was stable.

Let me know if video evidence from my replay, or my replay is needed. I feel accident should be judged from my client side replay, as it will clearly show what me as i driver saw when racing.

As this is a decision of the stewards, this would have to be an appeal. Details on how to appeal and the timeframes that this must be within are detailed in the NDR Sporting Code section VI.4.

The NDR Sporting Code can be found here: https://newdimensionracing.com/sportingcode
BF1 League 2021: Round 2 - Protests and Penalties
Jonathon.provost
S3 licensed
Please provide the following in your protest:

Session AND SERVER of Incident (Official Sessions for Round 2: Free Practice, Qualifying 1, Qualifying 2, Race; Servers: Main
Lap AND MPR timecode of incident (or session time or UTC Time of Day)
Car(s) involved
Location of Incident
Brief Description of Incident

Protests are due by 17:30 UTC on Monday, 20th December, 2021
Jonathon.provost
S3 licensed
Real names.
Car number, pipe, first initial, dot, last name.
E.g. 00 | J. Provost
BF1 League 2021: Round 2 - Driver Briefing
Jonathon.provost
S3 licensed
Round 2, South City Long

IMPORTANT NOTE: This round of BF1 League is to use 0.6V, NOT 0.7A. Per the NDR Sporting code regulation III.7.1.a.1.

Track Specifications
Circuit Length: 4.029 km | Track Map
Safety Car In-Race Position: End of Pitlane
1st Safety Car Line: Start of Turn 15
2nd Safety Car Line: 58m before Turn 2
Safety Car Maximum Speed: 180 kph / 110 mph
Virtual Safety Car Maximum Speed: 80 kph / 49 mph
Pit Lane Speed: 80 kph / 49 mph
Red Flag line: 38m before first start light gantry, marked with red cones on the armco
Practice Start Location: 120m after the pit exit line, drivers left
Penalty Box Location: 60m after the pit entry line, before all pit boxes

Event Timetable
13:35 UTC: Free Practice - 20 minutes
14:05 UTC: Qualifying 1 - 20 minutes - All Cars
14:32 UTC: Qualifying 2 - 10 minutes - Top 10 from Q1 - Starts 5 minutes after last car enters pitlane in Q1.
14:50 UTC: Driver Briefing
15:00 UTC: Race - 76 laps - Maximum race time of 2 hours

Event Specifics

1. Alerting the Administration:
Use @sc to alert administration to look at your car or the section of track you were in when you use the @sc command. The command will tell the administration what location you're at.

2. Communications:
All drivers are required to be in the NDR TeamSpeak server: teamspeak.newdimensionracing.com - Race Control messages will be broadcast to anyone in a channel in the Pit Wall in TS. If you would like a subchannel for your team or friendly drivers, please let us know and we will create one.
Make sure you have your race number and/or your LFS username as your nickname on TeamSpeak

3. Broadcast
This race will be broadcasted by Sim Broadcasts: https://twitch.tv/simbroadcasts

They will be in the NDR TeamSpeak. You are invited to be interviewed on stream during the breaks between sessions. Please follow their terms listed at https://simbroadcasts.tv/voice - we will apply those to our Commentary Box area.

4. Driver Naming:
CHANGED FOR THIS ROUND ONWARDS
Be sure to be in your proper name format Number, pipe, first initial, dot, last name [eg. 00 | J. Provost].

The car number must be in white. The pipe should be in the closest colour to the predominant colour of your car skin.

5. Practice Starts
Drivers are permitted to take practice starts at the location notified above, any time the pit exit is open. Drivers taking practice starts should pull up to the chalk line that marks the spot, and wait for a clear path to take their practice start. Cars in the exit lane have right of way over cars preparing for a practice start.

6. Virtual Safety Car Test
There will be a test Virtual Safety Car deployment in the free practice session, starting about 5 minutes remaining in the session. All drivers are encouraged to participate in this test.

7. Pit Entry and Pit Exit
On pit entry, all parts of the car must be to the LEFT of the white blend line.
On pit exit, all parts of the car must be to the LEFT of the white blend line.

8. Qualifying Procedure
The course is open for laps from the session start until the time has elapsed. The pit exit will close at the chequered flag. No driver should exit the pitlane without sufficient time to start a timed lap.

9. Race Start:
Each race will have one formation lap, followed by a standing start.

When the default LFS lights turn green, pull away from your grid slot and do one lap, return to the grid area. Stop at the furthest available grid slot. Once all cars are in position, the Starter will initiate the start sequence. An insim head-up display will appear, with five darkened lights. After 5 seconds, each light will illuminate red at one second intervals. After a pause of between 3 and 7 seconds, the lights will extinguish and the race will be started.

10. Safety Car:
During safety car deployments, the Race Director will permit lapped cars to unlap themselves. Listen for instructions on this procedure. Cars instructed to overtake must do so safely, and must maintain their position relative to other cars that were waved around.

On Restarts, the Safety Car will pull away from the field after Turn 12. It must not be overtaken before it crosses the 1st Safety Car line.

Overtaking is not permitted on SC restarts until YOU have crossed the start-finish line.

11. End of Race
After finishing the race, please slow WELL BELOW racing speeds after Turn 1 and proceed to pit lane. The top 3 shall report back to Start / Finish Line for podium pose.

Top three and anyone else wishing to be interviewed on the broadcast should join the Commentary Box Waiting Room, and one of the commentators will move you to the Commentary Box.

12. Miscellany:
Do NOT under any circumstances Shift+P or Shift+S from on course during the race without authorization from Race Control.

You do NOT need permission to retire once you are in the pit lane.

If you suffer a lost connection or timeout from the server, you are permitted to rejoin the race, and we will add your completed laps to your car once you've rejoined.

Stop & Go penalties may ONLY be taken from the penalty box located at the location noted above.

Please post any procedural questions in this thread.

Good luck!
Last edited by Jonathon.provost, .
BF1 League 2021: Rules
Jonathon.provost
S3 licensed
BF1 League 2021 - Rules


Attached are the rules for the MRc BF1 League 2021. Please review them. The NDR Sporting Code is in effect with this series.
Jonathon.provost
S3 licensed
This looks awesome, cannot wait to see this.
LLS 2021: Round 5 - Protests and Penalties
Jonathon.provost
S3 licensed
Please provide the following in your protest:

Session AND SERVER of Incident (Official Sessions for Round 4: Free Practice, Qualifying, Race 1, Race 2; Servers: Main
Lap AND MPR timecode of incident (or session time or UTC Time of Day)
Car(s) involved
Location of Incident
Brief Description of Incident

Protests are due by 17:30 UTC on Monday, 11th October, 2021

Penalty Log

Free Practice:

Qualifying:

Race 1:

Race 2:
Jonathon.provost
S3 licensed
Quote from D4NO :Protesting about DT penalty Ive been given for hitting car number 34 in lap 18 hairpin. Race number 2. In such situation i couldnt avoid hitting the car in front as he closed door right in front of me unaware of me being close to him. yes i could have waited for him instead of going after he spun but from my point of view i wasnt the one doing the mistake going into the corner so why would i be paying for that. So please look at the incident once more thank you. Daniel Lukaštík, car 08

You need to submit an appeal for this. All information regarding this is laid out in the Sporting Code Section VI.4
Jonathon.provost
S3 licensed
Quote from Kristian K :Since there is no race discussion topic this round, I’ll write this here.

Multiple drivers, including me, have wondered why there was no information shared on car 40’s false start investigation. I would not personally mind this non-informing way of dealing with the matter if nobody knew there was a jump start, but this time things were significantly different as the server tracker sent a message to everyone (not only race control) about a jump start by car 40. This obviously is something that the race stewards need to react to, and it didn’t happen.

I personally think that things during the race should’ve gone followingly:
1. Tracker: “Jump Start by Car 40”
2. Race Control: “Car 40 under investigation for possible false start”
3. Race Control: “Possible jump start by car 40 reviewed – no further action”

After this there would be no complaints. Everyone knows that stewards have reviewed the start and case closed. No jump start, no penalties given. This time we only got the first message. Even messages 1 and 3 would have been enough. Drivers shouldn’t have to ask mid-race whether something has been reviewed or not if they get a notification by the server tracker. I assume that if there is a jump start message, it will be automatic drive-through penalty unless the race directors state something else.

The main problem I see in this incident is that race directors should be there for the drivers. Race control knows that there will be no further action but the drivers in the grid do not unless it is communicated to them. We do not have team managers/engineers communicating with race control and the driver. Now we have only drivers and race control which means communication becomes a key factor and I feel that Sunday was a disappointment in that matter.

Quote from Viperakecske :And on top of that when i asked one of the stewards after race 1 why no information about the penalty during race,he simply reacted "why would we need to?".
Which is kinda funny considering its an NDR hosted league,expectations higher too.
In my opinion its not that hard to notice the others about the situation,when there is like 9 red colored "steward"on the server
.
Thanks

Hi both,

I understand your view with this and will share with you the internal processes we use...

The 'jump start' notification was a technical messages for the stewards to investigate. However this message is not to be mistaken with any administrative decision. The latter are only the penalties with their communication as they are the only one impacting the course of the race from the outside. This message does not mean that the driver did in fact jump the start or not. The insim can detect the slightest movement etc from the car which is why we review all starts. Regardless of this notification, the starts are reviewed (hence other penalties for the start procedure being given out).

It has not been standard practice for NDR to notify of incidents under investigation in the server previously (especially when using a 'sprint' format). The stewards review many many incidents throughout the race and one of our considerations is that this could lead to significant 'spam' in the server chat.

For the avoidance of doubt, as long as there is no penalty announced, you should not assume another competitor has a penalty.

We will of course review this and see if any procedural changes are needed.

Thanks
JP2
Jonathon.provost
S3 licensed
The NDR Board was referred Car 88 from the 6th round of the 2021 GT2 Challenge for further action on the NDR level. The Stewards elected to disqualify him from the meeting.

The NDR Board have elected to place Sean Lee on NDR Probation for 12 months, effective from the date of the offence (21st March 2021). Sean will also have his stewarding status revoked, and will not be allowed to be in Race Control during any race meeting without advance permission.

This decision was made on the 25th March 2021
Last edited by Jonathon.provost, .
Jonathon.provost
S3 licensed
Round 5 Replays added
LRL 2021: Round 3 - Protests and Penalties
Jonathon.provost
S3 licensed
Please provide the following in your protest:

Session AND SERVER of Incident (Official Sessions: Qualifying, Race; Servers: Main
Lap AND MPR timecode of incident (or session time or UTC Time of Day)
Car(s) involved
Location of Incident
Brief Description of Incident

Protests are due by 11:00 UTC on Sunday, 30 May 2021

Penalty Log
Qualifying

Race
Jonathon.provost
S3 licensed
Round 1 Replays Added
Layout Racing League 2021: Replays, Results, Points
Jonathon.provost
S3 licensed
Round 1 - Broker Hill National

Qualifying: Official Result || Tracker || Replay || mpRes

Race: Official Result || Tracker || Replay || mpRes

Driver's Championship after Round 1

Round 2 - Scawen's Racetrack

Qualifying: Official Result || Tracker || Replay || mpRes

Race: Official Result || Tracker || Replay || mpRes

Driver's Championship after Round 2

Round 3 - Port Town

Qualifying: Official Result || Tracker || Replay || mpRes

Race: Official Result || Tracker || Replay || mpRes

Driver's Championship after Round 3

Round 4 - Mini Monaco

Qualifying: Official Result || Tracker || Replay || mpRes

Race: Official Result || Tracker || Replay || mpRes

Driver's Championship after Round 4

Round 5 - Mid-Town Ring

Qualifying: Official Result || Tracker || Replay || mpRes

Race: Official Result || Tracker || Replay || mpRes

Driver's Championship after Round 5

Round 6 - Woodland Raceway

Qualifying: Official Result || Tracker || Replay || mpRes

Race: Official Result || Tracker || Replay || mpRes

Driver's Championship after Round 6

Round 7 - Hong Kong

Qualifying: Official Result || Tracker || Replay || mpRes

Race: Official Result || Tracker || Replay || mpRes

Driver's Championship after Round 7

Round 8 - Lmaoring

Qualifying: Official Result || Tracker || Replay || mpRes

Race: Official Result || Tracker || Replay || mpRes

Driver's Championship after Round 8
Last edited by dekojester, .
LRL 2021: Round 1 Protests and Penalties
Jonathon.provost
S3 licensed
Please provide the following in your protest:

Session AND SERVER of Incident (Official Sessions: Qualifying, Race; Servers: Main
Lap AND MPR timecode of incident (or session time or UTC Time of Day)
Car(s) involved
Location of Incident
Brief Description of Incident

Protests are due by 11:00 UTC on Sunday, 2 May 2021

Penalty Log
Qualifying

Race
GT2 Challenge 2021: Round 0a - Protests and Penalties
Jonathon.provost
S3 licensed
Please provide the following in your protest:

Session AND SERVER of Incident (Official Sessions for Round 0a: Free Practice, Race; Servers: Main)
Lap AND MPR timecode of incident (or session time or UTC Time of Day)
Car(s) involved
Location of Incident
Brief Description of Incident

All race day protests are due by TBD UTC on Tuesday, 6 April 2021.

Track Map

Penalty Log

Free Practice

Race
Jonathon.provost
S3 licensed
Final update, only usernames and skin changes
FGED GREDG RDFGDR GSFDG