# ROS2 cpp bridge does not stop after scenario exit

**URL:** <https://forum.beamng.tech/t/ros2-cpp-bridge-does-not-stop-after-scenario-exit/488>\
**Category:** ROS bridges\
**Created:** [16 November 2026 15:01 UTC](https://forum.beamng.tech/t/ros2-cpp-bridge-does-not-stop-after-scenario-exit/488 "2026-11-16T15:01:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gundondu0](https://forum.beamng.tech/user_avatar/forum.beamng.tech/gundondu0/32/198_2.png) [@gundondu0](https://forum.beamng.tech/u/gundondu0)\
**Post date:** [16 November 2026 15:01 UTC](https://forum.beamng.tech/t/ros2-cpp-bridge-does-not-stop-after-scenario-exit/488/1 "2026-11-16T15:01:16Z")

</div>

Hello,

This is meant as a bug report and a recommendation. Launching the cpp bridge and exiting the scenario without stopping it causes the ROS2 topics to stay alive. The only way to get rid of the topics is to close and relaunch the application.

Because the topic names (i.e. /bng#####/sensor\_name) are assigned on random the script that I use to find those topics looks at the three first letters. Thus it can not differentiate between old topics and the new ones if I forget to stop the bridge. It would be great to be able to choose the topic IDs in the config file, instead of it getting assigned on random.

Hope this helps!
