You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe our question or idea
MathWork's RoadRunner is a tool to create scenes (maps) and scenarios, which can be exported to Carla as Datasmith/OpenDrive maps and OpenScenario scenarios.
However, there are some issues with this.
The recommended export settings(*) from RoadRunner creates a TeleportAction for the spawn point. My experience is that this spawn point conflicts with the road/terrain. Increasing the value added to _spawn_point.location.z seems to fix it.
RoadRunner uses the state "runningState" instead of "startTransition". Adding "runningState" to the conditional triggers in the OpenScenario parser would fix this.
Expected behavior
Scenarios exported from MathWork's RoadRunner executing as expected without any issues.
Desktop (please complete the following information):
OS: Windows 10
CARLA Version 0.9.15
Python version 3.8
Version 0.9.15
(*) The recommended export settings include checking "Move non-instantaneous InitActions to Stories" under Advanced Settings in the OpenSCENARIO pane of the Export modal.
The text was updated successfully, but these errors were encountered:
Describe our question or idea
MathWork's RoadRunner is a tool to create scenes (maps) and scenarios, which can be exported to Carla as Datasmith/OpenDrive maps and OpenScenario scenarios.
However, there are some issues with this.
Expected behavior
Scenarios exported from MathWork's RoadRunner executing as expected without any issues.
Desktop (please complete the following information):
(*) The recommended export settings include checking "Move non-instantaneous InitActions to Stories" under Advanced Settings in the OpenSCENARIO pane of the Export modal.
The text was updated successfully, but these errors were encountered: