-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gz-sim: detachable_joint.sdf #238
Comments
The state of the breadcrumb isn't getting monitored properly for this simulation. Only after I did a reset did the state of a breadcrumb appeared. Was this the expected behaviour (Attaching video). Can somebody also verify too. detachable_joint-2023-09-07_21.49.58.mp4 |
I got the exact same behavior. Could you take a look at it @ahcorde ? |
I think msgs are published to the state topic only if there is a change in state (attached -> detached or vice versa) as opposed to periodic updates. Regarding reset causing a msg to be published on reset, that probably revealed an issue. It seems like an extra detachable joint is created whenever reset is invoked. It could be a bug. |
Yep, just tried it out and works as you explained. Thanks.
After playing a little bit around with it, the behavior does seems weird. I'm not sure if I understood what you mean by "an extra detachable joint is created...". The msg I received is related to the joints that were part of the simulation before: |
I was looking at the terminal that's running
The entity number ( |
Oh, I'm getting something different when I click reset: Msg [NameManager::issueNewName] (Skeleton::Joint | vehicle_blue) The name [fixed] is a duplicate, so it has been renamed to [fixed(1)]
Msg [NameManager::issueNewName] (Skeleton::Joint | vehicle_blue) The name [fixed] is a duplicate, so it has been renamed to [fixed(2)] |
can you try this patch ? This should reattach the models again |
Closing since PR has been opened |
Setup
Links
Checks
You can find the code used to generate this test case here
The text was updated successfully, but these errors were encountered: