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 the bug
This a situation, where i found two bugs, which correlate for some unknown reason. Please let me know, if i have to create seperate issues for these bugs with cross references. Although the one that crashes the simulation is more severe.
About the bugs: Depending on the order of the declared cars in OpenSCENARIO, when executing the file with Scenario-Runner, may crash or not.
To be exact:
On one hand, if i declare new_car first inside of <Entities> (see .xosc-file inside of [...]_broken1.zip), the simulation runs but with the side effect, where the properties of Ego and new_car are mixed up. This means, both cars have the color of new_car and when despawning new_car, it instead despawns Ego. I can't explain that behaviour.
On the other hand, if i declare new_car anywhere else but as the first car, the simulation tries to run as intended (which can be seen from the Ego vehicle color), but crashes instantly after spawning the cars Ego and Target. See the screenshots for the error message inside of the terminal.
The interesting part is, that the .xosc-files are identical, except for the declaration order of the entities.
To Reproduce
Execute both attached .xosc-files inside of the zip-folders, which can be found under "Additional context".
Expected behavior
Both simulations should be able to run independently, either without mixing up the properties of the car, or without crashing the simulation.
Screenshots
The terminal output of [...]_broken1.xosc (broken car properties):
The terminal output of [...]_broken2.xosc (simulation crashes):
Desktop (please complete the following information):
Describe the bug
This a situation, where i found two bugs, which correlate for some unknown reason. Please let me know, if i have to create seperate issues for these bugs with cross references. Although the one that crashes the simulation is more severe.
About the bugs: Depending on the order of the declared cars in OpenSCENARIO, when executing the file with Scenario-Runner, may crash or not.
To be exact:
On one hand, if i declare
new_car
first inside of<Entities>
(see .xosc-file inside of [...]_broken1.zip), the simulation runs but with the side effect, where the properties ofEgo
andnew_car
are mixed up. This means, both cars have the color ofnew_car
and when despawningnew_car
, it instead despawnsEgo
. I can't explain that behaviour.On the other hand, if i declare
new_car
anywhere else but as the first car, the simulation tries to run as intended (which can be seen from theEgo
vehicle color), but crashes instantly after spawning the carsEgo
andTarget
. See the screenshots for the error message inside of the terminal.The interesting part is, that the .xosc-files are identical, except for the declaration order of the entities.
To Reproduce
Execute both attached .xosc-files inside of the zip-folders, which can be found under "Additional context".
Expected behavior
Both simulations should be able to run independently, either without mixing up the properties of the car, or without crashing the simulation.
Screenshots
The terminal output of [...]_broken1.xosc (broken car properties):
The terminal output of [...]_broken2.xosc (simulation crashes):
Desktop (please complete the following information):
Additional context
File which doesn't crash the simulation: spawnDespawn_test_broken1.zip
Video of the execution: Screencast spawnDespawn_test_broken1.webm
File which crashes the simulation: spawnDespawn_test_broken2.zip
Video of the execution: Screencast spawnDespawn_test_broken2.webm
The text was updated successfully, but these errors were encountered: