The Virtual Racing Endurance Championship Series goes into the next round. It's off to the Adennen. The challenging track will challenge the drivers of the GT3 and GT4 classes with the characteristics of the track, but possibly also with some freak weather. The outcome of the race is just like the weather forecast: unpredictable.
1. General Information
1.1.1 GT3 class:
AMR V12 Vantage GT3
AMR V8 Vantage GT3
Audi R8 LMS EVO
Bentley Continental GT3
BMW M6 GT3
Ferrari 488 GT3 EVO
Honda NSX GT3 EVO
Lamborghini Huracan GT3 EVO
Lexus RC F GT3
McLaren 720s GT3
Mercedes AMG GT3
Mercedes AMG GT3 EVO
Nissan GT R Nismo GT3
Porsche 991 GT3 R
Porsche 991 II GT3 R
1.1.2 GT4 class:
Alpine A110 GT4
Aston Martin Vantage GT4
Audi R8 LMS GT4
BMW M4 GT3
Chevrolet Camaro GT4
Ginetta G55 GT4
KTM X-Bow GT4
Maserati MC GT4
McLaren 570S GT4
Mercedes AMG GT4
Porsche 718 Cayman GT4
1.2 Required DLCs
- GT4 Pack (for GT4 drivers)
- 2020 GT World Challenge (for GT3 drivers with corresponding car)
1.3 Balance of Performance
The standard 2020 ACC BoP will be used for the event.
1.4 Track Layout
The "Grand Prix" layout will be used for the event. The following map will be used for orientation and for matching the corner names (among others for the race committee).
2. Event preparation
The following defines any necessary steps and requirements prior to the race.
2.1 Registration of the drivers
The list of driver will be sent to the race director by PM. This list must be sent by 16.06.2021, 8pm at the latest.
2.1.1 Required data
When registering, the following data per driver must be submitted. The table can be used as a template and filled in:
|Driver:||First name:||Last name:||Name abbreviation (XXX):||Player/SteamID:|
2.1.2 Conditions of participation
Each driver must have driven at least one valid lap on the practice server by 16.06.2021, 8pm. Should a driver stand out due to a conspicuously slow lap time and thus represent a possible danger, the race director reserves the right to cancel the participation of the driver.
3. Guest starters
There will be 10 guest start slots available, in each class 5. The registration will start on the 29th may at 8pm in the linked thread. The teams will get no points for the championship.
The information for registration are available in the season announcement and are also mentioned in the thread of registration.
3.2 Driver amount
The number of drivers is a maximum of four and a minimum of one driver. The drivers of the guest start team can not compete on an other team in this event.
4. Event schedule
Event date: 19.06.2021
13:30 - Start of the race server (joining phase/training)
14:20 - Drivers briefing (All teams are in pits.)
14:45 - Qualification of the GT4 (20 minutes)
15:15 - Qualification of the GT3 (20 minutes)
16:00 - Start of the race
4.1 Specifications of the subsections
The exact procedures of the event are explained in the season announcement under point 4.
4.2 External conditions
4.2.1 Times and multipliers
The whole event will be simulated on a Saturday.
4.1.2 Track conditions and weather
|Probability of weather change||3|
5. Racing regulations
5.1 Stint times
The maximum stint duration is 65 minutes. This is controlled by the server.
5.2 Maximum driving time
Basically the maximum driving time is 150 minutes. If there are fewer registrations on a team than possible, the server will automatically compensate for any disadvantages.
5.2.1 Compensation for disadvantages (data without guarantee)
The disadvantage compensation is calculated from the following formula: (Maximum riding time) * (Maximum number of riders per team) / (Number of riders in the team)
|Amount of driver||Maximum driving time per driver|
|4 drivers||150 minutes|
|3 drivers||200 minutes|
|2 drivers||300 minutes|
5.3 Ingame chat
The ingame chat must be activated for each session. No messages may be sent during the qualification or race session. The right to write messages lies solely with the leading race stewards. Information from the race control and penalties will be sent via the ingame chat. In case of violations, the race control will first point them out. In case of repeated violations, the race control reserves the right to impose further sanctions.
5.4 Ingame penalties
Basically, no ingame penalties will be cleared by the race control. In special cases the race rontrol reserves the right to deviate from this rule.
5.5 Case of a Disconnect
In case of a disconnect, all drivers of the team have to leave the server. In addition, the race control has to be informed. The further procedure is to be discussed with them.
Once this has been done, the first listed driver must join the server. After that, the order as listed to the race director must be followed. This order can also be read in a spreadsheet and in the spotter guide. In case of non-compliance, problems with the entry list are to be expected, therefore the cooperation of all teams is required.
6. Race Control
A live race control will be available for the event. It will work on a protest basis. Cases must be sent to the race control members by PM according to the form below. The penalties will be announced via the ingame chat and in the forum. Penalties will be within the usual and known penalties of ACC, with no use made of normal time penalties.
6.1 Members of the Race Control
The race control consists of the Race Director and the other Race Commissioners.
6.1.1 Race Director
The race director serves as contact person for the teams before, during and after the race. In addition, penalties will be communicated by the race director via the ingame chat. The race director can be contacted before, during and after the race via PN in the forum and can be found on Teamspeak during the race.
The race director for the event is: Lukas Unger.
6.1.2 Race Commissioners
The race commissioners will be responsible for the evaluation of the protests.
6.1.3 Participants of the Race Control
The following are the participants of the race control listed until 24 hours before the start of the event. These are to be mention as recipients when sending a protest.
6.2 Protest form
Protests are to be filled out according to the following scheme:
|Protest author (name + start number)|
|Protest opponent (name + start number)|
|Approximate session rest time|
|Timestamp/Lap from replay|
|Curve/part of track|
Comments on the protests are not allowed.
6.3 Full-Course-Yellow (FCY)
Only in case of technical problems the race control reserves the right to call a FCY-phase. This serves to freeze the distances. As soon as this phase has been announced via the ingame chat, each vehicle must activate the pit limiter. The race will continue normally with the restricte speed via the FCY phase. The end will be announced through the ingame chat. This will first be done via a termination announcement message 15 seconds before the FCY phase ends. The second message ends the FCY phase. The race will continue normally.
6.4 Restarting the race session
If due to technical problems a server restart is necessary during the race session, the starting order will be defined by the positions at the termination of the race session. However, this is only the exception and will be tried to be avoided.
7. Sporting regulations
The basis of the sporting regulations are the VR regulations. The classification of the cases as minor, medium and major offences are reflected in the severity of the punishment.
7.1 Regulation of Lapping
The regulations of the DMSB will be followed:
The blue flag will be shown to a vehicle that is about to lap. When the flag is shown, the driver concerned must allow the vehicle behind to overtake at the earliest opportunity.
This means that the lapped vehicle must give way and create an opportunity for the lapping car to overtake. Communication via light signals or similar can be helpful if used correctly.
8. Training server
There are three training servers available for the race preparation, which can be found under the following names with corresponding conditions.
virtualracing.org#10_VRECS_Spa_Training_1 (Ideal conditions, Time: 2pm)
virtualracing.org#11_VRECS_Spa_Training_2 (event condition, Time: 4pm)
virtualracing.org#12_VRECS_Spa_Training_3 (event condition, Time: 8pm)
9. Social Media
Teams and riders with a social media presence are welcome to post under #VRECS or #VRECS_Monza, so that we would have common hashtags. No obligation, but you could potentially benefit from each other. We will also try to post content about the event on Virtual Racing's Instagram account.
The event will be broadcasted in german in its entirety, including the qualifying and race sessions. The livestream can be found on Virtual Racing's YouTube account.