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. |
| Approved applicants | Physics files and required assets such as light strips will be made available on Discord to approved applicants. |
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. |
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 |
|---|---|
| Naming format | Folder, KN5 and UI naming format: ef26_lastname_model. |
| 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. Crystal Encryptor is not allowed for review. |
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 only if requested
Only provide an unencrypted model if EFVD staff specifically requests it for tech review.
-
04
Staff returns final package
If an unencrypted model is required, EFVD can sign an NDA if needed and will not share or distribute it. Staff will return the approved encrypted version.
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
Pre-Check, Failed Tech and Resubmissions
Pre-check and final tech are separate processes. Pre-check is optional and helps catch obvious issues early. Final tech is the official approval review for event use.
Optional pre-check
A pre-check can be requested before final submission. Staff reviews obvious problems and gives correction notes to help the car reach final tech ready.
Final tech submission
Final tech is the official inspection for event use. If a final submission fails, additional review or resubmission may be required before the car can be approved.
-
01
Pre-check request
Driver requests optional pre-check through the announced Discord process.
-
02
Pre-check notes
Staff flags visible issues, file structure problems, missing assets or obvious technical concerns.
-
03
Final submission
Driver submits the corrected package for official tech review.
-
04
Pass or resubmit
Staff approves the car, requests corrections or requires another review after failed tech.
Fees may apply to optional pre-checks, failed-tech resubmissions or staff repair services. Current fee details, payment method and enforcement are detailed on Discord.
TR-12
Car Approval, Rejection and Post-Event Inspection
Only approved car versions may be used in EFVD competition.
| Outcome | Meaning |
|---|---|
| Approved | The car can be used for the event if no later issue is found. |
| Corrections required | Driver must fix listed issues before approval. |
| Rejected | The car cannot be used unless staff allows a replacement or corrected version. |
| Post-event inspection | Staff may inspect a car after competition if concerns are raised. |
Resubmission may be required
Changing car files, physics, collider behavior, required assets or approved visuals after tech can require new review. Allowed change windows are event-specific and announced on Discord when applicable.
Staff may inspect
EFVD may perform random spot checks before, during or after an event without needing a public complaint.
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
EFVD may modify this guide when needed to support sustainability, fairness and the continued growth of the championship.