-
Notifications
You must be signed in to change notification settings - Fork 0
Validation Checks
GrizzlyOne95 edited this page Jun 4, 2026
·
1 revision
The validation tools are meant to catch common legacy export mistakes before writing .geo, .vdf, or .sdf files. Validation is conservative: errors block likely broken exports, warnings flag risky or guide-derived issues, and info items document best practices or assumptions.
Scene Properties > Battlezone > Validation3D View > Battlezone > Selected GEO > Validation- Export dialogs also run validation and summarize blocking issues.
Use What Gets Checked in Blender for a compact in-app report of current validation coverage.
-
ERROR: likely invalid export or crash risk. -
WARNING: risky layout, missing helper, legacy convention mismatch, or likely gameplay issue. -
INFO: best practice, derived behavior, or non-blocking guidance.
Validation checks include:
- active GEO export object exists, is a mesh, and has vertices,
- legacy name length and LOD marker,
- GEO first-character best practice,
- normalized export name collisions,
- parent resolution inside the same exportable LOD set,
- multiple exportable model roots in one scene,
- LOD2 cockpit counterpart, parent, pivot, and orientation,
- LOD3 missing counterpart, high-detail mesh, and material usage,
- mesh face topology, including large n-gons,
- material texture name safety,
- GEO type and common hardpoint suffix combinations,
- armatures, skinning, shape keys, constraints, and unsupported legacy animation channels,
- VDF vehicle essentials such as Type 40 POV and vehicle COL helpers,
- collision helper names and mesh presence,
- animation preset slots,
- looping animation first/last pose mismatches,
- high animated-GEO counts,
- legacy frame-range guidance,
- turret/cockpit hierarchy conventions.
Vehicle collision helpers are important for normal vehicles, but producer, guntower, and building-like cases can be different. Validation avoids treating all VDF-style scenes as identical vehicles when structure/producer-style evidence is present.
If you are validating a true vehicle, use the Vehicle preset to keep vehicle-focused checks strict.
- Rename objects to valid 5-8 character legacy GEO names.
- Keep one exportable model root in the scene.
- Add or fix Type 40
povfor vehicle exports. - Parent hardpoints under the part that should move them.
- Match LOD2 cockpit pivots and parentage to LOD1 counterparts.
- Simplify or remove LOD3 for Redux-focused assets.
- Add animation elements before exporting animated legacy assets.