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
[Err] [SDFFeatures.cc:843] The geometry element of collision [collision] couldn't be created
I don't think that this error is very constructive or helpful as I am trying to add a plugin from asv_wave_sim into PX4 and don't know what the issue is. My boat just fell through the waves and I was wondering if it had to do with this Error, but again I don't know what is causing this error.
I put this under feature request, as I don't think that it is a bug, but rather that the pipeline probably needs some improving, I could be wrong!
If anyone knows more, I would be super grateful for any information/help, thanks!
The text was updated successfully, but these errors were encountered:
That error msg is misleading and may not the actual cause for the boat falling through waves.
@iche033 it's definitely not the reason for the hydrodynamics plugin not working. There'll be something not quite configured right in the setup of the PX4 example. Will continue to track in: srmainwaring/asv_wave_sim#157.
The message doesn't appear to impact creating collision meshes, or having them collide, or be used for other purposes. I'm not exactly sure what is not working correctly from a practical sense (maybe writing out to SDF as part of a snapshopt of the world). In any case when the models and plugins are set up correctly the simulation does not appear to be impacted, so it's mainly a noisy warning that may be nice to be able to optionally suppress.
Desired behavior
[Err] [SDFFeatures.cc:843] The geometry element of collision [collision] couldn't be created
I don't think that this error is very constructive or helpful as I am trying to add a plugin from asv_wave_sim into PX4 and don't know what the issue is. My boat just fell through the waves and I was wondering if it had to do with this Error, but again I don't know what is causing this error.
I put this under feature request, as I don't think that it is a bug, but rather that the pipeline probably needs some improving, I could be wrong!
If anyone knows more, I would be super grateful for any information/help, thanks!
The text was updated successfully, but these errors were encountered: