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
{{ message }}
This repository has been archived by the owner on Feb 3, 2025. It is now read-only.
Say we have two identical models in the world, which are equipped with a camera sensor. Though the model names are different, the local camera sensor names will be identical (due to the models being the same internally). If we look at CameraSensor.cc:117, scene cameras are created using the local sensor name, rather than the scoped name. This means that whenever one of the models is deleted, and RemoveCamera is called in CameraSensor::173, it is going to delete the camera of the first sensor that was added, regardless of whether this is the camera corresponding to the sensor.
Original report (archived issue) by Elte Hupkes (Bitbucket: ElteHupkes).
Say we have two identical models in the world, which are equipped with a camera sensor. Though the model names are different, the local camera sensor names will be identical (due to the models being the same internally). If we look at CameraSensor.cc:117, scene cameras are created using the local sensor name, rather than the scoped name. This means that whenever one of the models is deleted, and
RemoveCamera
is called in CameraSensor::173, it is going to delete the camera of the first sensor that was added, regardless of whether this is the camera corresponding to the sensor.The camera should use the fully scoped name of the sensor instead to prevent this issue. See https://bitbucket.org/ElteHupkes/gazebo/commits/2a7c5d6cd9b3aef9015d67866030040503aa87d5 for suggested fix.
The text was updated successfully, but these errors were encountered: