RD Le Mans Series Season 7 (rFactor 2)

Status
Not open for further replies.
I've a few requests pending:

Steam names:

Choune
Grant Crow
Etone
Damien HESLOUIS

@Theo Badry , Some of them have a similar Steam avatar as yours. If they are your drivers, could you ask them the reply to this thread with:

Steam ID (display name): ........
RD Forum name: .....
Team number & name: ........


Thanx,... :thumbsup:
 
Gijs van Elderen said:
I've a few requests pending:

Steam names:

Choune
Grant Crow
Etone
Damien HESLOUIS

@Theo Badry , Some of them have a similar Steam avatar as yours. If they are your drivers, could you ask them the reply to this thread with:

Steam ID (display name): ........
RD Forum name: .....
Team number & name: ........


Thanx,... :thumbsup:
Click to expand...

Hello Gijs.

I don't know who are Grant Crow and Damien Heslouis.

But i can confirm :
Steam ID (display name): Choune
RD Forum name: Laurent Gueneau
Team number & name: #26 Frenchie Fox Racing

Steam ID (display name): Etone
RD Forum name: Emmanuel Taphinaud
Team number & name: #26 Frenchie Fox Racing

Cheers.




 
IMPORTANT!

Due to the rFactor 2 update scheduled for Monday 1st May, and also to give us a little bit more time to finalise work on the resources for Round 2, there will be a maintenance period from 8pm on Monday (1st May) until 8am on Tuesday (2nd May). During this time the RDLMS servers will be unavailable, so that we can bring them up to date. We shall also take this opportunity to upload the updated versions of required resources, for the second event, to Steam Workshop before installing the latest component files on the servers and restarting. As a result of this delay we have extended the deadline for the submission of new and updated skin files by 24 hours, until 23:59 GMT on Saturday 29th April. We apologise in advance for any inconvenience that this may cause.
 
Last edited:
IMPORTANT!

Due to the rFactor 2 update scheduled for Monday 1st May, and also to give us a little bit more time to finalise work on the resources for Round 2, there will be a maintenance period from 8pm on Monday (1st May) until 8am on Tuesday (2nd May). During this time the RDLMS servers will be unavailable, so that we can bring them up to date. We shall also take this opportunity to upload the updated versions of required resources, for the second event, to Steam Workshop before installing the latest component files on the servers and restarting. As a result of this delay we have extended the deadline for the submission of new and updated skin files by 24 hours, until 23:59 GMT on Saturday 29th April. We apologise in advance for any inconvenience that this may cause.
 
Last edited:
Ike Ramos said:
Hi, there are places for another team. @Daiman Patel
Click to expand...
Hi Ike. There are currently no vacant places in either of the two classes, so if you register now the team shall be placed in the reserves list for your chosen class. Also please note that the entry list is now closed for Round 2, but open for subsequent rounds of the championship; if a team withdraws (or is removed) from the series before the second round, and you are promoted to the main entry list, then you will not be able to participate until Round 3 at the earliest.
 
HI !
Last changes :
Team name: Gentlemen Racers Spirit
Team owner*: PatriSte_GR
Team owner forum name*: Patrice Sayettat(@PatriSte_GR)
Preferred class*: GT
Number assigned #122
Driver 1*: Patrice Sayettat @PatriSte_GR
Driver 2: Stephane Perrin @Stéphane Perrin
Driver 3: Vincent Dimaio @Vincent Dimaio
Driver 4: Sam Suffi @tmbir

Driver OUT: Jeff Grits @Jeff Grits

I shall ensure all drivers are Premium Members for each round of the series: YES
I agree to the TOLA: YES
 
Update - April 30, 2017

The following additions and amendments have been made to the Rules & Regulations for the RDLMS. In case the rules in this section conflict with the 2017 RD League Regulations or v1.2 of the Additional Regulations for RDLMS Season 7 (see below for more information), the rules stated here shall override and supersede those in the aforementioned sets of regulations and guidelines.

  1. Starting driver. The race must be started by the driver who participated in the qualifying session. Participation in the qualifying session is mandatory, only one driver for each car must be on the server during the session, and driver swaps are not permitted, therefore the driver on the server at the time of the qualifying session will be required to start the race.
  2. Driver swap mandatory. Each team needs to perform at least one (1) driver swap in the course of the race to be eligible for points.
  3. Blue flag exception. Blue flags need only be respected when it concerns two cars of the same class. The slower car may ignore a blue flag issued over an approaching faster car from a different class. Both cars are still encouraged to facilitate inter-class overtaking. It is advised that slower cars do not move off the racing line or make unexpected moves when being overtaken by a faster car. Always be predictable and drive within your limits to avoid accidents.
  4. Rejoining the server. In case a driver disconnects from the server the driver - and only the driver! - may reconnect to the server and continue in the same car. The driver in question is strongly advised to reboot his or her PC in order for the rejoin to take proper effect. Since there were issues with rejoining and driver swaps in the first round, we will allow to re-enter the server with a new car. You will have to get permission at the stewards first and explain what happened, according to our review we will either allow you to drive or not to. In most cases a lap will be deducted from your standings.
  5. Race start procedure. At the beginning of each race a safety car shall move from the rear to the front of the grid, and lead the cars for a single formation lap, before a double-file rolling start. The safety car will be predominantly responsible for controlling the pace (this shall be approximately pit-lane speed). At the end of the formation lap the safety car shall move aside, and the lead car will be instructed to control the pace. Race control will subsequently call "Get Ready" before calling "Green Flag", at which point all overtaking shall be permitted.
  6. Racing infringements. Any racing infringements (such as causing a collision or disrespecting track boundaries) must be reported to the stewards immediately for review. The report must sent to the stewards by the team owner or one of his drivers. Any incident reported more than five (5) minutes after occurring will not be considered by the stewards.
  7. Other infringements. Any other infringements (such as software cheating or illegal drivers) can be reported to the stewards up to 24 hours after a the race. These incidents will be reviewed in the week after the event. This report must be sent by the team owner to @Frank , with the following in the title: RDLMS S7 Round <X> - <REASON FOR REPORT>. Please include a clear description of the incident, backed up with proof by way of a video or understandable data.

Rules & Regulations Addendum - v1.1 - February 10, 2017
  • TeamSpeak. At least one driver from each time is required to be present on the RaceDepartment TeamSpeak server, in a channel specifying your team name, at all times during an event. TeamSpeak shall be used for the pre-race briefing, as well as to make announcements during the qualifying and race sessions, for example to indicate the switch over time for GT and Prototype cars during the qualifying session, and to notify teams of green and yellow flags.
  • Qualifying format. The qualifying session shall be held in a single 60 minute session, but each class will only have 30 minutes to qualify. GT cars shall qualify first, followed by the Prototype cars. The start of the session and the switch over period shall be announced on TeamSpeak. Drivers must remain in their garage whilst it is not their qualifying session; any cars that enter the pit lane before the start of their qualifying session or after the end of their qualifying session (unless they are returning to their garage) shall receive a time penalty during the race. Pressing ESC is permitted. 5 and 10 minute warnings shall be given during the qualifying session for each class.
  • Headlights. All cars in the EnduRacers mod has fixed running lights (to allow cars to be visible to one another even in poor light conditions), so you may choose whether or not to also use your headlights during daytime hours. However, headlights must be used at night.
  • In case of a server crash. In the unfortunate (and hopefully unlikely) case of a server crash, teams shall be notified of the restart time over TeamSpeak and also in the RaceDepartment forums (in the thread for the current event). An attempt shall be made to resolve the issue as quickly as possible, and have the race underway again within 30 minutes of the crash.To help us achieve this we ask that the same driver on the server before the crash is also the driver who rejoins for the restart, and that they do so as quickly as possible after the crash; this will help to reduce the administrative burden when (re)setting positions and laps, and speed up the restart process.The time taken to restart the race, from the moment the server crashes up to the (re)start procedure, shall be subtracted from the remaining time in the race.
  • Spectating. To help ensure the stability of the server, and also to prevent join / exit lags spectating on the server shall not be permitted. Drivers may only enter the server as a spectator if they intend to conduct a driver swap, and they should only join the server within 5 minutes / 2 laps (whichever comes first) of the planned pit stop. This applies only to race sessions. During all other official sessions no spectating shall be allowed on the server. (Live timing and a broadcast shall be provided from Round 1 onward.)
  • Joining / leaving the server. During the qualifying session we ask that all drivers remain on the server (at this point only drivers who shall take part in the session should be on the server) to prevent join / leave messages. as well as lags when cars are loaded / unloaded. We would also prefer if drivers refrained from leaving the server during the warm up session so that we can ensure grid positions are maintained. We recommend that PCs, modems / routers, and anything else that you require is restarted and stable before the start of the official practice session.
  • Safety-first (yellow [blue] / orange / red) zones. For each race yellow [blue], orange and red zones, called Safety-first Zones, shall be defined, if necessary. The track map, in each event thread, shall indicate the locations of these zones, which have the following meanings:
    • Yellow [blue] zone: This is a one off zone that shall cover the first few corners, and will only be active for Lap 1 (and the first lap after any restarts). Its intended to prevent drivers from being overzealous at the start of the race. Overtaking is allowed in the yellow [blue] zone, but only with extreme care, and any accidents will be reviewed before immediate penalties are awarded to the offending car / driver.
    • Orange zone: These zones will be placed in "high-risk" areas, and will be enforced for the duration of the race. Overtaking is allowed in the orange zone, but only with extreme care, and any accidents will be reviewed before immediate penalties are awarded to the offending car / driver. Orange zones shall only be used if necessary.
    • Red zone: These zones will be placed in areas where overtaking is dangerous, therefore it shall not be permitted for the duration of the race. If a driver does overtake or cause an incident in a red zone then they shall be immediately penalised. Red zones shall be seldom used, and saved for only the most extreme cases.
  • Positioning when pitting. Guidance may be provided for positioning cars when pitting, to prevent accidents from occurring when an overtaking car does not realise that another car is moving to enter the pits. This guidance shall be provided according to the track, and only if it is necessary.

Rules & Regulations Addendum - v1.2 - March 6, 2017
  • Full-course yellow. When a full-course yellow is due to come into effect Race Control shall announce "THERE WILL BE A FULL-COURSE YELLOW", before commencing a countdown from "5" down to "1" over TeamSpeak. Drivers should NOT slow down (excessively) during this countdown period, to prevent potential accidents. At the end of the countdown Race Control will state "FULL-COURSE YELLOW IS IN EFFECT"; after this announcement all cars must immediately slow down to pit-lane speed, and have their pit limiters engaged. During the full-course yellow period all cars are expected to continue with caution, at pit-lane speed, and no overtaking shall be permitted except when a car has spun or is moving slowly due to potential damage. Announcements regarding slow moving cars shall be made over TeamSpeak. At the end of the full-course yellow period Race Control will state that the "DANGER HAS CLEARED - RETURNING TO GREEN", perform another countdown from "5" to "1", before calling "GREEN FLAG". Once "GREEN FLAG" has been announced cars can return to racing speed. The pits shall remain open at all times. NOTE: During the full-course yellow period the session will actually remain green, for technical reasons.
  • Re-entering the circuit under a full-course yellow. A driver exiting the pits or returning to the track after an incident must always surrender their position to a car already on track. If a car not "on track" rejoins the circuit alongside a car already on track then the latter (on track) car has the right of way.
  • Physical driver swapping. A physical driver swap, like in-game driver swaps, may only be conducted during a pit stop; at no other point should a driver swap be performed whilst a race is underway. After performing a physical driver swap the team will be required to drive to the end of the pit-lane and wait for an additional 5 seconds (the time for an in-game driver swap) to account for any time that could be gained. Guidance shall be provided, in the opening post of the thread for each round, to indicate where drivers must stop their car to serve the physical driver swap "penalty". The team is responsible for informing Race Control when a physical driver swap is due to be performed, and a steward will oversee the pit stop and ensure that the 5 second "penalty" is served at the end of the pit-lane. Failure to notify Race Control may result in a post-race penalty being applied. During qualifying and warm-up physical driver swapping is not permitted; the same rule also applies to in-game driver swaps for these sessions. [This rule may be subject to change.]
  • Real names on TeamSpeak & RDLMS server(s). All drivers are required to use their real name on TeamSpeak and the rF2 server(s) for the RDLMS, so that staff members are able to easily identify participants. (Please note that this is a general requirement as per the rules when racing at RaceDepartment, in any club event or league.)

Additional Regulations for RDLMS Season 7 (v1.3 - addendum and amendments)
  • Race start procedure. At the beginning of each race / restart there will be two safety cars, one for each class, and these shall lead the cars for a single formation lap before a double-file rolling start. Each safety car will be appropriately positioned on the grid before the start of the race session, and responsible for controlling the pace of the pack to which it has been assigned (approximately pit-lane speed). The safety car for the GT pack will also be responsible for creating a gap between the two packs, to reduced the likelihood of incidents occurring between the two classes once the race has commenced. During the course of the formation lap Race Control shall make separate announcements for each pack. At an appropriate location (a suitable straight before the start / finish line) all cars will be instructed to ensure that they are in position - "ALL CARS, LINE-UP IN FORMATION"; at this point all drivers in the pack must line-up in double file, in the correct position, and close the gap to the car in front. The safety car shall subsequently move aside, and pit limiters must be turned on following an "ALL CARS, ENGAGE YOUR PIT LIMITER" announcement. Race Control will then call "GET READY" before calling "GREEN FLAG", at which point the pit limiter can be disengaged by cars in the pack, and all overtaking shall be permitted. To reiterate, Race Control will make separate announcements to each pack according to its position on the track. Any Prototype cars in the GT pack at the start of the race will be instructed to safely overtake and join the back of their pack once the formation lap is underway.
  • Chat box. The in-game chat / message box must be enabled at all times during a race weekend as this may be used by Race Control for communicating with drivers and teams, either in addition or as an alternative to TeamSpeak. This will not, however, excuse chatting during either the qualifying or race sessions - both are forbidden, and will result in penalties being awarded to the offending team(s).
  • Qualifying switch-over time. Between the qualifying sessions for each class there shall be a 5 minute switch-over period. The start and end of the period shall be announced over TeamSpeak by Race Control. During this time GT cars will be allowed to complete their flying laps and return to the pits; no further timed laps will be permitted, and drivers can press ESC to immediately return to the pits. Any GT cars not in the pits by the end of the switch-over period will receive a penalty at the beginning of the race. At approximately the midway point (this will change based on the track) Race Control will announce that Prototype cars may leave their garages to commence their out-laps.
 
Last edited:
IMPORTANT!

The Additional Regulations for RDLMS Season 7 have now been updated, to v1.3; see here for more information. Changes include an update to the race start / formation lap procedure, details regarding an additional switch-over period between classes during the qualifying session, and an added requirement to ensure that the in-game chat box is enabled during a race weekend. We ask you to please read the updates, and would like to encourage you to ask any questions that you may have regarding the rules & regulations.
 
IMPORTANT!

The Additional Regulations for RDLMS Season 7 have now been updated, to v1.3; see here for more information. Changes include an update to the race start / formation lap procedure, details regarding an additional switch-over period between classes during the qualifying session, and an added requirement to ensure that the in-game chat box is enabled during a race weekend. We ask you to please read the updates, and would like to encourage you to ask any questions that you may have regarding the rules & regulations.
 
ANNOUNCEMENT!

In view of today's rFactor 2 update, which shall introduce the much anticipated DX11 upgrade, I would like to encourage RDLMS participants who opt to test / use DX11 to leave feedback about their experience in the General Discussion thread; if you could please avoid posting such messages in the event thread for Round 2, so that we can ensure this remains on topic, it would be much appreciated. Also, we ask you to please post any questions related to the upgrade, technical or otherwise, either in the main rFactor 2 sub-forum or preferably the Studio 397 forums where you will receive better support and responses; at this stage we know just as much as you do about the forthcoming update, but we shall try our best to answer queries when possible.

A recommendation regarding the use of DX11 for Round 2 of the RDLMS powered by Vesaro shall be made later on in the week. Please bear in mind that while this shall only be an advisory, the guidance that is provided will be based on the general feedback received not only from RDLMS participants but the rFactor 2 community as a whole.

In the meantime, I hope you all enjoy the rest of your day, especially if you have time off for May / Labour / Workers' Day! :)
 
ANNOUNCEMENT!

In view of today's rFactor 2 update, which shall introduce the much anticipated DX11 upgrade, I would like to encourage RDLMS participants who opt to test / use DX11 to leave feedback about their experience in the General Discussion thread; if you could please avoid posting such messages in the event thread for Round 2, so that we can ensure this remains on topic, it would be much appreciated. Also, we ask you to please post any questions related to the upgrade, technical or otherwise, either in the main rFactor 2 sub-forum or preferably the Studio 397 forums where you will receive better support and responses; at this stage we know just as much as you do about the forthcoming update, but we shall try our best to answer queries when possible.

A recommendation regarding the use of DX11 for Round 2 of the RDLMS powered by Vesaro shall be made later on in the week. Please bear in mind that while this shall only be an advisory, the guidance that is provided will be based on the general feedback received not only from RDLMS participants but the rFactor 2 community as a whole.

In the meantime, I hope you all enjoy the rest of your day, especially if you have time off for May / Labour / Workers' Day! :)
 
Status
Not open for further replies.

Top Stories This Month

Racing Club Schedule: September 29th - October 6th
Misc
Racing Club Schedule: September 29th - October 6th
Yannik Haustein
Comments
24
Assetto Corsa EVO: Confirmed Cars & Tracks
Assetto Corsa Evo
Assetto Corsa EVO: Confirmed Cars & Tracks
Yannik Haustein
Comments
123
Le Mans Ultimate Track Guides (Updated)
Guides
Le Mans Ultimate Track Guides (Updated)
OverTake.gg
Comments
82
AI Racing, Rain Line, Physics: Reiza Previews Automobilista 2 v1.6 In New Dev Update
Automobilista 2
AI Racing, Rain Line, Physics: Reiza Previews Automobilista 2 v1.6 In New Dev Update
Yannik Haustein
Comments
136
How to Drive Le Mans Ultimate in VR
Le Mans Ultimate
How to Drive Le Mans Ultimate in VR
Angus Martin
Comments
92
First Assetto Corsa EVO Trailer Confirms Early Access Release Date
Assetto Corsa Evo
First Assetto Corsa EVO Trailer Confirms Early Access Release Date
Luca Munro
Comments
130
BeamNG.drive’s Innovative New Career Mode
BeamNG
BeamNG.drive’s Innovative New Career Mode
Connor Minniss
Updated
Comments
22
Assetto Corsa EVO Early Access Delayed Until 2025
Assetto Corsa Evo
Assetto Corsa EVO Early Access Delayed Until 2025
Connor Minniss
Comments
85
Assetto Corsa EVO Gameplay Reveal Set For 30th September
Assetto Corsa Evo
Assetto Corsa EVO Gameplay Reveal Set For 30th September
Luca Munro
Comments
83
New Content, New Features: Le Mans Ultimate September Update Out Now
Le Mans Ultimate
New Content, New Features: Le Mans Ultimate September Update Out Now
Yannik Haustein
Comments
91

Latest News

Back
Top