Node Beam Export

Minimal exporter that dumps the current vehicle's node positions and beam connections to a JSON file.

Overview

util_nodeBeamExport exports the player vehicle's node/beam graph as a simple JSON file. Nodes include positions (converted to Z-up coordinate system) and optional names. Beams include their connected node IDs. Useful for external analysis or visualization tools.

Extension path: lua/ge/extensions/util/nodeBeamExport.lua

Exports (M)

Internals

Output Format

{
  "vehicle": {
    "id": 12345,
    "jbeam": "pickup",
    "name": "pickup"
  },
  "nodes": [
    { "id": 0, "name": "ref", "pos": [1.0, 0.5, -0.3] },
    { "id": 1, "pos": [1.2, 0.6, -0.2] }
  ],
  "beams": [
    { "id": 0, "n1": 0, "n2": 1 },
    { "id": 1, "n1": 1, "n2": 2 }
  ]
}

Coordinate Conversion

Node positions are converted from BeamNG's Y-up to Z-up:

• X = X
• Y = Z (game Z → export Y)
• Z = -Y (game Y negated → export Z)

Filename Suggestion

suggestFilename() scans the vehicle directory for existing export_*.nbexport.json files and returns the next sequential number. Files are placed in the vehicle's base directory.

Data Sources

• Vehicle object: getPlayerVehicle(0) - provides node positions via getNodePosition(id).
• Vehicle data: core_vehicle_manager.getVehicleData(id) - provides node metadata (names) and beam connections.

How It Works

1. Call exportFile() with an optional filename.
2. The current vehicle's nodes and beams are read.
3. Positions are coordinate-converted.
4. JSON is written with pretty-printing.

Lua Examples

-- Export to auto-suggested filename
extensions.util_nodeBeamExport.exportFile()

-- Export to specific file
extensions.util_nodeBeamExport.exportFile('vehicles/pickup/my_export.nbexport.json')

-- Get suggested filename
local fn = extensions.util_nodeBeamExport.suggestFilename()
print(fn) -- "vehicles/pickup/export_1.nbexport.json"

Additional Exports

• M.exportFile - (undocumented)
• M.suggestFilename - (undocumented)