Regulations of the SimRaceCommunity

Announcements for SRC events

1 Competition regulations

The SRC season events, e.g. GT3 World Tour, are carried out according to the following provisions in connection with the general invitation to tender that applies to the season.

1.1 Validity of this regulation

By registering, the drivers or legal guardians declare that they have read, understood and accepted the set of rules in full.

1.2 Wording and types of adressing

For better readabilty we will only use the male form of adressing words and terms We expressly point out that female participants are also admitted and welcome. Basically, we use the personal form of address “you”. If this is not desired, the league management must be informed in writing.

2 Participation

2.1 General

The SRC season events are one or more online championships. The organizer is SRC Commerce UG (limited liability). Anyone who owns the rFactor2 game and all the additional content required and is at least 16 years old is entitled to take part in the championship. In exceptional cases, drivers from the age of 12 or younger can also participate (consent of legal guardians required!). A suitability test is also carried out for younger drivers. Furthermore, every driver in the forum with a real name, e.B. Max Mustermann, without any additional (clan) abbreviations, numbers, special and fill characters, must register and apply for a cockpit. Basically, at the Simracecommunity you always have the obligation to register with the real name in Teamspeak, Discord, the forum and the servers !

2.2 Annual fee

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

From September 1st, 2021, interested drivers can pay an annual fee of 40 EUR (including 19% VAT) per season year (September to September). With payment of this annual fee, the respective driver is entitled to participate in all seasons, fun events, special series and special events hosted by the SRC. There are no additional 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 joining the server

If a driver does not appear on the server with the correct name, he must correct this state immediately, at the latest when requested by an admin. If he does not comply with any request, he can be removed from the server without comment. No competitor may use another competitor’s vehicle on the official race days. We also ask that you remove any unnecessary spaces in the driver’s name. This is not relevant for funevents.

3. Skins, car liveries

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.

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

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

The skins are to be sent to the address given in the respective advertisement.

3.2 Special requirements

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

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

Trademark rights for all logos used must be submitted by the author’s permission along with the regular files!

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

car.dds / car_region.dds / car.json

Additional skin files can be sent in voluntarily and will be incorporated into the final mod after checking the SRC. This does not apply to windscreen banners as well as the entire rear window of the vehicle and the flaps of the rear spoiler.

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

3.4 Skinupdates

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

4 Sub-series / Funevents

4.1 Start authorization for fun events and side series

Any driver who has paid the full annual fee of the SRC is entitled to participate in all fun events and off-season events without restrictions.

The league management reserves the right to suspend these rules in exceptional cases and to issue a different requirement for laps driven, depending on the length of the route. These are then announced in the corresponding thread in the forum.

4.2 Training

If the organizer can do, a training server for free training is provided all day and all the time between the races. Free trainings are generally not streamed. Special training and test days will be announced in the racing calendar. Special trainings can be streamed by the organizer.

4.3 Qualification

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

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

  • 1 server 24/7 online (if possible)
  • Track depending on the event
  • no streaming from the SRC is planned
  • no prizes and honours are currently planned
  • no mandatory rounds are necessary
  • no racing commission is organized by the SRC
  • there will be a simple race evaluation with championship rating

Further rules:

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

5 Vehicle lighting

At evening or night events, the vehicle lighting must be switched on by all participants. If the switching on of the vehicle lighting is disregarded, the simulation will issue a DQ penalty.

6 Rejoin

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

7 Driving regulations and rules of conduct

7.1 Communication

7.1.1 Generally

Insults or inappropriate dealings with each other in any form of communication between the Simrace Community and the Organizer are strictly prohibited. The Racing Commission reserves the right to issue penalties for inappropriate handling of the current event.

Inappropriate forms of communication include:

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

entering “foreign” team channels in order to deliberately disrupt / distract them or insult them during the race

any offensive forms of address in forum, chat, protests and Teamspeakchannels

The penalties are imposed directly or during a race evaluation without warning. Such unsportsmanlike conduct can be reported to the league management via the protest form or by email to rennkommission@simracecommunity.eu. Screenshots or evidence of the violation are necessary for a punishment by the race management. Ingame-Chat-Insults during the training or event must be made with the date and time and will be based on the server log.

7.1.2 Teamspeak

On the race days, the presence with real names in the Teamspeak is mandatory!

Server: 81.169.178.218

Password:

SRC@GTM15

During an event, announcements can be made by the race management using the TS whisper function. In order for this to work smoothly, we recommend that all participants remove the checkmark for “Always open Whisper history when they are whispered” under “Options / Whispers”!

7.1.3 Forum / Website / Comments / Chat

Each participant has the duty to inform himself appropriately about the events. The main portal for this is messages on the Simrace Community Forum and the website www.simracecommunity.eu.

7.2 Ban on chat and quick chat

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

7.3 Generally

The usual accepted principles and codes of conduct apply in racing – it is to act with fairness and overview. Accidents and collisions must be avoided by all means at their disposal. Drivers who leave the track may only return to the track in such a way that other participants are not endangered or hindered. Vehicles on the track always take precedence!

7.4 Gentlemen‘s Agreement

In principle, the Gentlemen Agreement applies – after one should treat one another on the track with the highest possible respect. Should a driver turn another one or push him off the track and gain an advantage, he should return this advantage to the driver, i.e. he should let the harmed driver pass through again at an appropriate place, within a lap.

7.5 Duel

In a duel, the opponent’s line must be respected at all times. If one driver has managed to position himself on an equal footing, next to another, both have to keep their line. Drivers are generally on an equal footing if both vehicles are at the same height or overlap at least half of them. In order to defend one’s own position, it is allowed to drive the so-called battle line.

A one-time line change is allowed before curves; a second only if it is excluded for the opponent to be forced to change lines or extraordinary braking manoeuvres. Changing the line multiple times to block the enemy is prohibited. In addition, a lane change is punished too late if this makes it impossible for the following vehicle to react and avoid a collision.

7.5.1 Duel OK

Duel OK

7.5.2 Racing accident: Both vehicles behave incorrectly

Racing accident: Both vehicles clearly overlap

7.5.3 Red vehicle causes the accident

The red vehicle intersects the line of the yellow vehicle

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.

yellow vehicle causes the accident: the yellow vehicle intersects the line of the red one.

7.6 Lapping

In the case of lapping cars, the driver of the vehicle in front shall let the lapping car pass in an appropriate spot (curve exit, straight line) and, if necessary, reduce the speed reasonably slightly. Displaying the overtaking by light horn is permitted.

7.7 Round back

If a fast lapped driver tries to gain a lap back, this should also be allowed for fairness reasons, unnecessary fights should be avoided. The driver who is unlapping himself should be clearly faster and should also pass his opponent cleanly through a clearly placed overtaking manoeuvre.

7.8 Pitstop

In the pit lane, the flowing traffic in the fast lane takes precedence over vehicles at the pit court and in the garage. Vehicles coming out of the box may not use the route in full width until the end of the solid white/yellow line marking the extended pit exit. A crossing of the white line is punished. Vehicles can collide in the pit area, causing damage to the same. There must be sufficient space for vehicles behind and for parking.

7.9 Flags

All flags are to be observed!

7.9.1 Yellow phase / yellow flag

As soon as there is a yellow phase, there is an absolute overtaking ban and the speed must be adjusted appropriately. Started overtaking processes must be completed before the area marked with the yellow flag is reached, or canceled prematurely. If an accident has occurred on the route, the corresponding section of the route is yellow, if a driver reduces his speed “insufficiently”, the corresponding driver is punished. The accident site should be carefully and carefully passed.

7.9.2 Green Flag

The green flag indicates that an area previously marked with a yellow flag is released again.

7.9.3 Blue Flag

The blue flag indicates that a faster vehicle is approaching, which is ready to lap. The faster driver should be let through as quickly as possible at the next opportunity, within one race lap.

7.9.4 Black Flag

A driver who is shown the black flag is disqualified and normally moved 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 on his pit court.

8 Race evaluation

The race evaluation is carried out by the XML and VCR files recorded by the server. The server VCR will be available for download as soon as possible after the race in the league forum. Championship stands can be viewed here.

9 penalties

For the season, we have created a penalty catalogue to standardise the work of the race management and to bring more transparency for all drivers in the assessment of individual incidents. The penalty catalog serves only as a guideline and is based on the DMSB penalty catalog.

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

10 Protest

10.1 General

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

10.2 Filing a protest

Protests are only processed in writing. These must be sent to the race management using a protest form. Protests by uninvolved people 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, at multi-part race events, the affected races are to be mentioned. The protester briefly describes what is happening in the “Description” area. If possible, the driver positions will be given. Personal assessments are to be avoided and are assessed as influencing the race commission. Such protests are rejected without comment!

10.4 Race Committee decisions

If the race 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 involve a team member of one of the registered teams in rotation by rotation in order to remain as neutral as possible.

The racing commission can also review, evaluate and award penalties without receiving protests.

10.5 Situations worthy of protest and unworthy of protest

Situations worthy of protest are incidents in which the protest opponent, either intentionally or for the purpose of his own advantage, causes situations that give him an advantage or accept the consequences of his actions. This includes situations in which it can be seen that a driver does not have sufficient visibility into the race and causes situations worthy of protest.

Situations that arise from minor driving errors and where it is clear that the polluter does not act intentionally or accept the consequences are not worthy of protest.

10.6 Prohibited Protests

Protests against the decisions of the racing commission are inadmissible.

11 Server Problems

The race management strictly differentiates between client-side (homemade) problems and server problems. Due to client-side problems on the race day of 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 lead to irregular and non-compliant racing conditions for one or more participants. If, contrary to expectations, server problems arise in qualifying, warm-up or racing, the following rule applies: If problems occur during or after qualification, the previously experienced positions are set on the server.

If the server fails in the race up to a length of 50%, the race will not be counted and will not be repeated. A race that is not rated has no influence on the results of the strikes. If necessary, after a server failure on our backup server, the race can be restarted in the form of a “safety car phase” with the last recorded status.

There is no overtaking in 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 allowed 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 regulations.

a) Driver equipment

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

It is imperative to use a headset (headphones with an integrated microphone) for communication.

b) Software terms

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

Timings

All Championships

Mitgliedschaft

Discord