VSCC S3 | News & Announcements
- Thread starter Nox
- Start date
- Status
Just a reminder that the skins deadline is the 26th of April. If you have your skin ready, you can submit it to @Davy Vandevenne early.
Due to the large number of sign ups, we've made some changes to how the league will run meaning all drivers will be able to participate. The League Information Thread has been updated, and I will repeat the changed information here in this thread for convenience. Please review the changes, it is your responsibility as a driver (don't come complaining later because you didn't know something 
) Any questions or clarifications, please ask me, thanks.
--
Points Structure
Position - Points
1st - 55
2nd - 52
3rd - 50
4th - 48
5th - 46
6th - 45
7th - 44
8th - 43
9th - 42
10th - 41
11th - 40
12th - 39
13th - 38
14th - 37
15th - 36
16th - 35
17th - 34
18th - 33
19th - 32
20th - 31
21st - 30
22nd - 29
23rd - 28
24th - 27
25th - 26
26th - 25
27th - 24
28th - 23
29th - 22
30th - 21
31st - 20
32nd - 19
33rd - 18
34th - 17
35th - 16
36th - 15
37th - 14
38th - 13
39th - 12
40th - 11
41st - 10
42nd - 9
43rd - 8
44th - 7
45th - 6
46th - 5
47th - 4
48th - 3
49th - 2
50th - 1
You must complete 75% of the race to be eligible for points.
How does it work?
There will be two servers running consecutively (with one overall championship table). The pre-season test will split the drivers into two servers based on fastest lap time. The fastest 28 drivers will be placed in server 1 for the first race, and everyone else in server 2.
The pressure is on. On Saturday 2nd May 2015 the pre-season qualification event will take place, and will be broadcast.
) Any questions or clarifications, please ask me, thanks.--
Points Structure
Position - Points
1st - 55
2nd - 52
3rd - 50
4th - 48
5th - 46
6th - 45
7th - 44
8th - 43
9th - 42
10th - 41
11th - 40
12th - 39
13th - 38
14th - 37
15th - 36
16th - 35
17th - 34
18th - 33
19th - 32
20th - 31
21st - 30
22nd - 29
23rd - 28
24th - 27
25th - 26
26th - 25
27th - 24
28th - 23
29th - 22
30th - 21
31st - 20
32nd - 19
33rd - 18
34th - 17
35th - 16
36th - 15
37th - 14
38th - 13
39th - 12
40th - 11
41st - 10
42nd - 9
43rd - 8
44th - 7
45th - 6
46th - 5
47th - 4
48th - 3
49th - 2
50th - 1
You must complete 75% of the race to be eligible for points.
How does it work?
There will be two servers running consecutively (with one overall championship table). The pre-season test will split the drivers into two servers based on fastest lap time. The fastest 28 drivers will be placed in server 1 for the first race, and everyone else in server 2.
- At the end of each race, the bottom 5 finishers in Server 1 get relegated to Server 2 for the next round.
- At the end of each race, the top 5 finishers in Server 2 get promoted to Server 1 for the next round.
- Points and results are server independent (i.e. if you finish 1st in Server 2, the most points you can get are for 29th overall, even if there are DNFs in Server 1).
- Only server 1 will be broadcast
- At the end of the league, your worst result will be removed, meaning even if you have a bad race, you can still compete.
The pressure is on. On Saturday 2nd May 2015 the pre-season qualification event will take place, and will be broadcast.
- The event starts at 19:00 GMT and will last one hour.
- You may show up at any time during the event to put in your laps.
- All drivers have a maximum of 5 laps - one out lap, 3 hot laps, and one in lap. Keep an eye on your lap count! Leaving the garage counts as a lap even if you escape and go back in.
- Text chat during this event is forbidden. This will be strictly enforced. Any text chat of any sort during the event will be penalised by having your fastest lap removed, and your second fastest time being used instead.
- At the end of the event, drivers will be assigned a server for race 1 based on their fastest lap time.
- DQs will be counted. If you DQ, you'll be placed at the bottom of the list.
Last edited:
Important Announcement
The skins deadline is tomorrow. There are a LOT of skins that haven't been submitted, so please get on it!
It takes time and work to compile a skin pack, and to avoid unnecessary work all members must be a Premium Member by the skins deadline or they will not be participating in the league. Staff aren't going to do work of adding skins for drivers who won't run in the league later anyway. Go premium by 00:00 GMT tomorrow, or lose your league slot! Thanks.
Thank you.
The skins deadline is tomorrow. There are a LOT of skins that haven't been submitted, so please get on it!
It takes time and work to compile a skin pack, and to avoid unnecessary work all members must be a Premium Member by the skins deadline or they will not be participating in the league. Staff aren't going to do work of adding skins for drivers who won't run in the league later anyway. Go premium by 00:00 GMT tomorrow, or lose your league slot! Thanks.
Thank you.
Skinpack Available!
Thanks to Davy Vandevenne, we now have the skin pack ready! Well done everyone who made a skin, they all look stunning. They're going to look amazing on our live broadcasts.
Download Here
Thanks to Davy Vandevenne, we now have the skin pack ready! Well done everyone who made a skin, they all look stunning. They're going to look amazing on our live broadcasts.
Download Here
Pre-Qualification Results
RESULTS ARE IN!
Click Here
Notes
RESULTS ARE IN!
Click Here
Notes
- The times on the table are the fastest allowed times; you may have done a faster lap, but it was removed for exceeding track limits.
- The following drivers had at least one lap time removed: Craig Patteson, Ryan Seltzer, Risto Kappet, Razvan Ariciuc, Allan Groth, Raphael Zanardi, Corrado Conti, Antonio Merino, Fabio Assuncao, Vitor Sousa.
- Screenshots are available to confirm where track limits were broken, and can be requested by the penalised driver, or by their team manager. PM Nox if you are interested.
- The following drivers did not appear for the pre-qualification event, and are placed last: Mark Breslin, Gabriel Sterr, Jeff Lasecki, Rolf Just. All drivers are penalised with 2 points for not reporting in the absence thread at least 24 hours before the event.
Round 1 Race Control
Incident, Server 2, Red Zone.
Drivers involved: @Andrew Harper @Genci Estebanez
Review: This video was presented to several members of RD's race staff.
Decision: It was agreed that Andrew Harper's spin back onto the track was unfortunate, however more effort could have been made to avoid it, and the driver put himself into a risky position in a designated red zone where drivers are instructed to be extra careful. Therefore Andrew Harper is penalised with a 10 point deduction for colliding with Genci Estebanez. (Note a red zone incident will be penalised with double the points as an identical incident elsewhere.)
Track Limits 1
Driver involved: @Neto Nascimento
Review: The driver was reported to race control. Race control viewed 10 consecutive laps of the driver and observed whether the driver exceeded track limits.
Decision: The driver went wide 6 times in 10 laps at the final turn. This is considered a high enough frequency that the driver is in breach of track limit rules. Driver is penalised with a 5 point deduction, and is warned that future breaches will result in higher point deductions.
Track Limits 2
Driver involved: @Guus (Verver)
Review: The driver was reported to race control. Race control viewed 10 consecutive laps of the driver and observed whether the driver exceeded track limits.
Decision: In the 10 laps, the driver was observed within the track limits at all times. The report is dismissed and the driver will not be penalised.
Track Limits 3
Driver involved: @Miguel Lopes
Review: The driver was reported to race control. Race control viewed 10 consecutive laps of the driver and observed whether the driver exceeded track limits.
Decision: The driver went wide 7 times in 10 laps at the final turn, with a blatant disregard of the rules. No attempt was made to keep the car within the track limits; and is considered to have gone wide with a high enough frequency to be in breach of track limit rules. Driver is penalised with a 5 point deduction, and is warned that future breaches will result in higher point deductions.
Please note track limit penalties are not given because a driver goes wide once or twice; it has to be a repeated number of times. The league tables have been updated.
Incident, Server 2, Red Zone.
Drivers involved: @Andrew Harper @Genci Estebanez
Review: This video was presented to several members of RD's race staff.
Track Limits 1
Driver involved: @Neto Nascimento
Review: The driver was reported to race control. Race control viewed 10 consecutive laps of the driver and observed whether the driver exceeded track limits.
Decision: The driver went wide 6 times in 10 laps at the final turn. This is considered a high enough frequency that the driver is in breach of track limit rules. Driver is penalised with a 5 point deduction, and is warned that future breaches will result in higher point deductions.
Track Limits 2
Driver involved: @Guus (Verver)
Review: The driver was reported to race control. Race control viewed 10 consecutive laps of the driver and observed whether the driver exceeded track limits.
Decision: In the 10 laps, the driver was observed within the track limits at all times. The report is dismissed and the driver will not be penalised.
Track Limits 3
Driver involved: @Miguel Lopes
Review: The driver was reported to race control. Race control viewed 10 consecutive laps of the driver and observed whether the driver exceeded track limits.
Decision: The driver went wide 7 times in 10 laps at the final turn, with a blatant disregard of the rules. No attempt was made to keep the car within the track limits; and is considered to have gone wide with a high enough frequency to be in breach of track limit rules. Driver is penalised with a 5 point deduction, and is warned that future breaches will result in higher point deductions.
Please note track limit penalties are not given because a driver goes wide once or twice; it has to be a repeated number of times. The league tables have been updated.
Last edited:
Round 2 Race Control
Incident 1, Server 2
Drivers involved:@Rolf Just @Sharjeel
Review: This video was presented to several members of RD's race staff.
Decision: This is a racing incident and there will be no penalties. Sharjeel makes a poor decision to move across the track into the path of another driver when not up to racing speed and is warned to be more careful in future. At the same time Rolf had sufficient time to react and avoid a collision but doesn't.
Track Limits 1
Driver involved: @Risto Kappet
Review: The driver was reported to race control for exceeding track limits in qualifying. Race control viewed the drivers qualifying session and observed whether the driver exceeded track limits.
Decision: The driver went wide a number of times in the final corner gaining a speed advantage when entering, or on, a hot lap, including on the fastest and second fastest lap. Driver is penalised with a 5 point deduction. This is the second time the driver has been penalised for exceeding track limits in the VSCC and is warned that future breaches will result in higher point deductions.
Track Limits 2
Driver involved: @Sergio Junior
Review: The driver was reported to race control for exceeding track limits in qualifying and the race. Race control viewed the drivers qualifying session and 10 consecutive laps in the race and observed whether the driver exceeded track limits.
Decision: The driver did not exceed track limits on his fastest laps, which avoids a penalty, however is warned to be more careful in future, it was borderline. During the 10 laps observed of the race, track limits were only exceeded twice, and is judged to have been racing with track limits in mind. Driver will not be penalised and the report is dismissed.
Absences/Late Reports
The following drivers are penalised with a 2 point deduction for not reporting absent at least 24 hours before the event: @vitor sousa @Fab #28 (Fabrizio Telasio) @Sk3ptik0n (Corrado Conti)
Incident 1, Server 2
Drivers involved:@Rolf Just @Sharjeel
Review: This video was presented to several members of RD's race staff.
Track Limits 1
Driver involved: @Risto Kappet
Review: The driver was reported to race control for exceeding track limits in qualifying. Race control viewed the drivers qualifying session and observed whether the driver exceeded track limits.
Decision: The driver went wide a number of times in the final corner gaining a speed advantage when entering, or on, a hot lap, including on the fastest and second fastest lap. Driver is penalised with a 5 point deduction. This is the second time the driver has been penalised for exceeding track limits in the VSCC and is warned that future breaches will result in higher point deductions.
Track Limits 2
Driver involved: @Sergio Junior
Review: The driver was reported to race control for exceeding track limits in qualifying and the race. Race control viewed the drivers qualifying session and 10 consecutive laps in the race and observed whether the driver exceeded track limits.
Decision: The driver did not exceed track limits on his fastest laps, which avoids a penalty, however is warned to be more careful in future, it was borderline. During the 10 laps observed of the race, track limits were only exceeded twice, and is judged to have been racing with track limits in mind. Driver will not be penalised and the report is dismissed.
Absences/Late Reports
The following drivers are penalised with a 2 point deduction for not reporting absent at least 24 hours before the event: @vitor sousa @Fab #28 (Fabrizio Telasio) @Sk3ptik0n (Corrado Conti)
Round 3 Race Control
Incident 1, Server 1
Drivers involved: @Craig Patteson vs Many others
Review: This video was presented to several members of RD's race staff.
Decision: This is an incident that had it been anywhere else during the race may have been written off as a racing incident. However, being a red zone drivers are expected to be extra careful not to put themselves into a position where such incidents can occur. The red zone will be strictly enforced as a deterrent for lap 1 incidents and overly aggressive racing. The staff considered a) red zone rules b) whether Craig could have made more effort not to go onto the grass and c) the resulting carnage and damage to other drivers. The driver will be penalised with a ten point deduction.
Official Warnings
While no points penalty applies this time, drivers @Flammenjc @Miguel Lopes and @Sergio Junior all received official warnings for overly aggressive racing. Defending and overtaking should not include such regular and aggressive contact, changing of line in the braking zone, and closing the door on another driver when they have significant overlap. Future breaches of this kind will result in points penalties being applied with no further warning.
The deadline for reporting incidents has passed, no further incidents from round 3 will be reviewed.
Incident 1, Server 1
Drivers involved: @Craig Patteson vs Many others
Review: This video was presented to several members of RD's race staff.
Official Warnings
While no points penalty applies this time, drivers @Flammenjc @Miguel Lopes and @Sergio Junior all received official warnings for overly aggressive racing. Defending and overtaking should not include such regular and aggressive contact, changing of line in the braking zone, and closing the door on another driver when they have significant overlap. Future breaches of this kind will result in points penalties being applied with no further warning.
The deadline for reporting incidents has passed, no further incidents from round 3 will be reviewed.
Round 4 Race Control
Incident 1, Server 1
Drivers involved: @Jon Hicken vs Many others
Review: This video was presented to several members of RD's race staff.
Decision: Being a red zone drivers are expected to be extra careful not to put themselves into a position where such incidents can occur. The red zone will be strictly enforced as a deterrent for lap 1 incidents and overly aggressive racing. Jon Hicken will be penalised with a ten point deduction.
Incident 2, Server 1
Driver involved: @Flammenjc (Jake Cooper)
Review: Driver accused others of cheating, swore and 'verbally' abused another driver, and left the server just before the event.
Decision:
Incident 1, Server 1
Drivers involved: @Jon Hicken vs Many others
Review: This video was presented to several members of RD's race staff.
Incident 2, Server 1
Driver involved: @Flammenjc (Jake Cooper)
Review: Driver accused others of cheating, swore and 'verbally' abused another driver, and left the server just before the event.
Decision:
- Automatic 2 point penalty for being absent without report
- Automatic 5 point penalty for finger pointing [as laid out in League Info thread]
- 10 point penalty for swearing at another driver in the lobby. [17 points total]
- Driver is removed/resigned from league
Round 5 Race Control
Incident 1, Server 1
Driver involved: @Ariciuc Razvan
Review: This video was presented to several members of RD's race staff.
Decision: This is clear cut; the driver runs into the back of a competitor and disadvantages a number of drivers. Driver is penalised with a 10 point deduction for causing an incident in the red zone.
Absences
The following drivers are deducted 2 points for not reporting absent at least 24 hours in advance: @Nox @Jason @Warren Schembri @Craig Patteson, @Sven-Arne Andersson . Additionally @Mark Breslin, @bömii @Fab #28 are also deducted 2 points and informed that their failure to report absent gives them lower priority when signing up for leagues in the future.
The deadline for reporting incidents has passed, no further incidents from round 5 will be reviewed.
Incident 1, Server 1
Driver involved: @Ariciuc Razvan
Review: This video was presented to several members of RD's race staff.
Absences
The following drivers are deducted 2 points for not reporting absent at least 24 hours in advance: @Nox @Jason @Warren Schembri @Craig Patteson, @Sven-Arne Andersson . Additionally @Mark Breslin, @bömii @Fab #28 are also deducted 2 points and informed that their failure to report absent gives them lower priority when signing up for leagues in the future.
The deadline for reporting incidents has passed, no further incidents from round 5 will be reviewed.
Last edited:
- Status
