Twisted D.I.R.T. Archive

Tool documentation

Practical guides for preserved track-making and game-modification tools.

Digital Earthworks 0.8.2.23

Download: DigitalEarthworksv0.8.2.23_setup.zip
Game: MX vs ATV Reflex
Purpose: Visual terrain, map, object, water, ecosystem, activity, and spline editing.

Setup

  • Use a legacy Windows environment with DirectX 9 and the compatible NVIDIA PhysX runtime.
  • Confirm DE locates Reflex and lists stock models before editing a project.
  • Old versions stored the game path as ReflexRootPath under HKCU\Software\Strawberry\DigitalEarthworks\options. Prefer normal setup/options; registry editing is a last resort.

Reliable build order

  1. Import the terrain and required control/surface maps.
  2. Save a compiler .track definition.
  3. Export a simple Free Ride beta and test it.
  4. Add a grouped start structure/drop gate.
  5. Build and validate the activity spline.
  6. Export to an installed SX/National beta slot and test.
  7. Add objects, water, and ecosystems in small batches.
  8. Re-test after every batch and keep dated project copies.
  9. Distribute the four matching beta-slot files; DE's Release Track feature was never completed.

DE does not smooth imported displacement data. Create terrain at final height and use scale 1 when possible; large compensating scale magnifies noise.

Spline rules

  • Outside lines form reset boundaries.
  • The next pair inward constrain AI and establish finish width.
  • The center line is the respawn path.
  • Enclose the complete gate, including space behind it.
  • Put the start one node inside the spline, not at its extreme edge.
  • Use at least two nodes before a funnel joins the loop.
  • Merge disconnected sections/single square nodes.
  • Right-drag moves a node without creating another.
  • Use enough nodes to prevent a crash respawning a rider far ahead.

A late-loading crash can be caused by an invalid spline even when compilation succeeded. Rebuild the smallest suspect segment first.

Stability notes

  • If a large object set fails inconsistently, disable experimental multithreading.
  • Missing objects usually indicate the Reflex path, model libraries, PhysX, or plug-ins are incomplete.
  • A green terrain often means maps are in the wrong slots or have the wrong 24/32-bit format.
  • If an export appears unchanged, verify both the chosen slot and all four newly generated files.

Sources