Skip to content
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

Simulation World resetCommand argument #1370

Closed
2 tasks done
costashatz opened this issue Jul 12, 2019 · 3 comments · Fixed by #1372
Closed
2 tasks done

Simulation World resetCommand argument #1370

costashatz opened this issue Jul 12, 2019 · 3 comments · Fixed by #1372
Labels
type: bug Indicates an unexpected problem or unintended behavior

Comments

@costashatz
Copy link
Contributor

costashatz commented Jul 12, 2019

Bug Report

  • I checked the documentation and the forum but found no answer.
  • I checked to make sure that this issue has not already been filed.

Environment

  • DART version: master
  • OS name and version name(or number): Ubuntu 18.04
  • Compiler name and version number: GCC 7.4.0

Expected/Weird Behavior

I am using a World to simulate a world using DART. When I do a step() I pass the resetCommand = false. Usually everything works fine until I used a soft body. In that case the behavior that I am getting when resetting or disable the rest of the commands in the step is different. In short, I get normal behavior when resetCommand = true and weird behavior otherwise.

Steps to Reproduce

  1. Create a world with a soft body (a soft cube for example) and a rigid floor
  2. Put the soft body at a height (e.g., 0.5)
  3. Run the simulation with resetCommand = true and with resetCommand = false

Why I am getting this behavior? Any ideas?

Thanks a lot!

@costashatz costashatz added the type: bug Indicates an unexpected problem or unintended behavior label Jul 12, 2019
@jslee02
Copy link
Member

jslee02 commented Jul 13, 2019

Thank you for the bug report. I could reproduce the issue from soft_bodies example with resetCommand = false option. Let me take a look if it can be quickly resolved.

@jslee02
Copy link
Member

jslee02 commented Jul 13, 2019

This should be fixed by #1372! Let me know if it doesn't work for you.

@costashatz
Copy link
Contributor Author

This should be fixed by #1372! Let me know if it doesn't work for you.

Seems to be working! Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Indicates an unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants