Best Practices


Development Best Practices

  • Avoid including too many sub-sections
    This will result in a more complex map than is necessary, which will cause issues further in the development process.

  • Do not use subsections for road markings
    This is considered an unnecessary expense, as it affects the whole portion of the road rather than the marking required for a specific road. In the case that the road marking matches the necessity to make a road section, it will be excluded.

  • Avoid creating more/less lanes in the middle of the road without following logical connections
    This can result in the car becoming detached from the road and potentially having no connections to a road.

  • Avoid using width tags unless absolutely necessary
    It is advisable to avoid using width tags unless they are absolutely necessary.

  • To achieve the desired curvature on certain road surfaces, you may need to use the curb tool.
    For more information, refer to the Console or Side Tab.

  • Experiment with good techniques to visually simulate a curb correctly when needed
    It is recommended that you experiment with good techniques, such as using a regular connection with an outer lane and width change, to visually simulate the curb correctly.

General Best Practices

  • Avoid “Ctrl + Z” and “Ctrl + Y”
    Avoid undoing/redoing (Ctrl + Z, Ctrl + Y) too many times. This will eventually crash the system and force you to close the editor and reopen all the files.

  • Constantly save changes
    Always remember to save your changes frequently to prevent losing your work and having to redo your progress from scratch.

  • Version control
    Ensure you create different versions of your files before making any complex changes. This practice helps prevent irreversible actions and provides a way to revert to previous versions if needed, effectively implementing version control.

Back to the top