Verify a generated package
Implementation snapshot · 2026-10-12 · Sources & update notes
Keep generation, measurement and qualification separate. Run tests against the exact new manifest and use a dedicated harness profile, not your normal play profile.
Choose the right check
Section titled “Choose the right check”| Operation | Scope | What it does not establish |
|---|---|---|
| Frame Quick | Four recordings: spring instrument, idle, flex and torsion | Damage or fracture qualification |
| Frame Full | Standard one-material schedule of 22 recordings, including repeats, damage/rate checks and captures | Acceptance without required rendered review |
| Vehicle pilot | Settle, supported drivetrain and articulation | Complete driving acceptance |
| Vehicle Verify package | Eight scenarios repeated three times; stops on failure | Real material/rupture qualification beyond the model |
| Attachment verification | Mount loading, commanded release and force-driven release | Full vehicle driving acceptance |
Quick is the frame UI default. The calibration CLI defaults to Full unless --verification quick is supplied.
First vehicle pilot
Section titled “First vehicle pilot”From the checkout root, set the four paths for your machine:
$calibrationPython = 'C:\BeamNGCad\venv\Scripts\python.exe'$manifest = 'C:\BeamNGCad\builds\vehicle\manifest.json'$game = 'D:\SteamLibrary\steamapps\common\BeamNG.drive'$profile = 'C:\BeamNGCad\harness'
& $calibrationPython tools/test-synthetic-vehicle.py $manifest --scenario settle supported articulation --game $game --profile $profileDespite its historical filename, this tool consumes the supplied exported-vehicle manifest. It records pilot-verification.json beside that manifest and stops on failure. Its built-in workstation paths are not portable, so pass your game and profile explicitly.
Inspect resting wheel orientation, articulation, mesh loading, joint motion and the recorded outcome. Diagnose failures and generate a new revision before acceptance.
Full driving acceptance
Section titled “Full driving acceptance”Use Build / test → Verify package. It runs settle, supported drivetrain, articulation, acceleration, braking, reverse, left turn and right turn three times.
The recorder checks complete finite telemetry, compiled mass and devices, motion errors and damage. Straight tests also measure uncommanded drift/yaw. Failed repeats withdraw driving qualification; a passed pilot cannot restore it.
Read evidence and recover
Section titled “Read evidence and recover”- Use the receipt’s generation, recording and qualification fields rather than interpreting a finished progress bar as a pass.
- Missing or corrupt captures fail evidence checks. A useful image still needs visual review.
- Keep failed diagnostics and the exact manifest when investigating.
- Resume only unchanged inputs and compatible implementation/game identity.
- Stop task cancels the owned worker; the harness closes its owned game session.
Passing runs may compact raw CSV and optional reports. Enable Save full build report before recording if later raw analysis is needed. Compaction preserves measured results and provenance, but cannot recreate discarded samples.
Continue with Package and install once the relevant status and limitations have been reviewed.