-
Notifications
You must be signed in to change notification settings - Fork 268
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
Removing model with JointPositionController
plugin leads to 'entity does not exist' error messages.
#2165
Labels
bug
Something isn't working
Comments
I think if we solve #2217 this will no longer be an issue. |
Closing as duplicate of #2217. |
arjo129
added a commit
that referenced
this issue
Nov 7, 2023
This commit tries to address #2217. In particular if a user despawns an entity, the associated plugin gets removed. This should prevent issues like #2165. TBH I'm not sure if this is the right way forward as a system should technically be able to access any entity in a traditional ECS. I also recognize that there may be some performance impact. I will need to quantify this. Signed-off-by: Arjo Chakravarty <arjoc@intrinsic.ai>
8 tasks
jrutgeer
added a commit
to jrutgeer/gz-sim
that referenced
this issue
Nov 21, 2023
Signed-off-by: Johan Rutgeerts <johan.rutgeerts@lancewood.eu>
arjo129
added a commit
that referenced
this issue
Jul 9, 2024
This commit tries to address #2217. In particular if a user despawns an entity, the associated plugin gets removed. This should prevent issues like #2165. TBH I'm not sure if this is the right way forward as a system should technically be able to access any entity in a traditional ECS. I also recognize that there may be some performance impact. I will need to quantify this. Signed-off-by: Arjo Chakravarty <arjoc@intrinsic.ai>
arjo129
added a commit
that referenced
this issue
Jul 9, 2024
This commit tries to address #2217. In particular if a user despawns an entity, the associated plugin gets removed. This should prevent issues like #2165. TBH I'm not sure if this is the right way forward as a system should technically be able to access any entity in a traditional ECS. I also recognize that there may be some performance impact. I will need to quantify this. Signed-off-by: Arjo Chakravarty <arjoc@intrinsic.ai> Signed-off-by: Arjo Chakravarty <arjoc@google.com>
arjo129
added a commit
that referenced
this issue
Jul 17, 2024
n particular if a user despawns an entity, the associated plugin gets removed. This should prevent issues like #2165. TBH I'm not sure if this is the right way forward as a system should technically be able to access any entity in a traditional ECS. The PR has now been reworked and greatly simplified. All we do is stop all worker threads if an entity is removed and then recreate remaining threads.
arjo129
added a commit
that referenced
this issue
Jul 19, 2024
n particular if a user despawns an entity, the associated plugin gets removed. This should prevent issues like #2165. TBH I'm not sure if this is the right way forward as a system should technically be able to access any entity in a traditional ECS. The PR has now been reworked and greatly simplified. All we do is stop all worker threads if an entity is removed and then recreate remaining threads.
arjo129
added a commit
that referenced
this issue
Jul 22, 2024
n particular if a user despawns an entity, the associated plugin gets removed. This should prevent issues like #2165. TBH I'm not sure if this is the right way forward as a system should technically be able to access any entity in a traditional ECS. The PR has now been reworked and greatly simplified. All we do is stop all worker threads if an entity is removed and then recreate remaining threads.
arjo129
added a commit
that referenced
this issue
Jul 26, 2024
n particular if a user despawns an entity, the associated plugin gets removed. This should prevent issues like #2165. TBH I'm not sure if this is the right way forward as a system should technically be able to access any entity in a traditional ECS. The PR has now been reworked and greatly simplified. All we do is stop all worker threads if an entity is removed and then recreate remaining threads.
arjo129
added a commit
that referenced
this issue
Jul 26, 2024
n particular if a user despawns an entity, the associated plugin gets removed. This should prevent issues like #2165. TBH I'm not sure if this is the right way forward as a system should technically be able to access any entity in a traditional ECS. The PR has now been reworked and greatly simplified. All we do is stop all worker threads if an entity is removed and then recreate remaining threads. Signed-off-by: Arjo Chakravarty <arjo@openrobotics.org>
arjo129
added a commit
that referenced
this issue
Jul 26, 2024
n particular if a user despawns an entity, the associated plugin gets removed. This should prevent issues like #2165. TBH I'm not sure if this is the right way forward as a system should technically be able to access any entity in a traditional ECS. The PR has now been reworked and greatly simplified. All we do is stop all worker threads if an entity is removed and then recreate remaining threads. Signed-off-by: Arjo Chakravarty <arjo@openrobotics.org>
iche033
pushed a commit
that referenced
this issue
Aug 1, 2024
n particular if a user despawns an entity, the associated plugin gets removed. This should prevent issues like #2165. TBH I'm not sure if this is the right way forward as a system should technically be able to access any entity in a traditional ECS. The PR has now been reworked and greatly simplified. All we do is stop all worker threads if an entity is removed and then recreate remaining threads. Signed-off-by: Arjo Chakravarty <arjo@openrobotics.org>
iche033
pushed a commit
that referenced
this issue
Aug 2, 2024
n particular if a user despawns an entity, the associated plugin gets removed. This should prevent issues like #2165. TBH I'm not sure if this is the right way forward as a system should technically be able to access any entity in a traditional ECS. The PR has now been reworked and greatly simplified. All we do is stop all worker threads if an entity is removed and then recreate remaining threads. Signed-off-by: Arjo Chakravarty <arjo@openrobotics.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a model that uses the
JointPositionController
plugin is removed from the simulation through the UserCommands service, repeating error messages appear:See the attached example files:
Run
gz sim -r world.sdf
Spawn a model with the spawn script:
./spawn_boxes
Remove the boxes with the remove script:
./remove_boxes
--> The error messages start.
Edit the
boxes.sdf
file and remove theJointPositionController
plugin.Repeat the test.
--> No error messages after removal.
example.tar.gz
The text was updated successfully, but these errors were encountered: