trackBuilder/obstaclePlacer - Track Obstacle Placement

Reference for extensions/util/trackBuilder/obstaclePlacer.lua. Places static and procedural obstacles (rocks, ramps, rings, etc.) along track segments.

Exports

Internals

• Static obstacles use predefined .dae shapes: sharp1, sharp2, obstacle1, obstacle2 (rocks and sharp angles from GridMap).
• Procedural obstacles use proceduralPrimitives to generate: ring, cube, cylinder, cone, bump, ramp.
• Object pooling: Static obstacles are pooled per type via expandTruncateList. Excess objects are deleted; missing objects are created on demand.
• Positioning: getAdjustedPosRotWidth(o, piece) computes the world position/rotation by interpolating along the segment's points based on o.offset (0–1 normalized position along the piece).
• Anchoring: Each obstacle has an anchor value that offsets it laterally relative to the track width.
• All objects are rotated 90° via turn90 quaternion to match the track coordinate system.

How It Works

1. placeObstacles(track) iterates all pieces, collecting static obstacle placement data.
2. For each obstacle type, the object pool is resized and objects are positioned/scaled/rotated.
3. For each segment, placeProceduralObstacles handles procedural meshes:
   • Counts how many procedural obstacles the segment needs
   • Creates/destroys ProceduralMesh objects to match
   • Generates the mesh geometry (ring, cube, etc.) and sets position/rotation
4. The obstaclesChanged flag on segments prevents unnecessary rebuilds.

-- Place all obstacles on the track
obstaclePlacer.placeObstacles(track)

-- Obstacle data structure on a piece:
piece.obstacles = {
  {value = 'ring', variant = '', offset = 0.5, position = vec3(0,0,1),
   rotation = quat(0,0,0,1), scale = vec3(2,0.5,1), anchor = 0,
   material = 'track_editor_A_border'}
}

Additional Exports

• M.clearReferences - (undocumented)
• M.placeObstacles - (undocumented)
• M.placeProceduralObstacles - (undocumented)