• You don't get fast in order to take part in club races, you take part in club races to get fast!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. #GiveAwayFriday. Win a copy of F1 2017 - The Game. Click here to join.

RDLMS S7 | General Information

Discussion in 'RD Le Mans Series by Vesaro' started by Yoeri Gijsen, Dec 19, 2016.

Thread Status:
Not open for further replies.
  1. Yoeri Gijsen

    Yoeri Gijsen

    Messages:
    8,616
    Ratings:
    +856
    Series Announcement
    RDLMS by VESARO Logo.png
    Introduction
    Welcome to a brand new season of the RaceDepartment Le Mans Series! This February - after two years of absence - RaceDepartment's most famous endurance championship is back to restore its former glory and test the endurance skills of both novice and veteran simracers. 2017 will be a wonderful year for those that are in for the long run!

    Features
    In its seventh season RDLMS will once again feature the much-appraised Endurance Series mod by Enduracers, now fully revitalised in rFactor 2, featuring both prototype and GT-cars that will renew memories of the inaugural seasons of RDLMS as well as some of the better Le Mans years of this century.

    The Season 7 championship will be contested over six rounds, ranging from six to 24-hour races, amounting to a total of 66 hours of competition on famous and infamous circuits from all over the globe. Only two out of forty teams will be able to claim a top spot in the RDLMS Hall of Fame in October, 2017. One of them will win the Prototype class, while the other will be the new GT Champion, each having prevailed over at least nineteen rival teams.

    All events will be broadcasted live by RaceDepartment's broadcasting team.

    Quick Links
     
    Last edited by a moderator: Apr 5, 2017
    • Like Like x 7
  2. Yoeri Gijsen

    Yoeri Gijsen

    Messages:
    8,616
    Ratings:
    +856
    The Cars

    Available Classes, Models & Engines
    Class: Prototype

    • Alpine A450b Nissan
    • Gibson 015S Nissan
    • Ginetta Zytek 09S Nissan
    • Ligier JS P2 HPD
    • Ligier JS P2 Judd
    • Ligier JS P2 Nissan
    • Lola B08/80 Judd
    • Lola B09/86 Mazda
    • Lola B11/83 HPD V6
    • Oreca 03 Judd BMW
    • Oreca 03 Nissan
    • Zytek Z11SN Nissan
    Class: Grand Touring
    • Aston Martin V8 Vantage
    • BMW M3 E92
    • Corvette C6.R 2012
    • Ferrari F430 GT
    • Flat6 (Porsche) RSR
    Driver Assists
    • Automatic Clutch: Yes
    • Automatic Gears: No
    • Traction Control: Low & Medium
    • Anti-Lock Braking: No
    • Stability Control: No
    • Spin Recovery: No
    • Steering Assist: No
    • Braking Assist: No
    • Driving View: Cockpit & TV Cockpit
    Car / Skin Pack Downloads
    • RDLMS Endurance Series: v1.0 (alt. link: v1.0)
    • RDLMS Endurance Series: v1.1 (alt. link: v1.1)
    • RDLMS Endurance Series: v1.2 (alt. link: v1.2)
    • RDLMS Endurance Series: v2.0 (alt. link: v2.0)
    • RDLMS Endurance Series: v3.0-beta (alt. link: v3.0-beta)
    • RDLMS Endurance Series: v3.1 (alt. link: v3.1)
    • RDLMS Endurance Series (v4.0) (alt. link: v4.0)
    • RDLMS Safety Car: v1.2
     
    Last edited by a moderator: Aug 14, 2017
  3. Yoeri Gijsen

    Yoeri Gijsen

    Messages:
    8,616
    Ratings:
    +856
    The Schedule

    Season Events
    • Round 0 | 2 Hours of Bahrain
    • Round 0.5 | 2 Hours of Daytona
    • Official Test Race | 2 Hours of Estoril
    • Round 1 | 12 Hours of Interlagos
    • Round 2 | 6 Hours of Silverstone
    • Round 3 | 24 Hours of Le Mans
    • Round 4 | 6 Hours of Road America
    • Round 5 | 12 Hours of Fuji
    • Round 6 | 6 Hours of Sebring
    The event schedule may be subject to change due to the availability of suitable venues such as a modern day Le Mans.

    Session Timetable

    • 10:55 | Race server reboot
    • 11:00 | Official practice (no duplicate cars allowed from this point on!)
    • 11:45 | GT qualifying (30 minutes)
    • 12:15 | Prototype qualifying (30 minutes)
    • 12:45 | Warm-up
    • 13:00 | Race start
    All times are posted in GMT. Daylight Saving Time changes occur between Round 1 and Round 2 for most countries. Find out when your DST changes! Some of the countries revert back towards the end of the season, though most don't (before the season ends, that is).

    Round 0 will be run with a different timetable.


    Season Calendar
    Pre-Season
    19 Dec | Entry list opens for seeded teams by invitation
    23 Dec | Entry list opens for all teams at 7 PM GMT
    02 Jan | RDLMS server opens
    09 Jan | First set of Round 1 teams confirmed
    21 Jan | Round 0 | 2 Hours of Bahrain
    11 Feb | Round 0.5 | 2 Hours of Daytona


    Note that Round 0 & 0.5 are open to any team that aspires the join RDLMS, even if their entry has not been confirmed or even submitted. Please restrict your participation to one car per team and use driver swaps if you wish to field multiple drivers during this race. Premium Membership is however required.

    Official Test Race
    26 Mar | Deadline Official Test Race livery submission
    04 Mar | Official Test Race | 2 Hours of Estoril

    Round 1
    19 Mar | Entry list closes for Round 1
    20 Mar | All Round 1 teams confirmed
    24 Mar | Deadline Round 1 livery submission
    01 Apr | Round 1 | 12 Hours of Interlagos

    Round 2
    24 Apr | Entry list closes for Round 2
    28 Apr | Deadline Round 2 livery submission
    13 May | Round 2 | 6 Hours of Silverstone

    Round 3

    29 May | Entry list closes for Round 3
    09 Jun | Deadline Round 3 livery submission
    24 Jun | Round 3 | 24 Hours of Le Mans

    Round 4
    31 Jul | Entry list closes for Round 4
    11 Aug | Deadline Round 4 livery submission
    26 Aug | Round 4 | 6 Hours of Road America

    Round 5
    18 Sep | Entry list closes for Round 5
    22 Sep | Deadline Round 5 livery submission
    07 Oct | Round 5 | 12 Hours of Fuji

    Round 6

    30 Oct | Entry list closes for Round 6
    03 Nov | Deadline Round 6 livery submission
    18 Nov | Round 6 | 6 Hours of Sebring


    The calendar may be subject to change due to the availability of suitable venues such as a modern day Le Mans.
     
    Last edited by a moderator: Apr 21, 2017
    • Love Love x 2
  4. Yoeri Gijsen

    Yoeri Gijsen

    Messages:
    8,616
    Ratings:
    +856
    The Regulations

    Core Regulations
    Season 7 of the RDLMS will operate in accordance with the 2017 RD League Regulations unless specifically outlined otherwise below.

    Additional Regulations for RDLMS Season 7
    The rules stated in this section act as a championship season specific appendix to the 2017 RD League Regulation as linked above. In case the rules in this section conflict with the 2017 RD League Regulations, the rules stated here override those linked above.
    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. No overtaking is permitted before the start / finish line. 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.
    • Full-course yellow. When a full-course yellow is called by Race Control there will be a countdown from 5 down to 1, over TeamSpeak, before "Full-course Yellow" is announced and enforced. Once in effect all cars must immediately slow to a safe speed slow down to pit-lane speed, and engage their pit limiter. During the full-course yellow period all cars are expected to continue with caution, at a constant speed (i.e. pit-lane speed) 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 period Race Control will state that the danger has cleared, and once again call "Green Flag" following a countdown. The pits shall remain open at all times. NOTE: During the full-course yellow period the session will actually remain green, for technical reasons, and announcements shall be made via TeamSpeak and the rFactor 2 chat box.

    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.)

    Rules & Regulations Addendum - v1.3 - April 30, 2017
    • 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.
    Rules & Regulations Addendum - v1.4 - June 22, 2017
    • Flashing headlights. Flashing of the headlights is permitted during a race, but only within reason. A driver is allowed to flash the car's lights to indicate their presence when lapping, to warn a slower car ahead that they are behind and looking to overtake. In this case it is still the responsibility of the driver who flashes their lights to initiate and perform a safe overtaking manoeuvre without forcing the slower car off their line, and equally the slower car should behave predictably and remain on the racing line when being lapped by a quicker car. However lights must not be flashed to distract another driver - it is forbidden when battling for position - nor in anger or to show frustration. Headlights should not be flashed repeatedly; a single sequence of the lights being flashed up to 4 times within a ~2 second period should suffice for each car that is encountered when lapping, and a second sequence will be acceptable if a driver believes that they have not been seen by the driver in a car ahead.

    Championship Point Scoring System
    Points are scored when a car covers at least 75% of the distance covered by the winning car in its class. Consequently championship standings are kept per class only. Additionally only teams score points. No driver championship standings are kept. Points are distributed per class as follows:
    1. 30
    2. 25
    3. 21
    4. 18
    5. 16
    6. 15
    7. 14
    8. 13
    9. 12
    10. 11
    11. 10
    12. 9
    13. 8
    14. 7
    15. 6
    16. 5
    17. 4
    18. 3
    19. 2
    20. 1
    Championship standings are determined by:
    1. Highest amount of championship points
    2. If 1. does not suffice: Highest amount of first places, then second places, etc.
    3. If 1. and 2. do not suffice: Best result in the longest race
    The rules for Season 7 are still being formulated. As such they may be subject to change.
     
    Last edited by a moderator: Jun 22, 2017
  5. Yoeri Gijsen

    Yoeri Gijsen

    Messages:
    8,616
    Ratings:
    +856
    The Team Owner License Agreement (TOLA)

    What is the TOLA?
    The Team Owner License Agreement (TOLA) is the agreement between the RaceDepartment Le Mans Series (RDLMS) staff and the team owner (licensee) in RDLMS . This agreement is part of the RDLMS license. The license is handed out by the RDLMS staff upon the validation of a team owner's request to enter RDLMS Season 7 and is communicated to the team owner through a private message on the RaceDepartment forums.

    Rights of the licensee
    The licensee has the right to enter one car with the designated startnumber in the designated class in all organised events within the series for the duration of the season, provided the license is not revoked before expiration.

    Terms & conditions for maintaining a license
    • The licensee must choose one car model and engine in the designated class, prior to submitting a livery, to which his team will be bound for the duration of the season, unless otherwise decreed by the RDLMS staff.
    • The licensee must submit a livery for the chosen car model, which meets all the conditions of The Sign-Up Procedure, before the livery submission deadline of the first round he enters his team (with the exception of the Round 0 deadline). The choice of car is final and irrevokable upon the submission of the livery, unless otherwise decreed by the RDLMS staff.
    • The licensee must enter the chosen car, running the submitted livery with the designated startnumber in all official race events for which the entry deadline was met when entry into the series was request.
    • For each official event the licensee must assign a minimum of two (2) and a maximum of six (6) drivers, each of which are Premium Members of RaceDepartment, to drive his car. None of these drivers may already be assigned to a different team in the same class. Changes in the team's line-up can be communicated through this form.
    • The licensee is responsible for the conduct of his drivers on the RDLMS forums, in following procedures and in respecting regulations.
    • A licensee can hold multiple licenses at a time, but no more than one (1) per class.
    • RaceDepartment has the right to revoke any license at any time. Licenses are revoked when the terms and conditions are not met by the licensee. The license automatically expires at the end of the season.
     
  6. Yoeri Gijsen

    Yoeri Gijsen

    Messages:
    8,616
    Ratings:
    +856
    The Liveries

    This section of the post shall outline the process for creating & submitting skins for the RDLMS Season 7.

    NOTE: this shall only contain relevant details regarding how to create and submit skins for the RDLMS, and is NOT a tutorial for creating skins. Information for designing, producing and testing skins may be found here.

    Every team confirmed as an entry for Season 7 of the RD Le Mans Series is required to submit a vehicle skin; failure to do so may lead to a penalty. Each team must supply a skin before the submission deadline of the first round in which they shall participate, so that the livery may be added to the custom skin pack for this league.

    Once a skin pack has been created teams may use their livery if it has been included as part of the pack. At all other times the available default liveries must be used; no other (custom) liveries are permitted to be used on the server.

    The submitted livery must use the template, from the provided RDLMS Templates, corresponding to the team's chosen car model. Elements that have been added to each template by RDLMS staff - number plates, league logo, sponsor logos, etc. - must not be moved; doing so may result in the rejection of your skin. [SEE BELOW FOR UPDATED INFORMATION ABOUT MOVING AND RESIZING ELEMENTS PLACED BY RDLMS STAFF]. Vehicle window skins will be added by RDLMS staff for each skin that has been submitted, and this will overwrite any modifications made to the windows by teams.

    The skin templates for all of the available cars can be downloaded from here:
    The following list specifies each of the cars and the name of the folder in which its template files can be found:

    Prototype
    • Alpine A450b Nissan - RDLMS_P2_Oreca03/2014
    • Gibson 015S Nissan - RDLMS_P2_Zytek
    • Ginetta Zytek 09S Nissan - RDLMS_P2_Zytek
    • Ligier JS P2 HPD - RDLMS_P2_LigierJSP2
    • Ligier JS P2 Judd - RDLMS_P2_LigierJSP2
    • Ligier JS P2 Nissan - RDLMS_P2_LigierJSP2
    • Lola B08/80 Judd - RDLMS_P2_LolaCoupe/2010
    • Lola B09/86 Mazda - RDLMS_P2_LolaCoupe/2010
    • Lola B11/83 HPD V6 - RDLMS_P2_LolaCoupe/2011
    • Oreca 03 Judd BMW - RDLMS_P2_Oreca03/2014
    • Oreca 03 Nissan - RDLMS_P2_Oreca03/2014
    • Zytek Z11SN Nissan - RDLMS_P2_Zytek
    Grand Touring
    • Aston Martin V8 Vantage - RDLMS_GTE_V8Vantage
    • BMW M3 E92 - RDLMS_GTE_M3E92
    • Corvette C6.R 2012 - RDLMS_GTE_C6R
    • Ferrari F430 GT - RDLMS_GTE_F430GT
    • Flat6 (Porsche) RSR - RDLMS_GTE_F6RSR
    Setting Your Car Number

    Each main body template skin file includes 3 groups named 'Number Template 1', 'Number Template 2', and 'Number Template 3'. Within each of these groups is a text layer named 'Your Number Here!' (or similar) - each one of these layers must be selected in turn, and the typing tool must be used to change the value to your car number.

    All 3 layers must be set with your correct car number, else your skin shall be rejected.

    The font, text size, text colour, background colour and position of the number plate must not be altered in any way, else your skin shall be rejected.

    File Naming Convention


    Each skin file must be exported and saved as a .dds file from the graphics editor of your choice. Any skin file not in this format will NOT be accepted.

    The main body file (all of which are named #.psd as templates) MUST be exported to .dds and included as part of the skin submission for your chosen car. Failure to include this file will mean that your skin shall be rejected. Meanwhile, only those "extra" files that have been modified should be included as part of the submission; for any extra files that are excluded the corresponding default extra will be used.

    The skin template files have been named in such a way that the following must be done before submitted your files:
    • "#" should be replaced with your car number for the necessary skin files in the folder for your chosen car (refer to the above list of cars and folder names to determine which template files you should use)
    For example, the files to be submitted for car #16 would be:
    • 16.dds
    • 16EXTRABODY.dds
    • 16WINDOW.dds
    • ...(etc.)
    All skin files to be used for your chosen car must be added to and sent as a single compressed file (.zip, .rar & .7z will be accepted). However, the files themselves must not be packed - .mas files will NOT be accepted. The name of this compressed file must conform to the following format: <car_number> - <car_name_from_list> (see here for list of car names; replace any invalid file name characters, such as "/", with "_"). For example, the name of the compressed file containing the skin files for the #16 Lola B08/80 Judd would be as follows: 16 - Lola B08_80 Judd

    Painting Rules
    • Liveries must not contain any explicit images or graphics, nor any profanities, political propaganda, biased messages, or any other material deemed inappropriate or offensive
    • Drivers' names may be added to the door frame of your chosen car (on one or both sides), but they must not appear anywhere else (unless they form part of the team name)
    • The maximum image resolution is 2048 x 2048 pixels
    • The maximum size of submitted files is 20MB (this limit applies to all .dds files in the compressed file, once these files have been extracted - this is NOT the permitted size for each file or the size of the compressed file)
    Teams that do not comply with these rules will have their submissions rejected, and depending on the severity of the breach disciplinary action may be taken - this includes potential disqualification from the league and / or a RaceDepartment ban.

    Please send your skin submissions to either @Daiman Patel or @Dennis by sending a PM titled: RDLMS Skin - <car_number> - <team_name>. For example, the title of the PM for team RedShift Racing, with car #16, will be as follows: RDLMS Skin - 16 - RedShift Racing. If your team has entered more than one car then a separate PM must be sent for each car. The PM should contain a download link created via Google Drive, OneDrive, Dropbox, Mega, or a similar file sharing repository, and the name of the chosen car (from the list of those that are available) must be specified. Please ensure that your skin works before it is submitted.

    If you have any questions please do not hesitate to contact either @Daiman Patel or @Dennis via PM with your query, and we shall do our best to answer as quickly as possible.

    Issue when using GIMP

    There is a problem with text layers when loading .PSD files into GIMP - the plugin for reading a .PSD file is currently unable to distinguish text layers from other layers, therefore the text cannot be edited. This feature was once available, but following changes to the PSD format and the slow evolution of GIMP there are a number of similar incompatibilities.

    When using GIMP you must do the following to add your number, in place of the existing (placeholder) layers:
    • Set the layer visibility so that each of the number (placeholder) layers is invisible
    • Create a new text layer in its place, with the following properties
      • Font: Arial Bold Condensed
      • Size: 108px
      • Kerning: -5.0
    • Duplicate this text layer - create two more copies
    • Align a text layer over each of the number plates
    • Ensure that the text layers are below the alpha layer - it would be best to place a text layer within each of the 'Number Template #' layers

    IMPORTANT
    • If you wish to submit an updated skin for any subsequent rounds of this series then you may do so; the files must be received in the correct format before the submission deadline of an upcoming round, else it will not be included until the following round. Each time a new skin is submitted this will be the livery that shall be used for your car.
    • Due to the way in which the templates and cars have been designed, there are inconsistencies in the size of number plates and logos between templates. As a result these elements appear to be larger on some cars than on others. Therefore we have taken the decision to allow you to resize and move (only along the panel on which it is already placed) elements placed by RDLMS staff on your car; they must still be a sensible size, and continue to be clearly visible. The background colour of the number plate must NOT be changed.
    • Custom skins may be submitted for Round 0, however this is not a mandatory requirement. Any submissions that are received before 15th January 2017 will be included as part of the custom skin pack for Round 0, and shall continue to be used for the remainder of the league unless an update is submitted. All skins for Round 1 must be received before 29th January 2017; failure to submit a skin may result in your disqualification from this round.
    • Skin file updates may continue to be submitted at any time.
    • The skin submission PM, for each car that has been entered to partake in this series, must be titled: RDLMS Skin - <car_number> - <team_name>.
    • The name of the chosen car (from the list of those that are available) must be specified in each skin submission PM, alongside the download link to the skin files.
     
    Last edited by a moderator: Jan 8, 2017
    • Like Like x 5
  7. Yoeri Gijsen

    Yoeri Gijsen

    Messages:
    8,616
    Ratings:
    +856
    Update - January 21, 2017
    • Round 1 has been moved two weeks down the line to March 4, 2017
    • Deadlines for Round 1 have also been moved by up to four weeks
    • Deadlines for Round 2 have been moved by two weeks
    Please check here to see new deadlines and dates.

    These changes have been made to allow staff members to implement necessary changes in light of the news regarding our new sponsor, and also to give more teams the opportunity to sign up before the start of the league.
     
    Last edited by a moderator: Feb 10, 2017
    • Like Like x 2
  8. Daiman Patel

    Daiman Patel
    Damimam Staff Premium

    Messages:
    3,680
    Ratings:
    +2,034
    Update - February 10, 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.0 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.
    5. Race start procedure. At the beginning of each race a safety car shall lead the grid away 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. No overtaking is permitted before the start / finish line.
    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.

    Additional Regulations for RDLMS Season 7 (v1.1 - addendum and amendments)
    • 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.
    • 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.)
    • 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.
    • Full-course yellow. When a full-course yellow is called by Race Control there will be a countdown, over TeamSpeak, before it is enforced. Once in effect all cars must immediately slow to a safe speed, and engage their pit limiter. During the full-course yellow period all cars are expected to continue with caution, at a constant speed (i.e. pit-lane speed), and no overtaking shall be permitted. At the end of the period Race Control will state that the danger has cleared, and once again call "Green Flag" following a countdown. The pits shall remain open at all times. NOTE: During the full-course yellow period the session will actually remain green, for technical reasons, and announcements shall be made via TeamSpeak and the rFactor 2 chat box.
     
    Last edited: Apr 24, 2017
    • Like Like x 3
  9. Daiman Patel

    Daiman Patel
    Damimam Staff Premium

    Messages:
    3,680
    Ratings:
    +2,034
    Update - March 6, 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.1 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.
    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 & Regulation 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 / orange / red) zones. For each race yellow, 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 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 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.
    • Full-course yellow. When a full-course yellow is called by Race Control there will be a countdown, over TeamSpeak, before it is enforced. Once in effect all cars must immediately slow to a safe speed, and engage their pit limiter. During the full-course yellow period all cars are expected to continue with caution, at a constant speed (i.e. pit-lane speed), and no overtaking shall be permitted. At the end of the period Race Control will state that the danger has cleared, and once again call "Green Flag" following a countdown. The pits shall remain open at all times. NOTE: During the full-course yellow period the session will actually remain green, for technical reasons, and announcements shall be made via TeamSpeak and the rFactor 2 chat box.

    Additional Regulations for RDLMS Season 7 (v1.2 - addendum and amendments)
    • 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.)
     
    Last edited: Apr 30, 2017
  10. Frank

    Frank
    Administrator Staff Premium

    Messages:
    3,171
    Ratings:
    +889
    Update - April 5th, 2017
    The following additions and amendments have been made to the Rules & Regulations for the RDLMS.
    • Due to issues with driver swaps and rejoining the race in Round 1, drivers will be allowed to re-enter the server with a fresh car from Round 2 onward. Before exiting the pits, the team / driver must seek permission from the stewards and explain the circumstances; the stewards will review the situation and a give a verdict, based on which the car will or will not be allowed to continue in the race. Depending on the situation (if the disconnection follows an incident in which damage may have been sustained) a lap / laps will be deducted from those that have been completed by the car in question. Failure to notify the stewards, even if the disconnect is a result of network issues, will result in a penalty being issued. Also, the driver who rejoins the server must still be the person who originally disconnected, else the rejoin will be unsuccessful.
     
    • Like Like x 1
    • Love Love x 1
  11. Daiman Patel

    Daiman Patel
    Damimam Staff Premium

    Messages:
    3,680
    Ratings:
    +2,034
    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: May 6, 2017
    • Like Like x 5
  12. Daiman Patel

    Daiman Patel
    Damimam Staff Premium

    Messages:
    3,680
    Ratings:
    +2,034
    Update - June 22, 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.3 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.)

    Rules & Regulations Addendum - v1.3 - March 30, 2017
    • 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.

    Additional Regulations for RDLMS Season 7 (v1.4 - addendum and amendments)
    • Flashing headlights. Flashing of the headlights is permitted during a race, but only within reason. A driver is allowed to flash the car's lights to indicate their presence when lapping, to warn a slower car ahead that they are behind and looking to overtake. In this case it is still the responsibility of the driver who flashes their lights to initiate and perform a safe overtaking manoeuvre without forcing the slower car off their line, and equally the slower car should behave predictably and remain on the racing line when being lapped by a quicker car. However lights must not be flashed to distract another driver - it is forbidden when battling for position - nor in anger or to show frustration. Headlights should not be flashed repeatedly; a single sequence of the lights being flashed up to 4 times within a ~2 second period should suffice for each car that is encountered when lapping, and a second sequence will be acceptable if a driver believes that they have not been seen by the driver in a car ahead.
     
    • Like Like x 1
    • Love Love x 1
Thread Status:
Not open for further replies.