‹›
Vehicles

Debugging and Troubleshooting

Visualizes native wheel state and provides a systematic path for diagnosing creation, contact and handling problems.

JOLT_DEBUG_VEHICLES draws hard points, suspension, wheel axes, driven/passive state, contact markers and normals from current native snapshots.

Enable vehicle debug drawing#

GML
jolt_debug_enable(true);
jolt_debug_set(JOLT_DEBUG_VEHICLES, true);
jolt_debug_draw();

Vehicle does not build#

  • Verify the chassis is Dynamic, non-sensor and still valid.
  • Add at least two wheels and stay below the 32-wheel limit.
  • Mark at least one wheel driven or add a valid explicit differential.
  • Check every Boolean return and immediately inspect jolt_get_error().

Wheels do not contact ground#

  • Check chassis/ground collision layers and remember sensors are skipped.
  • Verify hard points, wheel radius and suspension travel in chassis-local coordinates.
  • Increase maximum_slope_angle only when the surface normal is intentionally drivable.
  • Try Sphere after a working Ray setup if sharp seams cause intermittent loss of contact.

Unstable or unrealistic handling#

  • Set chassis mass and center of mass before tuning springs.
  • Avoid extreme spring frequency, anti-roll stiffness and tyre multipliers.
  • Confirm the visual scale matches physical wheel radius and chassis dimensions.
  • Use get_forward_speed(), wheel compression and contact normals to distinguish traction from geometry problems.