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

Don't iterate on collision geometries when undefined #2147

Merged

Conversation

stephane-caron
Copy link
Collaborator

Closes #2146

@stephane-caron
Copy link
Collaborator Author

stephane-caron commented Feb 1, 2024

I have tested this change locally and it loads my collision-less model 😃

(I looked into the unit test directory to see if we already had a fixture for visualizers where I could add a test for this, but we don't. Maybe hard to add to the CI?)

Copy link
Contributor

@jorisv jorisv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a changelog entry (under Fixed section)

@jorisv jorisv linked an issue Feb 2, 2024 that may be closed by this pull request
@jorisv jorisv merged commit d7c4b8c into stack-of-tasks:devel Feb 2, 2024
16 of 20 checks passed
@stephane-caron stephane-caron deleted the fix/meshcat_no_collision branch March 18, 2024 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Meshcat visualizer error when collision model is undefined
3 participants