Software & Tools Integration
MATLAB-Simulink Integration You can connect BeamNG.tech with the MathWorks products MATLAB and Simulink via our official MATLAB toolbox BeamNG.tech Support for MATLAB and Simulink . This toolbox comes with two components: Software and Tools Integration MATLAB-Simulink In This category is for BeamNG.tech integration with MATLAB and Simulink: co-simulation, controller/ADAS prototyping, sensor/telemetry streaming, and data analysis. Share workflows, bridges (BeamNGpy, TCP/UDP, MATLAB Engine, FMU/FMI), examples, and troubleshooting specific to MATLAB/Simulink. ScriptAI Editor The ScriptAI Editor is a GUI tool for authoring, executing, and refining complex multi-vehicle interactions in BeamNG.tech. Create precise, repeatable scenarios, from real-world trajectory replays to safety‑critical events like emergency stops, collisions, and tight lane changes, using time- or speed-based trajectories editable directly on the map with spline fitting, velocity matching, and behavior controls. FMI Integration BeamNG.tech implements the Functional Mock-up Interface (FMI) standard as a co-simulation option for vehicle coupling. Road Architect Road Architect is BeamNG.tech’s procedural road network editor. It lets you sculpt terrain, lay out and connect roads and junctions, and detail networks with built-in assets such as lamp posts, barriers, traffic lights, signs, and markings. The tool targets fast road-based content generation and lane-level connectivity, with an eye toward interoperability with third‑party tools compatible with ASAM OpenDRIVE. Co-Simulation Editor The Co-Simulation Editor allows the BeamNG.tech user to set up a tightly-coupled system between a BeamNG vehicle and third-party software (such as Mathworks Simulink). A GUI-based tool faciliates the creation of .csv files which are used as a contract to describe the parameters of the message-passing between the two sides of the coupling. The user can use the mouse to choose from a multitude of properties across the vehicle (kinematic properties, wheel data, vehicle electrics data, powertrain data, etc) - properties which are to be sent to the third party. Incoming properties (from the third party) are also selected in a similar way.
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| About the Software & Tools Integration category |
|
0 | 32 | 19 August 2024 |
| Questions about Road Architect |
|
2 | 132 | 12 August 2025 |
| I want to save the roads I created in Track Builder to a map |
|
3 | 111 | 22 May 2025 |
| About headless settings |
|
1 | 35 | 19 May 2025 |
| I would like to know how to place walls on a road created with MeshRoadEditor |
|
2 | 39 | 19 May 2025 |
| I can't place an AI road created with Decal Road Editor on a road created with Mesh Road Editor. |
|
2 | 71 | 30 April 2025 |
| [Release] Telemetry Collector for all to a client local vehicles in a Multiplayer session |
|
1 | 196 | 15 April 2025 |
| Export Map as OpenDrive File Not Working |
|
7 | 139 | 13 March 2025 |
| How to use co-simulation? |
|
1 | 73 | 18 November 2024 |
| Vehicle Dissappear in World Editor |
|
1 | 84 | 14 October 2024 |