High speed, long straights. An epic start for a season! General Information Date: Saturday 8th of October 2016 Server Name: RDGTC Round #1 - Monza Extra Gridslots Version Download: CLICK HERE Skin Pack: DOWNLOAD HERE Virtual Time of Day: 13:30 Track Grip: 98% Increasing Conditions: According to forecast Livetiming: click here Race Schedule 17:00 GMT (18:00 BST) | Free Practice | 90 minutes 18:30 GMT (19:30 BST) | Qualifying | 30 minutes 19:15 GMT (20:15 BST) | Race | 1H 30min - Standing Start All drivers must be present in the server at the start of qualifying. Technical Notes Track Length: 5.793 km Top speed: 280 km/h Turns: 11 in total. (7 right, 4 left) Track Map & Red Zone: The red zone for Round 1 applies from the start finish line to the exit of Turn 3 during the first lap of the race. Incidents that occur in this zone will be automatically looked at and may be punished more severely. Track Limits Article 6.1 of the 2016 RaceDepartment League Regulations states that all drivers must maintain at least two wheels within the white lines of the track at all times when under normal control of their car. Whilst article 6.1 applies to the entire race track, the stewards will pay particularly strong attention to the following areas of the track. The cutting penalties outlined in the Stewards Notice Board thread will be applied to drivers who take liberties with these areas too often. Ascari Pit Lane Exit Drivers must not exceed the white line on the exit of the pit lane which guides you safely back to the racing line, at any point during Qualifying or the Race. If caught doing so, you will be given an automatic 10 second time penalty added to your race time. Drivers are allowed to cross it during the practice session, provided it does not cause an incident. If it does cause an incident, then the affected driver is free to submit an incident report. Incident Reporting If you feel you've been unjustly disadvantaged by a fellow driver breaking our League Regulations, you are free to submit an incident report to the league director via Private Message, which will then be submitted to an independent steward panel from the staff group who will review it and issue a verdict. The report consists of a video + description of the incident. Reports will be accepted up to Monday 23:59 GMT post-race. Any later and they won't be considered. Teamspeak Teamspeak will be Mandatory for the league, as the race director may use whisper messages to communicate everything needed. Make sure to properly set up TS for whispers, using the same settings as the screenshot below. Speakers must be activated at all times during qualifying and race. When joining the server you can create your team's subchannel following the steps listed below. You are free to lock it with a password.