Welcome to the 2026 VSCA State of the League. As in previous years, this document covers three things: key points from the current season, items we discussed for the upcoming season, and any new changes made and introduced.
Table of Contents
- Who We Are, and Why
- 2026 Season Lookback
- Sponsorship
- Finances
- VSCA Volunteer Positions
- SportsCar Championship
- New Series: Challenger Series
- License Penalty Points (LPP) Updates
- Sporting Code Updates
- Driver’s License Fee
- VSCA Privacy Policy Update
- 2026 Feedback
- Related Links
A lot of what’s in this year’s edition came out of internal discussion among Organizers and directly from feedback from Competitors, Team Managers, Race Stewards, and Race Directors alike.
As we head into the sixth year of VSCA, we are still looking for ways to improve VSCA as a whole, the website, and internal processes. We’ve also added valuable members to the VSCA team this year who have or will make a real difference for Organizers and Competitors, and we’re grateful for it.
Who We Are, and Why
Before we get into the details on the season and the future, we want to spend a few minutes on something more fundamental: what VSCA actually is, and why. Rules and how VSCA is run are downstream of the philosophy of VSCA. If the philosophy isn't clear, every ruling under it will look arbitrary to someone, no matter how consistent it actually is.
VSCA was built to run something as close as possible to a real IMSA-style Championship where different classes share the track the way they do in real life, decisions that lean on real-world precedent rather than sim-racing convention, and rules that sometimes feel stricter or less forgiving than you'd find elsewhere. That's not incidental. It's the reason VSCA exists, and it's why the stewarding is tougher than most leagues.
Holding drivers to that standard only means something if we hold ourselves to one too. After a stretch of races with a lot of full course yellows, IMSA's own Senior Vice President of Competition, Simon Hodgson, was candid that while the series would keep refining its own procedures and penalty structure, drivers "need to [also] improve." Both sides own a piece of it, and neither excuses the other. We feel the same way about VSCA. Later in this address we'll be direct about where we've fallen short this season and what we're changing because of it. But we also want to be honest that no amount of system-building on our end substitutes for drivers actually racing to the standard this league exists for. We can build the frameworks. We can't drive the cars.
And we want to name one pattern specifically, because it's been recurring this season: when a race has a lot of time under FCY or a lot of FCYs overall, the feedback afterward is almost always about the FCY criteria being too strict, or the procedures being too complicated. Rarely is it about what actually triggered the caution in the first place because the amount of FCYs and time spent under yellow is a downstream effect. The cause of FCYs, in the overwhelming majority of cases, is a driver putting a car into a wall or into someone else. As for the length of the FCYs themselves, our procedures aren't meaningfully more complex than real life's. Yet IMSA runs a full FCY sequence in about 18 minutes on average, while VSCA's average 30 minutes. While some of this comes down to the safety car speed, most of this gap isn't the procedure itself. It's wave-bys not taken at speed, cars not catching the pacing line, and cars not slowing enough for the class sort.
All of these small execution things add up over the course of a caution. Extra laps get completed before we can move to the next step, and that adds multiple unnecessary minutes. Streamlining the criteria and procedures is a fair conversation, and we're open to it; we've made updates there, which we'll discuss more below. But it doesn't address why the caution was needed to begin with or what's taking so long to complete the FCY, and that part is a driving problem, not a procedure problem.
If VSCA is the league you signed up for, we're going to hold ourselves to that standard, and we're going to hold you to it too. That's not meant as a threat, it's just the deal. If that's not the league you're looking for, that's completely fine. There are plenty of other leagues built around a different philosophy, and we'd rather you find one that's actually a good fit than stay here, get frustrated, and try to turn VSCA into something it's not. VSCA isn't trying to be everything to everyone.
2026 Season Lookback
The Good: Participation
Season-long participation was a genuine bright spot this year. Entry counts held up better across the full calendar than in prior seasons. Credit to the drivers who stuck with it through a full season, and to the teams who kept cars on track even when results weren't going their way.
The Bad: Driving Standards
The driving standards this season were below where they need to be. This isn't a one-sided problem, and fixing it isn't going to be either. It's going to take Organizers and drivers both doing better, and neither side gets to point at the other and call it solved.
The numbers speak for themselves: six races this season saw a FCY on Lap 1. Five of those were consecutive races opening under FCY before the end of lap 1, including races where Organizers had explicitly emphasized caution during drivers meeting less than ten minutes before green flag. One event alone produced 10 FCYs over a 6-hour race.
Individually, any one of these could be written off as a bad night. Six times in a season, five of them in a row, right after being told directly to dial it back, that's not random. That's an aggression problem.
We own our part in it. As part of this year's regulations overhaul, we removed the harsher penalty structure that had previously been in place specifically for incidents on the first 2 laps of a race start/restart. Since that structure came out, every single race except Petit Le Mans opened under a Lap 1 FCY. We don't think that's a coincidence, and it's a decision we're revisiting for next season.
That wasn't the only instability we introduced. The first half of this season saw more regulation changes than we're comfortable with, and we own that too. None of those changes were made lightly. They came directly out of Competitor feedback and constructive criticism. At the time we felt each one was necessary for the health of the league. But stacking that many changes into half a season is hard on everyone, and it's fair to ask whether some of those changes contributed to the driving standards problems we saw. We heard that feedback too, and it's part of why the second half of the season saw zero regulation changes. We wanted to give the rules a chance to settle and give drivers a stable target to race against. That stability is something we intend to carry into next season by default, not just as a one-time correction.
But we want to be honest about the rest of it. Between drivers meeting emphasis, harsher penalties, and clean racing incentives, we tried a number of things to get ahead of this pattern. But the driving standards on track, especially on lap 1, looked the same regardless. At some point the common denominator isn't the rulebook. It's the racing.
We can build every system in the world to encourage better decision-making, and we intend to keep doing that. But no penalty structure, no drivers meeting, and no stewarding framework can substitute for drivers actually racing like it's lap 1 of a multi-hour endurance event and not a 3-lap sprint. Regulations only provide the platform for clean racing; they can't force it. We, and plenty of your fellow Competitors, have asked repeatedly and directly for more restraint at the green flag and during the race, and largely didn't get it. That part is on the field, not the rulebook, and it needs to change regardless of what the regulations say next season.
This is the single biggest input into the stewarding and conduct changes we're rolling out for next year, which we'll get into in detail later in this address. But we didn't want those changes to land without first being honest about what drove them, on both sides.
Sponsorship
We're always working to secure sponsorship for VSCA. It helps offset our expenses, keeps the entry fee as low as possible, and lets us keep improving the experience for Competitors. If you know of someone, or a company, that might be interested in sponsoring VSCA, have them reach out via email to admin@vscaracing.com.
Finances
As in previous years, here's the full breakdown of where entry fees go this season, for transparency:
| Proceeds | Amount in USD |
|---|---|
| Entry Fee Payments | 7,333.60 |
| 2025 Ending Balance Carry-Over | 448.61 |
| Sponsorship Payment | 90.00 |
| Total Operating Balance | 7,872.21 |
| Entry Fee Refund* | (1,849.68) |
| Race Director Payment** | (1,365.00) |
| Race Steward Payment** | (675.00) |
| Website Hosting Payment*** | (674.67) |
| Adobe Photoshop | (252.55) |
| VSCA iRacing Account Funds Recharge for Session Hosting | (170.00) |
| Google Drive Storage | (133.49) |
| Graphics Design | (121.68) |
| Sponsorship Refund | (100.00) |
| iRacing Subscription | (98.18) |
| Postal Address Service | (71.57) |
| iRacing Content Purchase | (17.79) |
| 3rd Party Cloud-Based Object Storage for Replays | (1.26) |
| Test Transactions | (0.60) |
| Total Expenses | (5,531.47) |
| Remaining Balance | 2,340.74 |
| Amount Carried-Over to 2027 to Off-Set 2027 Expenses & Entry Fees | (2,340.74) |
| 2026 Season Ending Balance | 0.00 |
*Refunds are a combination of teams withdrawing before competing resulting in a full refund, incorrect payments.
**Time spent in Race Direction or Race Stewarding by Organizers was not paid.
***There have been increased costs in 2026 due to a server move before the end of our contract and ordering of a new SSL/TLS encryption certificate. This increase is only expected to be applicable for 2026 and not recurring in future years.
VSCA Volunteer Positions
During 2026, numerous people joined the VSCA team to help with various positions. This has been a great improvement internally and has allowed Organizers to focus on other areas that need attention. We're still actively looking for the following positions to help expand VSCA and make the series better for everyone:
- Series Director for the Challenger Series (LMP3 & GT4)
- Balance of Performance Data Specialist
- Partnership & Sponsorship Director
- Broadcast Commentators
- Race Director
- Race Steward
If you are interested, or know of anyone else who may be interested, head over to https://www.vscaracing.com/volunteer/ and send in an application.
SportsCar Championship
2027 Season Registration
Registration will open at three separate dates depending on specific criteria.
Returning Entries, Early Registration will open on November 14, 2026 at 1600 GMT. An Entry must meet the following requirements to be eligible:
- Must have competed in a minimum of 6 races during the 2026 season, or have competed in each remaining race in 2026 from the moment of its most recent promotion to the grid.
- Must compete in the same class as 2026 and use the same car number, unless the returning GTP champion elects to use #1, or the car number used was assigned for a specific manufacturer (i.e. 911 when running the Porsche GT3) and the Entry elects to change car manufacturer/model (i.e. changing to Ferrari).
- May change iRacing Team ID.
- May change car manufacturer/model.
Changing Entries, Early Registration will open on November 18, 2026 at 1600 GMT. An Entry must meet the following requirements to be eligible:
- Must have competed in a minimum of 6 races during the 2026 season, or must have competed in each remaining race in 2026 from the moment of its most recent promotion to the grid.
- Is not competing in the same class as 2026.
- May change car number.
- May change iRacing Team ID.
- May change car manufacturer/model.
New Entries, Public Registration will open on November 21, 2026 at 1600 GMT, for any Team or Entry that does not meet either set of requirements above. Registration also stays open at any point during the season once it's started.
After Public Registration opens, Car Numbers are no longer reserved to Early Registration-eligible entries except for the returning Series Champion from the GTP class if they choose to run car #1.
Classes & Cars
To align closer to real life IMSA, we have rebranded GT PRO and GT AM to GTD PRO and GTD, respectively. All the templates have been updated with the new rebranded class names and decals as well. Additionally, similar to 2026, GTD PRO and GTD will remain a single class within the sim, and Teams will have free car choice from all GT3 cars listed below.
The classes and cars that will be used for 2027 (shown below) are subject to change pending the release of any new cars in the 2027 Season 1 iRacing build. Additionally, any new car added to iRacing during the 2027 season that would be eligible to run in any of the classes below will be assessed by Organizers for mid-season addition:
-
GTP
- Acura ARX-06 GTP*
- Aston Martin Valkyrie AMR-LMH
- BMW M Hybrid V8
- Cadillac V-Series.R GTP
- Ferrari 499P
- Porsche 963 GTP
-
LMP2
- Dallara P217
-
GTD PRO
- Aston Martin Vantage GT3 EVO
- BMW M4 GT3
- Chevrolet Corvette Z06 GT3.R
- Ferrari 296 GT3
- Ford Mustang GT3
- Lamborghini Huracan GT3 EVO
- McLaren 720S GT3 EVO
- Mercedes-AMG GT3 2020
- Porsche 911 GT3 R (992)
-
GTD AM
- Aston Martin Vantage GT3 EVO
- BMW M4 GT3
- Chevrolet Corvette Z06 GT3.R
- Ferrari 296 GT3
- Ford Mustang GT3
- Lamborghini Huracan GT3 EVO
- McLaren 720S GT3 EVO
- Mercedes-AMG GT3 2020
- Porsche 911 GT3 R (992)
*The availability of the Acura ARX-06 GTP depends on if iRacing allows the increased car count per session of 17 total within league sessions.
Car Template Updates
Because of the updates needed for the GT class name change, we've taken the time to update all of the design templates for all cars. Here's what designers should expect:
All number panels are now square-edged rather than rounded, for a cleaner look. On some cars, the class-colored background has been increased in size slightly for a more proportional appearance. Teams can also choose between a white-bordered or black-bordered number panel, whichever suits their design better.
The front VSCA logo now includes a white-border or black-border option as well, and Teams can choose whichever they prefer. On the BMW GTP specifically, designers can place the VSCA logo either at iRacing's default "IMSA" branding location on the right side of the nose, or at the standard centered position.
The class logo on the rear of the GT cars has been reduced slightly in size, giving designs more freedom for movement and placement.
The window banners have been updated to match what's used in real life for the 2026 season. Where real cars run multiple banner variants, we've provided those options too. For example, BMW cars run both a solid black/white and a colored version of the BMW M Performance logo, and Teams can choose which to use. For any car with a paintable interior window banner, we've added the VSCA banner on the inside with a slight shadow effect, to replicate what drivers would actually see from the cockpit in real life.
All of these templates are planned to be ready by the time registration opens.
Qualifying Points
In the summer of 2026, Organizers took a closer look at IMSA's use of qualifying points toward the championship. These points are worth 10% of the total championship points based on finishing position (e.g. 350 points for 1st place in the race means 35 points for qualifying 1st in class). VSCA will implement this the same way starting in 2027.
Max Drivers Per Race
The maximum drivers allowed per entry has been reduced for all race lengths other than 6 hour races:
- 24 hours - 5 max (previously 6 max)
- 12 hours - 4 max (previously 5 max)
- 10 hours - 3 max (previously 4 max)
- 6 hours - 3 max (no change)
- 2 hours 40 minutes - 2 max (previously 3 max)
Practice Sessions
Official practice sessions will still be team sessions. However, there will be no restriction on the number of cars that teams can register. We ask two things: be courteous to other teams by not taking up 5-10 grid spots, and if you register with an iRacing team that isn't registered with VSCA, use a number that isn't already taken by an Entry on the grid.
Safety Cars Per Class & Race Starts
We'll be adopting the new safety-car-per-class feature, so long as it's supported in hosted sessions, for the cars we're using, and at the tracks we're racing. This means switching to split class starts rather than combined Prototype and combined GT starting groups.
For GTP, LMP2, and GTD PRO, we'll also be using iRacing's new Start Zones feature in place of a leader-controlled start. Instead of the leader deciding when to go, all cars will be shown the pace car's speed throughout the rolling pace lap and are expected to form up in an orderly grid and hold that pace. Once the pace car pulls into the pits, the displayed pace speed turns from grey to yellow. When the pace speed is yellow, race control pace speed control is now active. Any attempts to jump the start by accelerating early will receive a jumped start penalty. The green flag is a fixed moment race control calls, not something the leader triggers, and once it drops for a class, the race is green for everyone in that class.
GTD PRO and GTD are still considered a single class by iRacing, so GTD will keep a leader-controlled start, as was the case in 2026, rather than using Start Zones. GTD will create a gap to GTD PRO, ignore the iRacing green flag, and start from a designated start zone under the leader's control.
If the safety-car-per-class or Start Zones features aren't available after the 2027 Season 1 iRacing build releases, we'll fall back to the 2026 procedure but with a split class start for each class individually, rather than the two combined starting groups (Prototype and GT) used in 2026.
Full Course Yellow Procedures
Thanks to the iRaceControl (iRC) app and discussions with our Race Directors over the course of the season, we'll be switching from the iRacing safety car to a human-driven one. This gives Race Directors a lot more freedom to run FCYs effectively, and should help reduce some of the issues we saw in 2026, especially the issues seen at the final race of the season at Petit Le Mans. The procedures themselves will stay mostly the same as 2026, but execution will change slightly in a few areas. For instance, instead of slowing down to create a gap before the restart, the human-driven safety car can accelerate away on its own to build the gap, then hand pacing control to the first car in line, something you'll often see at restarts in real life.
The human driven safety car will utilize the BMW M2 Racing (G87) car in iRacing which will allow for it to run in its own class in sim and therefore be easily recognized by everyone on both the relative black box, and the new iRacing in-sim track maps.
Drivers need to be aware that the human-driven safety car will no longer be able to be driven through, so they'll need to make sure to avoid it when taking wave-bys.
If you are not racing in shorter races, or want to help out in the longer races, and want to help take an hour or two of being the dedicated safety car driver, let Organizers know and we will happily use your help!
We're also adding a new trigger for the Short FCY procedure. Currently, Short FCY applies when the previous green flag run was under 15 minutes, or when a caution comes out in the last 30 minutes of the race. For 2027, in addition to what was used in 2026, that same Short FCY procedure will also apply by default for any caution within the first 30 minutes of the race. If the Race Director determines the situation requires more than that, such as server issues or poor weather conditions, they'll move straight to the Extended FCY procedure rather than the Normal FCY procedure. This is meant to cut down on the long early-race cautions we saw too often in 2026.
Live Race Control & Appeals
For 2027, we are moving to live Race Control for every race. Incidents will be reviewed and penalties issued during the race itself, rather than after it's over. The exception is for incidents that occur late enough in the race that there isn't time left to review and act on them before the checkered flag; those will still be issued as post-race penalties. We're still actively looking for more stewards to help make this work; see the Volunteer Positions section above. All stewards will be compensated for their work.
Moving to live Race Control also means we're removing the ability to appeal. Appeals add delay to the review process, and both we and Competitors have said the same thing all year: fewer post-race penalties, not more. Live Race Control exists specifically to resolve incidents while the race is happening, so keeping appeals in place would work directly against the reason we're making this change.
To keep reviews moving quickly, incident reports must be submitted within 30 minutes of the incident occurring. That 30-minute window applies whether the race is under green flag or under FCY.
Reports themselves are also being simplified. Teams will no longer include a written description of what happened. Instead, a report will include only: the infraction being alleged (i.e. incident responsibility, unsafe rejoin, track limit violation, etc.), the cars involved, the timestamp of the incident, and the section of track. Quick for Teams to submit, quick for stewards to act on.
We're also changing the base penalty for non-procedural infractions. Racing incidents, No Further Action, and warnings will still be issued as stewards deem necessary, but where a penalty beyond a warning is warranted, the default will now be a 30-second stop and hold rather than a drive-through. This comes directly from feedback on our past experience running live Race Control: a drive-through often ended up meaningless whenever an FCY came out shortly after, since the time lost merging back into a caution-bunched field was effectively nothing. Procedural infractions, such as entering a closed pit lane under FCY or missing a wave-by, are unaffected by this change.
Self Serving Penalties
With the move to live race control, self-serving penalties will be removed in 2027.
Clean Racing Incentives
In the 2026 season, we implemented three new measures to promote clean racing, on top of the incident limit already carried over from 2025, which had been the only item to date that saw a noticeable impact. We increased clean racing bonus points, giving higher bonus points to teams with better CPI than those with worse CPI. To make things fairer, we also introduced removal of incident points for drivers deemed not responsible for an incident they were involved in. Finally, since a driver's incident points after all RC decisions were finalized represented points they were actually responsible for, any driver finishing a race with under 100 CPI received 2 License Penalty Points (LPPs). All of this was aimed at incentivizing cleaner racing.
Based on feedback from the survey, Discord discussions, and emails, we understand there are mixed feelings on all of these. Those in favor of these incentives have said: the 10x limit forces accountability that drivers often wouldn't otherwise take; the bonus points give teams that were taken out early a chance to recover something in the championship when they can no longer fight for position; and the LPP system works well, keeping a record of drivers over the course of a season.
Common feedback against these incentives includes: the 10x incident limit is too strict and makes people race more tensely, causing more incidents; there are too many reports coming in and penalties being issued for small things; the bonus points feel like a gimmick that takes away from the spirit of racing and devalues on-track finishing position; and in shorter sprint races especially, 100 CPI can be wiped out by a single incident and FCY. Another common piece of feedback we've received over the past year is that competitors feel the best way to improve racing is through live, in-race feedback knowing immediately, or with only a slight delay from incident review, what went wrong so they can adjust in the moment.
With that feedback in mind, we've made changes to the clean racing incentives for 2027. With live Race Control now reviewing incidents and issuing penalties in real time, we want stewards focused on consistency above all else. The fewer variables they need to weigh per incident, the more consistent the outcome. Here's what that means for each item listed above.
Incident point removal for incidents you're deemed not responsible for is being scrapped. While the iRC app can technically do this, it's extra work for stewards and can introduce inconsistency, so we think it's best removed. Since we're no longer removing those incident points, it wouldn't be fair to base clean racing bonus points or LPPs on iRacing incident totals that may or may not reflect actual fault. So the clean racing bonus points, and the 2 LPPs for finishing under 100 CPI, are also being removed.
The incident limit has been the one item we've tried since after Laguna Seca of the 2024 season that we, as Organizers, feel has had a noticeable impact on the quality of racing, including back when we ran live race control in VSCA's earlier years. Since adopting the iRC app in 2026, we've been doing a deep dive into everything it offers. So long as the person running the app is a session admin, it tracks incident points exactly as iRacing does: a 1x in iRacing shows as a 1x in iRC, a 4x shows as a 4x, and so on. Two of its features we'll be implementing are the ability to issue a penalty of our choosing once a car crosses a specific incident point threshold, and the ability to remove incident points for clean driving.
How will this be implemented, how does it work, and what should you expect as a competitor? Starting with implementation: we'll keep the 10x incident limit, but it will now trigger a drive-through penalty at 10x, with an additional drive-through penalty every 5x after that. On top of that, 1 incident point will be "removed" from an entry's total for every 15 minutes of racing in which that entry doesn't pick up a new incident.
Now, we know what you might be thinking: this looks stricter than what we have currently, and that's understandable. So let's walk through how it actually works. As mentioned, the app records incidents the same moment iRacing does. For example, say you pick up a 2x at the 0:10:00 mark. As soon as that incident point registers, a 15-minute countdown starts. If you race clean and don't pick up anything new over those 15 minutes, at 0:25:00 you'll get a private in-sim message telling you an incident has been dropped and what your new total is, and the 15-minute clock resets. Now say instead that at 0:33:00, 8 minutes after that last point was removed, you pick up a 4x. Your new total is 5x, and the 15-minute clock resets again.
Now let's say you hit that first incident limit mark of 10x and serve the drive-through penalty. You might be thinking you only have 5x of room until the next limit. That's correct in terms of points at that moment, but not in terms of total: the next threshold is actually at 15x total. If you hit the 10x mark and then run the next 2 hours 30 minutes completely incident-free (10x × 15 minutes = 150 minutes), over time your total will eventually reset to 0x as described above, and the next penalty threshold is back at 15x.
One thing all competitors need to be aware of: the incident count shown by iRacing itself will NOT be the number used to determine stop and holds under this system. Instead, teams will need to track their standing through their in-sim chat history. The private messages that reduce an entry's incident count will only be sent by a session admin, either a Race Director or Organizer, and barring technical issues, it will be the same person sending them for the entire race. To determine your current total, check the most recent private message from the RD or Organizer, then add any incidents you've picked up since then.
We understand this brings some limitations, but we feel the benefit of rewarding clean driving with incident removal outweighs the loss of being able to see your total incident count at a glance.
We ran an analysis on the impact of this using data from several 2026 races:
- At Watkins Glen, under the current hard 10x limit, 34 of the 51 participating cars had to serve at least one drive-through penalty with 8 cars serving two or more. Had this new system been in place, that number would have dropped from 34 to 9 hitting the 10x limit and 1 hitting the 15x limit without anyone even changing how they drove to avoid it.
- At Road America, 43 of 56 cars served at least one drive-through penalty; under this system, that would have dropped to 20 hitting the 10x limit and 10 hitting the 15x limit.
- At Indy, 14 of 55 entries served a drive-through; under this system, that would have dropped to 5 hitting the 10x limit and 1 hitting the 15x limit.
- At Road Atlanta, 53 of 54 entries served a drive-through with 45 serving two drive-throughs or more; under this system, that would have dropped to 31 hitting the 10x limit and 22 hitting the 15x limit.
Digging deeper into each race, the cars still getting penalized under the new system are the ones picking up multiple incidents in short windows and unable to race cleanly for a full stint. This naturally raises a fair question for drivers who feel that none of the incidents behind an incident limit penalty were really their fault, and we've thought about that carefully. We've addressed the broader version of this question elsewhere in this address, but it's worth revisiting here specifically: hitting the incident limit means multiple incidents stacked up over the course of a single race in a short period of time. One incident on its own isn't a pattern, it's a race and incidents happen during a race. Several incidents in a short period of time compounding to the point of hitting an incident limit threshold is. Even when RC reviews each one individually and doesn't rule you primarily at fault, accumulating that many incidents in a short period of time points to a common denominator, all while other drivers in the same race, in the same conditions, on the same track, aren't getting into the same number of incidents. It's a signal worth taking seriously on its own. The question isn't whether any single incident in that chain was your fault. It's why you kept ending up involved, again and again, when others around you didn't.
This is exactly the kind of accountability we mentioned earlier in this address. It's not about assigning blame for any one incident. It's about recognizing that a pattern like this, however it's made up of individual rulings, is yours to own and yours to change. No one else on track can do that for you.
Overall, we feel this gives some of the relief competitors have asked for. It creates an immediate in-race incentive to race clean, rewards drivers who stay within their means and keep the car on track, and means competitors no longer have to drive for hours with only 1 incident point to spare. At the same time, it still keeps a system in place for repeat offenders who can't get through a full stint without picking up multiple incidents.
One more change for 2027 is aimed directly at the pattern we saw far too often this season where FCYs were caused by incidents in the opening minutes of a race, or immediately following a restart. Six races this year had a Lap 1 incident trigger a FCY, and there were several additional cases of another FCY coming almost immediately off the back of a restart. Starts and restarts deserve more caution than they got, not less, and we're adjusting the penalty structure to reflect that.
Starting in 2027, any incident occurring within 5 minutes of a green flag, whether from a race start or a restart, where a driver is deemed at fault and the incident warrants more than a warning, will result in a 5-minute stop-and-hold. This applies in place of what penalty the incident would otherwise carry under normal circumstances.
We're also making a change to ensure penalties carry real weight beyond the incident itself. Any driver issued a Race Control penalty for non-proceedural penalties within the previous green flag period will not be eligible for the 3rd wave-by at the next FCY. This does not include incident limit penalties; an entry that hits the incident limit but isn't issued a separate penalty by Race Control for non-procedural penalties in that window remains eligible. As a reminder, the 3rd wave-by allows cars a lap down from their class leader to get back on the lead lap under caution, a deliberate departure from real life that we've kept in place because it gives drivers a reason to keep racing hard instead of quitting after an early incident. Losing that opportunity because of a recent penalty gives penalties a consequence that extends beyond the drive-through or stop-and-hold itself, without touching the underlying purpose of the wave-by rule.
Entry Fee
As mentioned previously, Organizers are actively working on securing sponsorship for the 2027 season, and finalizing the other pieces that factor into cost: volunteers helping with FCYs, live Race Control, and broadcast coverage. We're still actively looking for broadcast personnel to help make live broadcasts happen; see the Volunteer Positions section above, and as with stewards, broadcast personnel will be compensated for their work.
Because broadcast coverage is one of the larger cost factors and isn't yet locked in, the entry fee depends on whether we're able to secure it. If we're able to provide a broadcast for the season, the entry fee will be $155 per entry for the full season. If we're not, the entry fee will be $110 per entry for the full season.
New Series: Challenger Series
Starting in 2027, VSCA will finally be introducing the much-anticipated second series: the VSCA Challenger Series. This series will emulate the IMSA VP Racing SportsCar Challenge ("VPSCC") and will feature two classes, P3 and GSX, using the LMP3 and GT4 cars in iRacing.
The Challenger Series will be focused more on the “AM” driver caliber, similar to VPSCC, and therefore VSCA “P” classified drivers will not be allowed to participate. While VSCA “G” classified drivers will be allowed to participate, unlike in VPSCC, the participation of “G” drivers will be limited similar to LMP2 and GTD in the VSCA SportsCar Championship.
Regulations are still being finalized. Some of the key information so far is included below.
2027 Season Registration
Registration will open on December 19, 2026 at 1600 GMT. Teams will also be able to register at any point during the season after it has started.
Classes & Cars
The classes and cars that will be used for 2027 (shown below) are subject to change pending the release of any new cars in the 2027 Season 1 iRacing build. Additionally, any new car added to iRacing during the 2027 season that would be eligible to run in any of the classes below will be assessed by Organizers for mid-season addition:
-
P3
- Ligier JS P320
-
GSX
- Aston Martin Vantage GT4
- BMW M4 G82 GT4 Evo
- Ford Mustang GT4
- McLaren 570S GT4
- Mercedes-AMG GT4
- Porsche 718 Cayman GT4 Clubsport MR
Schedule
Race dates are subject to change pending the release of the iRacing Special Events Calendar. Race start times are to be confirmed and will be included within the Regulations once published.
| Date | Length | Track (Layout) | Classes |
|---|---|---|---|
| Sun, Feb. 28, 2027 | 2H | Sebring International Raceway (International) | P3 | GSX |
| Sun, Apr. 4, 2027 | 2H | Barber Motorsports Park | P3 | GSX |
| Sun, May 16, 2027 | 2H | Mid-Ohio Sports Car Course (Full Course) | P3 | GSX |
| Sun, June 20, 2027 | 3H | Watkins Glen (Boot) | P3 | GSX |
| Sun, July 25, 2027 | 2H | Road America (Full Course) | P3 | GSX |
| Sun, Sept. 12, 2027 | 3H | Michelin Raceway Road Atlanta (Full Course) | P3 | GSX |
| Sun, Sept. 26, 2027 | 1H 30M | Lime Rock Park (Grand Prix) | P3 | GSX |
Entry Fee
As with the SportsCar Championship, the Challenger Series entry fee depends on whether we're able to secure broadcast coverage for it. If we're able to provide a broadcast, the entry fee will be $60 per entry for the full season. If we're not, it will be $35 per entry for the full season.
License Penalty Points (LPP) Updates
For 2027, we're simplifying how LPPs are assessed for in-race infractions. Currently, incident responsibility carries three separate LPP tiers depending on the severity of damage to the other car(s) involved (2, 3, or 4 LPPs). We're removing that tiered structure entirely.
Going forward, LPPs will be assessed as follows:
- Procedural infractions, such as entering a closed pit lane or FCY wave-by issues, will carry no LPPs.
- Warnings will remain at 1 LPP, unchanged.
- All other infractions will be a flat 2 LPPs.
- Careless driving, if Race Stewards determine the infraction meets that standard, will be 5 LPPs.
This is a direct result of moving to live Race Control. With stewards reviewing and issuing penalties during the race itself rather than after it, we want the LPP structure to be as fast and simple to apply as possible, consistent with what we've said elsewhere in this address: the fewer variables stewards have to weigh per call, the more consistent the outcome.
Sporting Code Updates
As part of our usual offseason process, we're reviewing the Sporting Code for anything that needs updating, clarifying, or correcting. There are two changes we want to specifically touch on.
First, we're softening the minimum age requirement for Team Managers and Assistant Managers. Currently, the Sporting Code requires a Member to be 21 years of age or older at the time of registration of the Team. Going forward, a Member who will turn 21 at some point during the current VSCA season will be eligible to register as a Team Manager or Assistant Manager, even if they haven't yet turned 21 at the moment they register the Team.
Second, we're allowing a Member to be a Member and/or Team Manager of multiple Teams going forward. We're still working on building this functionality into the VSCA Paddock, which will take a few months, so we ask for your patience until it's released. We'll announce when it's live.
Driver’s License Fee
We recently surveyed the membership on a potential Driver License Fee, a flat per-season fee for Drivers that would have helped offset VSCA's costs and allowed us to lower the per-Entry entry fee. After reviewing the feedback, we've decided not to move forward with this. All VSCA costs will continue to be covered through the Entry Fee and any sponsorship we're able to secure.
VSCA Privacy Policy Update
We have updated the VSCA Privacy Policy on October 1, 2026. All Members are required to acknowledge this document by October 31, 23:59 GMT or their membership will be set to inactive until they request for reinstatement. Furthermore, iRacing have changed their Terms of Use for the iRacing API requiring all Members to give VSCA consent to use and process their iRacing API data.
Refer to the announcement covering both here.
2026 Feedback
We'd also like to touch on suggestions, comments, and ideas that came up this year through the survey, Discord discussions, and emails. We've summarized the different items below, italicized, and grouped them together where they cover similar topics.
- Why is this an IMSA based league as opposed to an endurance sports car championship?
- Why don’t we make it 100% like IMSA in terms of rules, schedule, track selection, etc.?
- Why are some things IMSA does ignored or implemented but other things IMSA does not do are brought in?
In 2021, shortly after another bad experience most can relate to in a special event, Benjamin Fischer wanted to create a calendar-long series built around some of the longer iRacing Special Events, to give his Team a home with a better atmosphere and experience than the official series. Benjamin had experience organizing and participating in leagues on NR2003, and brought the idea to Kyle Birnie, who had over 8 years of experience organizing leagues, to gauge whether it was possible and could succeed on iRacing. He recruited Kyle to join the Organizers Team.
Shortly after, VSCA was established. For a year-long calendar championship built around iRacing's Special Events, emulating real-life IMSA was the obvious choice. VSCA's core philosophy is to achieve the highest level of realism and immersion possible through the simulation, the league's rules and regulations, and its presentation.
We focus on IMSA not only because it reflected the main iRacing special event calendar at the time, but because we wanted to bring the real-world championship into the sim world for all of us to enjoy. That said, we can't make it 100% true to real life for a few reasons. For starters, we don't have access to every IMSA track. iRacing is currently missing Detroit, for example.
Some aspects of real life we've tried and found don't work, or wouldn't suit sim racing. For example, we used to allow P drivers in GTD, but they dominated the class and drove Teams out of the championship as a result. To keep competition high, we removed P drivers from the class. We instead placed more emphasis on B and S drivers, which is reflected in the current rule requiring 50% of total drive time from those classifications.
Supply and demand is another factor. In real life, particularly in the U.S., anyone chasing professional endurance racing really only has IMSA to go to. On iRacing, the number of races and leagues available far exceeds demand. As Organizers, we've realized a 100% authentic series won't always work in the sim world. When Teams fall out of championship contention, they'll often just stop showing up and find another league instead. In real life, they don't have that option.
We've also seen, as with special events, that when people wreck out of an endurance race early they tend to just quit, and we see that in VSCA too. That's why we use the 3rd wave-by. It's not realistic, but it incentivizes drivers to keep racing, since a FCY gives them a path back into the fight. We've regularly seen cars several laps down early on come back to finish top 5, on the podium, or even win. Race retirements in VSCA are noticeably lower than in special events as a result.
Overall, we look at as much of what IMSA does as possible and assess whether it would work in the sim world, whether it would work specifically for VSCA (as with P drivers in GTD), and whether it's actually implementable given human, sim, or other constraints (like not being able to run two separate GT classes in-sim with the full car pool available to both). We'll also look at historical IMSA, ALMS, and Grand-Am, when relevant, especially for track selection. That's why VSCA has raced at tracks like COTA, Miami, and Mexico City: none of these are current IMSA venues, but all have historical roots in IMSA, ALMS, or Grand-Am, and we feel they suit VSCA well.
When we weigh all of this, plus ongoing Discord discussions, emails, and survey responses, we try to land on the decision that best balances what's true to real life, what's actually possible in the sim world, what competitors want, and what Organizers want.
- One additional concern is organizational accountability. The regulations define detailed consequences when competitors make mistakes, but there is no equivalent process when an error by the Organizers, Race Control, stewarding system, or scoring system causes sporting harm.
- VSCA should establish an error-correction policy requiring the issue to be investigated, acknowledged, explained, and corrected where possible.
This is a fair ask. We believe Organizers should hold themselves accountable when things don't go according to plan. We feel we already do this publicly whenever it happens: we own up to the mistake, apologize, explain what happened, and make the changes needed to prevent it from happening again.
Examples of this happening just this season include:
- This State of the League and what has been mentioned above
- Our announcement on changes to the FCY made on March 14, 2026 where we explicitly stated: “We as Organizers are raising our hands and taking ownership of this, as this is on us, and apologize to everyone as you all deserve better.“
- Our statement on FCY15 at Daytona, where the incident was fully investigated, a detailed explanation was provided, a public statement was issued, and Organizers and RC acknowledged their responsibility.
We've also received emails throughout the year on other issues needing clarification, and in every instance where a mistake was made on our end, we've acknowledged it and accepted our role in it. Accountability is something Organizers strive to apply whenever it's warranted, and we've done that since the start of VSCA. We try to lead by example.
- Why is the Entry Fee so expensive when there aren’t any prizes or awards?
Running a league costs a lot, as you can see from the finances shown above, especially a league with over 75 hours of racing across 12 races in a season. Other leagues that run endurance races typically have 5-7 races, ranging from 2-6 hours each. At an average of 4 hours across 6 races, that's only 24 hours of racing for an entire season, the same as a single one of our races. Their broadcast and live race control costs are usually much lower as a result, which lets their entry fee be lower too.
It's also not uncommon for league owners to cover some league costs out of pocket. Organizers aren't in a position to do that, so those costs need to be spread across entrants instead. We continue to look for sponsors to help offset costs, and when we land one, it genuinely helps.
- Why isn’t drive time and/or driver combinations similar to real life IMSA rules, specifically in LMP2 and GTD?
We've found a lot of Teams run an S/B and G rating combination. Limiting LMP2 and GTD to just S and B drivers, to make them truly "AM" classes, would affect a lot of current Teams. LMP2 also has a requirement for a B driver in IMSA, which would hinder many Teams here as well. Because of that, we allow G drivers in, but limit their drive time so the emphasis stays on S and B drivers.
- Can we allow a small buffer on drive time like other leagues have to give some forgiveness and allow for more strategy?
This is technically possible, but it's not something we're interested in doing. A buffer with no consequences just becomes part of the actual drive time. For example, if the max drive time is 90 minutes with a 2-minute buffer and no additional consequences, the real limit is just 92 minutes.
With that said, we did revisit the drive time limits across all classes this year. We wanted to make sure they still strike the right balance: strategic depth, team racing versus one driver doing most of the work, staying reasonably true to real life, and keeping the emphasis in LMP2 and GTD that we discussed above. We found what we currently have still holds up, so we're leaving it unchanged.
- We need to be able to race freely and allow door to door contact.
- Rubbing is racing and should be allowed.
- There needs to be an understanding from the teams and the organizers that we are here to race not tip toe around.
It might feel like we're asking everyone to just drive around and not race but that's not the case. Sim racing carries no risk of physical injury and no financial cost for damage. Those two things naturally push people to overdrive the car beyond their actual skill level, which has become the "status quo" behind a lot of the wrecks and poor driving standards compared to real life.
We agree Teams and Organizers both need to feel like we're actually racing here, not tip-toeing around. But racing online also means dealing with netcode, whether we like it or not, and netcode alone means we can't race exactly the way real cars do. Small door-to-door contact and rubbing will happen when racing, but the sim doesn't always behave like real life, and we have to account for that if we want to clean up the racing.
We're all amateurs. None of us are Senna, Schumacher, Hamilton, or Verstappen, putting the car in the exact same spot lap after lap. That's a big part of why we've long defined and emphasized racing room as keeping roughly 0.5 car widths between you and the car next to you. It's not there to hold you back, it's there because we can't hit our marks with pro-level precision every single lap, and that extra space is what turns a lot of wrecks into no-incident racing.
- We shouldn’t be penalized for small things, even a mistake where someone gets pushed off the track should not result in a penalty unless it is a repeat offender.
- Repeat offenders should be penalized more severely each time.
Pushing someone off-track isn't clean racing. Teams and Organizers both need to understand the lengths some people will go to in sim racing to get a win and at times it can be worse than real-life racing in that regard. If we allow pushing people off track without consequence, we can guarantee it will get used intentionally to gain positions. That isn't clean racing, sporting racing, or racing with good sportsmanship.
Escalating penalties for repeat offenders is easy to describe on paper, every penalty gets more severe than the last. Actually tracking that accurately, and applying it consistently on every decision, is where it gets difficult in practice. That may be something worth building toward, but our collective focus right now, as Organizers, Teams, and Race Stewards, should be getting baseline consistency right first.
- We need better RC decisions or more consistency.
- There must be clearly defined regulations in place in order to properly make decisions in RC,
- RC must be able to properly analyze races and accidents so that there is no room for doubt regarding the decisions made.
- There need to be methods for correctly analyzing accidents including steering inputs and pedal inputs to better understand the whole situation.
We'll be telling the new Race Stewards in 2027 that we, and Competitors, don't want every small thing penalized. That said, we won't be instructing them on exactly what to penalize or not. What matters more to us as Organizers is consistency: penalties should be applied the same way across a race, and across multiple races, before we worry about how severe those penalties are. Stewarding that's harsher than most would like but consistent is better than stewarding that's lenient but inconsistent. Even the most consistent RC in the world, applying decisions with zero ambiguity, won't get everyone to agree with every call. Look at any "who's at fault" thread on the forums, social media, or YouTube, the only incidents where everyone tends to agree are the intentional ones. Expecting full agreement on anything else isn't realistic.
Competitors frequently ask us for more clearly defined, black-and-white regulations, so everyone knows exactly what is and isn't allowed. When we've put that in, it's often either ignored or criticized as "too much to think about while racing." The rules we ran in the first part of 2026 were, by most accounts, about as clearly defined as it gets, laid out plainly enough that if you took the regulations and applied them to an incident, most people should have reached the same conclusion. We're well aware of the issues that approach caused.
We've spent a lot of time reading the regulations of IMSA, WEC, F1, SCCA, and several club racing series. Across all of them, there's a common thread: extremely limited written guidance on what's expected on track, for RC to use in decision-making. In the 2026 IMSA Regulations, for example, articles 30.1.1 and 30.2 on pages 85-86 are the only guidance IMSA provides for what to expect on track and how RC should apply it. As far as we can tell, everything else is left to RC's judgment.
What you see in iRacing is all RC has to work with for analysis in terms of driver inputs. We can't see telemetry inputs while spectating, and even session admins don't have access to that. Expecting RC to have anything beyond visual steering inputs, speed, sound, and car positioning isn't realistic.
For 2027, we're also going to work directly with the Race Stewards to build a shared foundation for reviewing common, repeatable incident types. This means baseline reference points for the kinds of incidents that come up over and over, so similar incidents start from the same place instead of being evaluated from scratch every time.
As one illustrative example (not necessarily reflecting what the actual foundation will say), take a case where the car behind isn't alongside the car ahead by the turn-in point. One possible baseline would be to treat that situation, by default, as a late pass attempt or dive-bomb. That wouldn't replace judgment on the specifics of the incident: closing speed, class differences, racing line, and everything else stewards already weigh would still apply. But starting from an agreed baseline gives similar incidents a consistent reference point instead of each one being fully re-litigated independently.
Neither stewards making every call entirely on their own instincts, with no shared reference point, nor Organizers dictating exactly how every incident should be judged, is the answer. Both are part of why calls have felt inconsistent from race to race. Stewards are the ones in these reviews every week, and that experience should shape the foundation, not just get overridden by it. Organizers, meanwhile, have a vision we're working toward to make VSCA the best it can be. Working through this together, as a joint effort, gives us a real shot at getting the consistency 2026 was missing in a way that neither approach alone would.
- Just because IMSA has over 12-13 FCYs at Daytona, or runs 6, 7, 8 hours under FCY, doesn’t mean we should try and replicate that.
We're not trying to replicate the number of FCYs or the time spent under them. That's never been the goal. Before switching to incident-based FCYs in 2026, Organizers warned Teams that doing so would lead to more incidents overall. Competitors understandably tend to only follow their own race, which means they don't see the bigger picture of what's actually happening on track.
If you ever get the chance in a special event, an official series, another league with big grids, or even one of our own races, try switching to the "focus on crashes" camera for a couple of hours. It gives you a much broader view of what's really going on: the off-tracks, contacts, spins, and so on that most drivers never see.
A few years ago at the VSCA race at Laguna Seca, the field picked up over 100 incident points in the first 5 minutes of the race. This equates to more than 12 car contacts in 5 minutes across the field (8x per car contact, 4x per car involved). If you were running up front, you'd likely never have known any of that happened. Watching with "focus on crashes" on, though, you'd catch most of it. It's a real eye-opener for what's actually happening during a race.
- Less severe penalties should be added; for instance, if someone is at fault for an action but the actual harm done isn't that significant, a 5-second penalty might be more than enough.
- We need to have 5 or 10 second penalties as an option of a penalty because there are a good amount of incidents where a drive through is very tough and the warning is too light.
Unfortunately, iRacing's current implementation makes this impossible for us. It's not something we can offer unless it's a 100% post-race penalty. The moment you apply any "hold" penalty in iRacing, the sim automatically adds 25 seconds to the stop if any service is performed during it. That's why a stop-and-go, or even a stop-and-hold for as little as 1 second, becomes a 26-second stop-and-hold in practice if you don't clear all your pit work during the penalty.
- Any change being made to the rule that allows existing 6k+ iRating drivers to still race?
No, and we want to explain why. Sports Car iRating is earned across a huge range of cars, not just the ones VSCA run. A driver sitting at 6,000+ iRating may have built most of that rating in an MX-5, Spec Racer Ford, Radical, Renault Clio, or other cars which tells us very little about how they'll actually perform in a GT3 car or a prototype. iRating is only ever used to assign an initial classification when a driver has no VSCA history to go on. Once we have that history, what actually matters to us is how a driver performs on track in our cars, not what their iRating says going in.
That said, we have made the system measuring that performance more accurate this year. Updates to the Race Performance Report and the internal calculations included give us a clearer read on who's actually too fast or too slow for their current classification, and classifications will continue to be updated to reflect that throughout the season.
Here's the part we want every Team to take seriously: a Driver's classification isn't fixed for the season just because it was accurate on day one. If a driver signs up close to the top of a classification's iRating range, there's a real chance they get reclassified upward within just a few races, based on how they're actually performing against the field. That's not a system malfunction. It's the system doing exactly what it's supposed to do. If you're building a lineup around a driver near the ceiling of their classification, go in knowing that reclassification is a realistic possibility early in the season, and plan your lineup with that risk in mind rather than being caught off guard by it later.
- Considering increasing the iRating requirements. There's often a very clear difference in racecraft between current bronze drivers and others. I've suffered two accidents this season as a direct result. Increasing the minimum requirement to at least 2000, maybe even 2250 might help raise the bar.
- Naturally people are going to progress and I think the league should grow with those drivers so it allows teams to have more than a couple seasons and do officials.
We hear this, and we don't doubt the specific incidents behind it. But we want to push back gently on the idea that a higher iRating floor is the fix. As we mentioned above, iRating doesn't reliably predict racecraft. It is not uncommon to see higher-iRating drivers with worse on-track judgment than drivers sitting lower in the range. Raising the minimum from 1500 to 2000 or 2250 wouldn't filter out poor racecraft. It would just filter out some of the lower-iRating drivers who happen to race clean, while leaving in higher-iRating drivers who don't. That's why we've moved away from leaning on iRating as a gatekeeper and leaned further into performance-based reclassification instead, which is a more direct measure of what we actually care about.
VSCA has deliberately chosen not to grow with our fastest drivers. If we did, the iRating floor would climb year over year, and eventually VSCA would become a league where only a shrinking pool of very fast drivers could compete, the exact outcome some other leagues have drifted into over time. That's not what VSCA is for. We want this to stay a place where competitive racing doesn't require being an above average rated driver.
This doesn't mean drivers who improve have nowhere to go. It means VSCA, as a whole, isn't the vehicle for that progression. A driver who outgrows our iRating range or outgrows their classification has genuinely gotten better, and that's a good problem for them to have. Official iRacing series, or other leagues built around a higher iRating band, are the right next step for that kind of growth. We'd rather stay true to what VSCA is for the drivers who are here, than stretch the league upward and leave behind the exact audience it was built for.
- Why doesn’t VSCA use virtual safety cars or Code 60s instead of, or in combination with safety cars to allow more green flag racing.
Simply put, IMSA doesn’t in real life, and until they do, we won’t be bringing it into VSCA. This is one area where we don't want to deviate from the real thing.
- RC decisions should have text to inform people on how the decisions was made
We understand the appeal of documenting how decisions were made. When we've done this in the past, though, it often led to more confusion and more arguing over the reasoning rather than to learn from the incident. Because of that, we stopped documenting decisions this way. It also ties back to what we mentioned above. We want to keep the Steward's job as simple as possible, so they can focus on consistency and getting the call right, rather than administrative work like this.
- Sometimes we pick up incidents through no fault of our own
- We were hurt by incident through zero fault of our own
- You often get into accidents through no fault of your own and immediately rack up a lot of X's, which is bad.
- The current incident limit penalizes an entry if they are in incidents through no fault of their own.
- If you get spun off 3 times and it wasn't your fault, to have to then serve a DT for incidents that are not your fault.
We agree: you can be collected in someone else's spin, get hit from behind on a restart, or do everything right and still end up facing the wrong way because of someone else's mistake. That happens in real racing, and it happens here.
Here's where we push back on the constant “through no fault of our own” premise. If this happens to you once in a race, or once in a season, that's racing. If it happens to you three, four, five times over a season, the question stops being "was that specific incident my fault" and starts being "why do I keep ending up in these situations." Once is chance. Twice is coincidence. Three times is a pattern; and a pattern is not bad luck, it's information.
Getting collected isn't purely random. Where you position your car, how much space you leave in traffic, how you manage restarts, how predictable your inputs are to the cars around you, how you handle a car that's clearly faster or slower, how you read situations around you of cars overdriving or signaling aggression/unpredictability, all of that changes how often you end up in someone else's incident. You may not have caused the contact, but you may still have been able to put yourself somewhere you don’t get involved.
If every driver in the field believes every incident they're part of is someone else's fault, then by definition nobody in the field is at fault for anything and standards can never improve, because nobody has anything to fix. That's the exact dynamic we've heard back countless times over the years after race discussions and included in this survey, and it's the same dynamic behind a lot of the driving standards issues we've already talked about elsewhere in this address.
You can only control yourself. You can't control the driver next to you, but you can control your closing speed, your positioning, your patience on a restart, and whether you put yourself in a spot where someone else's mistake can catch you. If you end up in incidents, the productive question isn't "how do I get the penalty removed". It's "what do I need to change so I stop being there in the first place."
None of this means the incident and penalty structure is beyond scrutiny. That's a separate, ongoing conversation, which we have addressed above and we'll keep refining it where it makes sense to. But that conversation and this one shouldn't get merged. A better incident system might change how a no-fault collection gets determined. It won't change whether you were in position to be collected in the first place, and that part is squarely something drivers individually have control over and no one else.
If you've picked up multiple incidents this season, we'd genuinely rather you spend the offseason reviewing your own replays for what you could have done differently than spend it arguing the case for why none of them were your fault. One of those makes you a better, safer driver next season. The other doesn't.
- Tire limits would be a great addition to the series.
We've discussed bringing tire limits into the series, but ultimately couldn't land on a limit that would be broadly agreed upon and genuinely impactful across all races. Two other factors pushed us away from it as well: FCYs already heavily dictate how much green flag running happens in a race, and rain effectively cancels out any tire restriction the moment it shows up. It's also worth noting that real-life tire limits apply across an entire event weekend (practice, qualifying, and the race) not just the race session the way any limit in iRacing would be scoped to.
That distinction matters more than it might seem. In real life, a team that pushes too hard on tires in practice or qualifying has fewer sets available for the race, which directly shapes their race strategy. A race-session-only limit in sim doesn't eliminate that strategic element entirely, but it meaningfully reduces its impact, since practice and qualifying tire usage carries far less consequence into the race than it does in real life.
- Eliminate or at least greatly reduce the chance and intensity of the rain. My computer struggles even more with frame rates to the point that Sebring was almost undrivable.
- The torrential rain that has happened in several of the races. It is not fun, nor realistic. Homestead was a good example. I drove the last stint and literally had to get my teammate/spotter to tell me if I was on the track or not going through parts of the infield. Light rain is fine, but iRacing's heavy rain is just broken.
- Realism is great but fun should be the focus. Most of us have real lives and use this as an escape for fun. Tone down the chance of rain.
The only way we could realistically tone down or guarantee lighter rain, assuming we keep rain at all, is by switching to the timeline editor. That comes with a real trade-off, though. It would move us away from forecasted, genuinely random weather. The timeline editor tells you exactly when rain will happen and how much, down to the minute, which means Teams could plan their strategy around the weather in advance, rather than reacting to it as it unfolds mid-race.










