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

Collision of supports with objects #12723

Open
zburget opened this issue May 16, 2024 · 4 comments
Open

Collision of supports with objects #12723

zburget opened this issue May 16, 2024 · 4 comments

Comments

@zburget
Copy link

zburget commented May 16, 2024

When printing multiple objects that use organic supports and the objects are placed close together, the supports and adjacent objects collide. In the event of a collision, wouldn't it be possible to automatically "slide" the objects so that the collisions are resolved?

It is especially unpleasant when the objects on the mat are placed automatically and the slicer places them so close to each other that a collision occurs.

@u89djt
Copy link

u89djt commented May 16, 2024

If you combine all the objects (select them all and right click) the supports will be generated for the ensemble and not crash into each other. You'll often see a given tree span more than one of your objects. Save the project before you combine them for convenience. That's what I do anyway - I'm a fellow user.

@zburget
Copy link
Author

zburget commented May 17, 2024

And this is an even better solution - to have an option something like "Generate supports for all objects together".
This would be especially useful when printing multiple instances of an object.

@u89djt
Copy link

u89djt commented May 17, 2024

I'd be confident they're aware of this as a "nice to have". There's a software engineering burden; spawning new records of everything independent of the working set and deleting those when it's done without screwing everything up. Given that we can do this reliably ourselves it seems unlikely to outrank solving substantive errors or introducing new functionality that we can't do ourselves. It might not be complex per se, just asking for the usual kinds of trouble - have a look at the code base and see if you can spot a clean way of doing it.

@zburget
Copy link
Author

zburget commented May 17, 2024

I wrote only as a suggestion for improvement.

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

No branches or pull requests

2 participants