The editor supports importing from and exporting to the ASAM OpenDRIVE (.xodr) format. This allows roads which were created by third party software to be opened (and edited) in BeamNG. Conversely, road networks generated in BeamNG can be viewed/edited in third-party OpenDRIVE-supporting software.
NOTE: The import/export functionality is only available in BeamNG.tech (not BeamNG.drive).
Import:
The Import button is found on the editor’s Main Tool Window.
This opens the Import Options Window, as shown in the following image.
The following options are available for imports:
The Offset To Terrain checkbox will, upon import, snap all roads to the existing terrain.
The Use Custom Offset checkbox and corresponding input box will, upon import, elevate all roads by the supplied vertical offset value. This is useful for files which are far below the terrain.
The Terraform Terrain To Import checkbox will, upon import, terraform the terrain to the road network. This is discussed further in the ‘Terraforming’ section of this documenation.
To import, push the button on the Import Options Window. This will open a file dialog, where an .xodr file can be selected.
The following image shows the difference between importing with no additional options set and importing with a custom offset and employing terrain terraforming.
Post-Import Fixing:
Once an import has been performed, the user may wish to adjust certain properties in the road. The usual editing options are available at this point. In particular, the user may wish to set all roads (or some roads) to use meshes rather than just decals on their own (which is the default). This would be required with bridges, for example.
Export:
The Export button is also found on the editor’s Main Tool Window.
Upon pushing the Export button, a file dialog will open, then when a filename is chosen, all roads currently in the editor will be exported as-is to .xodr format and saved to disk.
The following images show some examples of road networks which were created with the editor, then exported to third party viewing software.
Unsupported OpenDRIVE Features:
The following ASAM OpenDRIVE features are not currently supported by the editor.
A. elevation shape definitions.
B. elevation strips.
C. excluding lanes from lateral profile.
D. lane linkage info (predecessor/successor data).
E. lane borders.
F. road markings.
G. most junction types.
H. objects.
I. signals.
