TR-01
Purpose and Technical Philosophy
Technical review exists to keep EFVD cars fair, stable, broadcast-ready and consistent for judged tandem competition.
Same rule set
Cars must use the official season data and approved technical requirements.
Server-safe files
Cars should load cleanly, avoid oversized assets and not create event delays.
Broadcast quality
Cars should look professional and be identifiable on stream, replay and screenshots.
TR-02
Vehicle Eligibility
Cars must fit the EFVD competition category before visual, file or physics review continues.
| Rule | Requirement |
|---|---|
| Body type | Maximum 5 doors, post-1985 vehicle, RWD drivetrain. |
| Not allowed | No SUV, truck, body-on-frame pickup, monster truck, plane, boat, animal or joke vehicle. |
| Wheel style | No donkey-style wheels. Wheel size must look realistic for the car. |
TR-03
Visual Standards and Livery Rules
The car must look like it belongs in a serious drift competition and be suitable for public broadcast.
| Area | Requirement |
|---|---|
| Body kit and livery | Professional body kit and professional livery required. |
| Wheel fitment | Wheels must be realistic in size and must not clip through fenders or arches. |
| Wheel stickers | Contrasting color sticker required on wheels. |
| Lighting style | No automatic strobe lights or neon. |
| Stream-safe content | Offensive, explicit, hateful or unreadable liveries can be rejected. |
TR-04
Required Identification and Lighting
Driver identification, event branding and required light assets must be present for competition visibility.
| Item | Requirement |
|---|---|
| Brake light / G-Force light | Official Brake light/G-Force light must be installed on the windshield and rear window. |
| Windshield banner | Official windshield banner is required. |
| Driver cards | Driver cards are required on both sides. |
| Sponsor and event branding | EFVD staff will add required driver cards, banners, sponsors and event branding where applicable. |
| Official preparation kit | The public EFVD Car Tech Kit contains the current physics, required light asset and driver/inspector checklist. |
TR-05
Optimization and File Size Limits
Cars must meet one of the approved optimization profiles. Pick one profile and keep the car within all limits in that profile.
| Profile | Limits |
|---|---|
| Profile A | Up to 575,000 triangles, 300 objects, 175 materials. |
| Profile B | Up to 675,000 triangles, 250 objects, 150 materials. |
| Profile C | Up to 800,000 triangles, 200 objects, 125 materials. |
| KN5 / FBX size | KN5 max 80MB. FBX should be similar in size. |
| Skin folder | Skin folder max size 50MB. |
TR-06
Texture and Material Rules
Texture rules keep car packages clean, efficient and easier to review.
| Rule | Requirement |
|---|---|
| Texture format | All textures must be .dds only. PNG textures are not allowed. |
| Unused files | Remove unused textures, backups and duplicate assets before submission. |
| Material count | Material count must stay within the chosen optimization profile. |
| Preview | Preview preset in Content Manager must be GT5-like. |
TR-07
Physics and Performance Rules
Physics and performance must match the official season package. Drivers may not create a performance advantage through unapproved data.
| Area | Requirement |
|---|---|
| Official data | Use official season Engine, Gearbox, Tires, Aero and Suspension data. |
| Power graph | Power graph must be recalculated in Content Manager. |
| Engine sound | Engine sound must match the installed engine. |
Download the Official Car Tech Kit
The public kit contains the current Physics Suite 5.0 package, official Brake/G-Force light KN5 and driver-and-inspector checklist. This remains the official kit until EFVD intentionally publishes a replacement.
TR-08
Colliders, Aero and Contact Rules
Contact behavior and aero must stay realistic for drift competition.
| Rule | Requirement |
|---|---|
| Colliders | Colliders must be realistic and match the visible vehicle shape. |
| Parts placement | Suspension parts, exhaust, wings, bumpers and visible add-on parts must be placed realistically and match the car model. |
| Aero level | No GT-style or higher aerodynamics. |
| Bumper-mounted wings | Bumper-mounted wings must be hit-able. |
| Contact review | Unrealistic collision behavior can cause tech rejection or post-event review. |
TR-09
Folder Structure and Naming
Clean structure helps staff review cars quickly and reduces event-week problems.
| Item | Requirement |
|---|---|
| Folder and KN5 naming | Use EFVD_lastname_model for the car folder and EFVD_lastname_model.kn5 for the main KN5. |
| Content Manager UI name | The car name shown in Content Manager must visibly include EFVD. |
| SFX folder | Clean SFX folder required. Oversized .bank files may be rejected and staff may request cleanup. |
| Extension folder | The extension folder must only contain files required for the submitted car. Remove unused configs, old test files, backup files, unrelated scripts and assets not used by the approved car. |
| UI description | UI description must be up to date. |
| Showroom | Model must open cleanly in Showroom. |
| KN5 encryption | Unencrypted submissions are strongly recommended. Encrypted or unreadable models need inspector review; encryption alone is not an automatic rejection. |
TR-10
Submission, Encryption and Tech Review
Car approval depends on a reviewable submission and cooperation with technical staff.
-
01
Prepare the car
Clean files, confirm naming, verify physics and test the car in Content Manager.
-
02
Submit as requested
Follow the announced Discord process and provide the requested car files.
-
03
Unencrypted KN5 files recommended
Readable source files make model checks easier. An encrypted, damaged or unsupported KN5 needs additional review or a readable replacement if checks cannot be completed. Normal correction and revision-fee rules apply.
-
04
EFVD handles encryption
The EFVD team will encrypt the approved car and return the final encrypted package. EFVD can sign an NDA if needed and will not share or distribute the unencrypted model.
Cars, numbers, liveries, required decals and required event assets must be approved before the posted technical deadline. Late, changed or incomplete packages may be refused for that event. Car and livery change windows are announced on Discord if applicable.
TR-11
Quick Check, Car Inspection and Corrections
Submit your car link once. An automated check runs as part of submission, then an inspector reviews the car. A scan pass never approves a car for competition.
Licensed Drivers and Wild Cards each receive one free official inspection per event. Both follow the same submission, correction and revision-fee process if the car does not pass.
Quick Check
A clean automated check sends your submission to inspection. If warnings appear, review the fixes or choose Submit Anyway. An unreadable file offers Submit for Manual Check.
Ask an Inspector
Use Ask Inspector for car questions or early feedback. It opens a private question form; there is no separate pre-check application.
-
01
Registration confirmation
Final Tech submission opens after Event Ops confirms the driver's event registration.
-
02
Car inspection
One official inspection is included per event. The inspector reviews the exact submitted version. My EFVD shows your applicable payment or existing pass coverage.
-
03
Inspection decision
The inspector approves the submitted version, requests changes or rejects it. The decision identifies the required corrections and next step.
-
04
Revision, if required
After Changes Requested or Rejected, the inspector states whether the $5 CAD resubmission fee is required or waived. Paid resubmission fees are non-refundable by default, including before inspection work starts; exceptions require Event Ops approval. Follow the request in My EFVD before paying.
Help is optional. See the Financial Guide for fees and the Refund & Withdrawal Guide for inspection and revision terms.
TR-12
Approval, Car Updates and Post-Approval Review
Only the exact car version approved through Final Tech may be used in EFVD competition.
| Outcome | Meaning |
|---|---|
| Approved | The car can be used for the event if no later issue is found. |
| Changes Requested | The driver must fix the listed issues before approval. |
| Rejected | The car cannot be used unless staff allows a replacement or corrected version. |
| Post-Approval Review | Staff may check an approved car before, during or after competition. |
Get approval before changing the car
A driver who wants to change car files, physics, collider behavior, required assets or approved visuals must follow staff instructions. Approval of the original version does not cover the update. Another review may be required, and change windows are event-specific.
Staff may recheck an approved car
EFVD may initiate a compliance or spot check before, during or after an event. A public complaint is not required, and this review is not an automatic stage for every driver.
Results can be affected
Illegal or changed files discovered after competition may lead to correction requests, result review, prize ineligibility, event removal or license review. Results and payouts can remain provisional until required checks are complete.
TR-13
Policy Changes
Last updated: September 9, 2026. EFVD announces material changes through its official Discord before the affected registration opens.