The SRC
Regulations.

Calls for SRC events

• SRC GT3 World Tour RFactor2
• SRC GT3 Ultimate Tour LMU
• SRC GT3 Challenge iRacing

1 Competition regulations

The SRC Seasonal events, e.g. GT3 World Tour, are carried out in accordance with the following provisions in conjunction with the framework announcement applicable to the season.

1.1 Validity of these regulations

By registering, the drivers or legal guardians declare that they have completely read, understood and accepted the regulations.

1.2 Wording and Personal forms

In favor of readability, the distinction between female and male forms of address is omitted and the male form is used uniformly. It is expressly pointed out that female participants are also permitted and desired. We generally use the personal form of address “Du”. If this is not desired, the league management must be informed in writing.

2 Participation

2.1 General

The SRC seasonal events are one or more online championships. The organizer is SRC Commerce UG (limited liability). Anyone who owns the rFactor2 game and all required additional content and is at least 16 years old is entitled to take part in the championship. In exceptional cases, drivers aged 12 or younger can also take part (consent from legal guardian required!). For younger drivers, a suitability assessment is also carried out. Furthermore, every driver must register in the forum with their real name, e.g. Max Mustermann, without any other (clan) abbreviations, numbers, special or filler characters, and apply for a cockpit. In principle, you are always required to register with your real name in the Simrace Community in Teamspeak, in the forum and on the servers!

2.2 annual fee

There are free and paid events. Further information can be found in the announcements for the series.

Since September 1st, 2021, interested drivers can pay an annual fee of EUR 40 per season (September to September) (including 19% VAT). By paying this annual fee, the respective driver is entitled to participate in all seasons, fun events, special series and special events organized by the SRC. There are no further costs. The billing period is September to August of the following year. A GT3 summer and winter season are always included!

2.3 rFactor 2 and entering the server

If a driver does not appear on the server with the correct name, he must correct this situation immediately, at the latest upon request by an admin. If he does not comply with any request, he can be removed from the server without comment. No participant in the championship is allowed to use another participant's vehicle on the official race days. We also ask that you remove any unnecessary spaces in the driver name. This does not apply to Funevents.

3. Skins, vehicle paintwork

3.1 Specifications / Acceptance

To ensure good DX11 compatibility, the skins must be created in the following format:

DDS files for the skin with 4096×4096 pixels Important: Select “DXT5 8bpp interpolated alpha” when saving, MipMaps = all The size of the number plates of the SRC and the specified sponsors

SRC logos and number plates may not be changed or moved on the vehicle.

One number plate is attached to the driver and "passenger side", additional number plates (front or rear area) may be placed voluntarily.

The SRC gives uniform disc skins/banners, which can contain the league logo and the driver name as well as the registered vehicle number.

The skins must be sent to the address stated in the respective advertisement.

3.2 Special requirements

The design used must not violate netiquette, be offensive and/or offend other people. It must not violate applicable law or morality. Cigarette advertising, even in modified form, is prohibited.

By sending the design used to the race management, participants assure that they have observed any copyrights of images, logos, advertising or the entire skin and that they do not violate any copyrights that may be thereon.

Trademark rights for all logos used, permission from the author must be sent along with the regular files be!

3.3 The following files are required for a complete vehicle skin:

fahrzeug.dds / fahrzeug_region.dds / fahrzeug.json

Other skin files can be submitted voluntarily and will be incorporated into the final mod after the SRC has checked. Excluded are windshield banners as well as the entire rear window of the vehicle and the flaps of the rear spoilers.

The race management reserves the right to reserve additional areas of the vehicles for its own lettering or sponsors in order to be able to place our/their advertising there.

3.4 Skin updates

Skins and skin changes are generally collected and at a suitable time updated.

4 Minor series / fun events

4.1 Entitlement to start for fun events and side series

Every driver who has paid the SRC annual fee in full is entitled to take part in all fun events and off-season events without restrictions.

The league management reserves the right to override these rules in exceptional cases and, depending on the length of the route, one to announce different specifications for laps driven. These are then announced in the corresponding thread in the forum.

4.2 Training

If the organizer is able, a training server will be made available for free training all day and the entire time between the races. Free training sessions are generally not streamed. Special training and test days will be announced in the race calendar. Special training sessions can be streamed by the organizer.

4.3 Qualification

The time/number of laps for side series events and fun events can be found in the respective race calendar.

4.4 Race schedule/rules for FunCups, free events and Secondary series

• 1 server 24/7 online (if possible)
• Rout depending on the event
• there is no streaming planned by the SRC
• there are currently no winners and honorary prizes planned
• there are no compulsory rounds necessary
• there will be no race commission organized by the SRC
• there will be a simple race evaluation with championship ranking

Further rules:

• fair driving is required
• Drivers who cannot show themselves fairly on the track by other participants in the League management must be reported. If more than 2 complaints are received about a driver, they will be permanently banned from the Funcup/side series server. The same applies to participants who do not adhere to the polite etiquette of the Simrace community and are reported.

5 Vehicle lighting

During evening or night events, all participants must turn on the vehicle lighting at all times. If switching on the vehicle lighting is ignored, the simulation will issue a DQ penalty.

6 Rejoin

Unless otherwise stated for individual events, server rejoin is possible in all stages of a race. SRC assumes no liability for incorrect use of the rejoin procedure or incorrect rejoin process.

7 Driving regulations and rules of conduct

7.1 Communication

7.1.1 General

Insults or inappropriate treatment of one another in any form of communication between the Simrace community and the organizer are strictly prohibited. The racing commission reserves the right to impose penalties for inappropriate interaction with one another during the ongoing event.

An inappropriate form of communication includes:

Chatspam during the event, regardless of the phase of the event

Entering “foreign” team channels in order to specifically disrupt/distract or hinder them during the race insult

any insulting forms of address in the forum, chat, protests and teamspeak channels

The penalties will be imposed without warning directly or during a race evaluation. Such unsportsmanlike behavior can be reported to the league management using the protest form or by email to rennkommission@simracecommunity.eu. Screenshots or witness evidence for reporting the violation are necessary for punishment by the race management. In-game chat insults during training or events must be stated with the date and time and will be based on the server log.

7.1.2 Teamspeak

On race days, attendance with real names in teamspeak is mandatory!

Server: 88.99.193.85

Password:

SRC@GTM15

During an event, announcements from the race management can be made via the TS whisper function. To ensure that this works smoothly, we recommend that all participants tick “Always open whisper history when whispered to” under “Options/Whispers”. to be removed!

7.1.3 Forum/Website/Comments/Chat

Every participant has the obligation to obtain appropriate information about the events. The main portal for this are messages in the Simrace Community Forum and the website www.simracecommunity.eu.

7.2 Ban on chat and quick chat

After the qualification session or racing session has started, there is a strict ban on chat and quick chat until “every” driver has finished their race! Violation will result in a subsequent penalty. The only exception is instructions from the race organizers!

7.3 General

The generally accepted principles and rules of conduct in racing apply - you must act with fairness and overview. Accidents and collisions must be avoided using all available means. Drivers who leave the track are only allowed to get back on the track in a way that does not endanger or hinder other participants. Vehicles on the track always have priority!

7.3.1 Briefing and bulletin regulations

All participating drivers are required to be present at the briefing for the respective race. If a driver cannot be present or arrives late, he or she must take care of obtaining the latest information from the race management. In the briefing, route-specific adjustments to the race taking place can also be announced verbally.

Bulletins will be announced for permanent changes to the regulations or announcement in the usual places.

7.4 Gentlemen's Agreement

The gentlemen's agreement generally applies - after you should treat each other with the greatest possible respect on the route. If a driver turns or pushes another off the track and thereby gains an advantage, he should give this advantage back to the driver, i.e. he should let the injured person pass again at a suitable place within one lap.

7.5 Duel

In a duel, the opponent's line must be respected at all times. If a driver has managed to position himself equally next to another, both have to hold their line. As a rule, the drivers are on equal footing if both vehicles are at the same height or if they overlap at least half. To defend your own position, you are permitted to use the so-called battle line.

A single change of line is permitted before corners; a second only if it is impossible for the opponent to be forced to change lines or make extraordinary braking maneuvers. Changing the line multiple times to block the opponent is prohibited. In addition, changing lanes too late will be penalized if this makes it impossible for the vehicle behind to react and avoid a collision.

7.5.1 Duel okay

7.5.2 Racing accident: Both vehicles behave incorrectly

7.5.3 Red vehicle causes the accident

The red vehicle intersects the line of the yellow vehicle

7.5.4 d) yellow vehicle causes the Accident

The yellow vehicle intersects the line of the red one.

7.6 lapping

When lapping, the driver of the vehicle in front must make room for the person being lapped at a suitable place (exit of a curve, straight) and, if necessary, reduce the speed slightly as appropriate. Indicating the readiness to overtake by flashing the headlights is permitted.

7.7 Lap back

If a fast lapped driver tries to lap back, he should be allowed to do so for reasons of fairness; unnecessary fights should be avoided. The driver who is rounding back should be clearly faster and also pass the car in front cleanly through a clearly placed overtaking maneuver.

7.8 Pit stop

In the pit lane, flowing traffic has priority over vehicles in the pit area and in the garage. Vehicles coming out of the pits are only allowed to use the full width of the track after the end of the solid white/yellow line that marks the extended pit exit. Crossing the white line will be punished. Vehicles can collide in the pit area, causing damage to them. There must be enough space for following and parked vehicles.

7.9 Flags

All flags must be observed!

7.9.1 Yellow phase/yellow flag

As soon as there is a yellow phase, overtaking is absolutely prohibited and the speed must be adjusted appropriately. Overtaking maneuvers that have begun must be completed or stopped prematurely before reaching the yellow flag area. If an accident has occurred on the route, the relevant section of the route is yellow. If a driver reduces his speed “insufficiently”, the driver in question is penalized. The scene of the accident should be passed carefully and carefully.

7.9.2 Green Flag

The green flag indicates that an area previously marked with a yellow flag has been reopened.

7.9.3 Blue Flag

The Blue Flag indicates that a faster vehicle is approaching, which is approaching is ready to lap. The faster driver is to be allowed to pass as quickly as possible at the next opportunity within a racing lap.

7.9.4 Black Flag

A driver who is shown the black flag is disqualified and normally transferred directly from the simulation back to the garage. If the simulation does not implement the black flag, the driver must drive his vehicle into the pits and park it in his pit space.

7.9.5 Drive against the direction of travel

If a driver drives against the direction of travel on the track or crosses the track against the direction of travel and thereby gains an advantage or endangers other drivers, he will be disqualified. If the disqualification does not come automatically from the simulation, it will be announced by the race commission, either immediately or subsequently.

8 Race evaluation

The race evaluation is carried out using the XML and VCR files recorded by the server. The server VCR will be made available as a download in the league forum as quickly as possible after the race. Championship standings can be viewed here .

9 Penalties

We have created a catalog of penalties for the season in order to standardize the work of the race management and to bring more transparency to the evaluation of individual incidents for all drivers. The catalog of penalties serves only as a guideline and is based on the DMSB catalog of penalties.

If it is possible to set up a live racing commission, this will be announced in the forum.

10 Protest

10.1 General

Any misconduct that does not comply with the rules can be filed for a period of 48 hours after the 24-hour blocking period has been observed. Protests that are not submitted within this two-day period will be deleted without comment. This also applies to protests that are submitted too early. Specifying the race time based on the server VCR is mandatory. In addition, for two-part races, the respective race must be specified.

10.2 Submit a protest

Protests will only be processed in writing. These must be sent to the race management using a protest form. Protests from people not involved will not be recognized. The protest form is available at https://simracecommunity.eu/protestformular/.

10.3 Protest Format

The names of the protagonists involved, as well as the respective timecode/time stamp, in the case of multi-part race events, the affected race must be mentioned. The protester describes the event briefly and objectively in the “Description” section. If possible, the driver positions will be provided. Personal evaluations are to be avoided and will be seen as influencing the racing commission. Such protests will be rejected without comment!

The time code can be found in the server replay and can be found at the following point in the in-game replay:

10.4 Decisions of the racing commission

If the racing commission has to decide on a protest, it examines the scene and announces a decision on the current situation in the forum. It is planned to rotate a team member from one of the registered teams to the RK in order to maintain the greatest possible neutrality.

The race commission can view, evaluate and award penalties to situations even without a protest being received.

10.5 Situations worthy of protest

Situations worthy of protest are incidents in which the protesting opponent Either intentionally or for the purpose of his own advantage, causes situations that give him an advantage or accepts the consequences of his actions with approval. This also includes situations in which it is clear that a driver does not have a sufficient overview of what is happening in the race and creates situations that warrant protest.

10.6 Inadmissible protests

Protests against the decisions of the racing commission are inadmissible.

Protests from third parties who are not involved in the situation will not be taken into account. (Team bosses excluded, for the team's own drivers)

11 Server problems

The race management strictly differentiates between client-side (home-made) problems and server problems. Due to client-side problems on race day for individual drivers, there is no change in the course of the race day.

Server problems exist when it is clearly evident that technical problems on the game server are causing irregular racing conditions that do not comply with the regulations for one or more participants. If, contrary to expectations, there are server problems in qualifying, warm-up or race, the following rule applies: If problems occur during or after qualification, the previously experienced positions on the server will be set.

If the server fails in the race up to the length of 50%, the race will not be counted and will not be repeated. A non-ranked race has no influence on the cancellation results. If necessary, after a server failure on our alternative server, the race can be restarted in the form of a “safety car phase” with the last status shown.

There is a ban on overtaking on the first lap and the vehicles must line up in the single file. The leader sets the pace. The leader then releases the race at the start/finish line. Overtaking is only permitted once the start-finish line has been passed.

12 Technical regulations

Anything not expressly permitted by these regulations is prohibited. Permitted changes must not result in unauthorized changes or violations of the regulations.

a) Driver equipment

It is assumed that a compatible steering wheel and pedals are used.

For communication it is urgently necessary to use a headset (headphones with an integrated microphone).

b) Software Regulations

Each driver is responsible for owning the simulation to be used and other third-party software (if required), as well as their licenses.