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

[4.0.0] Per Model Settings: unexpected side effects on overlapping geo? #5854

Closed
hooyah opened this issue Jun 5, 2019 · 4 comments
Closed

Comments

@hooyah
Copy link

hooyah commented Jun 5, 2019

Application Version
Cura 4.0.0

Platform
Windows 10 x64

Printer
Ender3 (but I don't think that makes a difference)

Steps to Reproduce

  1. import a model that has two overlapping meshes in it. (cylinder and cube) single stl.
    Cura1

  2. slice -> the two meshes are "unioned" into one and the slices look as expected
    Cura2

  3. import another mesh that overlaps any part of the first mesh(es). I'd like to use it as a cutter.
    Cura3

  4. select the new mesh (sphere) and change the Per Model Settings to modify settings for overlap with other models. No settings have to be overridden at this point.

Actual Results
5) slice -> the internal overlaps of the first model (cylinder&cube) now create strange cavities and the two meshes will no longer print connected (see picture)
Cura5

Expected results
5B) what I actually wanted to do was to add settings for wall thickness, top/bottom thickness and infill density and set them all to 0 in order to create a cutout shaped like the sphere. And this indeed works, except for the aforementioned anomaly 5).

Is this not how this feature is intended to work? I read that it used to be called 'cutting mesh' which I find incredibly useful, eg.
to add optional cutouts to my prints.

Cura5B

Additional Information
Here's the Cura project (not actually a zip, just renamed)
CE3_cubecyl.3mf.zip

@nallath
Copy link
Member

nallath commented Jun 5, 2019

No. That's not how it's intended to work.

You're trying to do solid modeling, which should be handled in the domain of CAD (Computer-aided design) software. Cura is CAM (Computer-aided manufacturing) software, so it's about how a model should be constructed (not how the model looks).

Cura expects a model without any internal geometry. It has some algorithms to handle the situations where this fails, but this is always a losing battle (as you can see from it failing in your case).

The cutting mesh is used to indicate that the overlap of the cutting mesh and the model need to be printed with another extruder (and not what you're trying to do: not printed at all. That should be handled when designing the model).

@nallath nallath closed this as completed Jun 5, 2019
@hooyah
Copy link
Author

hooyah commented Jun 6, 2019

Well if that's it's sole intended use then there are too many buttons that seemingly do the same thing.
Maybe you could write some documentation that explains how these options are meant to be used?
Why are these modes available at all if they are only meant for dual extrusion purposes when I only have one extruder installed?

@nallath
Copy link
Member

nallath commented Jun 6, 2019

Well, the cutting can also be used to treat part of a model as a separate object. It's most common usage is to then print it with a different extruder, but there might be cases where you want to print both with the same extruder).

@Ghostkeeper
Copy link
Collaborator

A cutting mesh is meant to cut out a piece of your mesh to print the intersection with different settings. Could even be a different extruder. It could set everything to 0 and literally replace part of your mesh with void.

That changes nothing in that your normal mesh has internal geometry which makes it inherently ambiguous what the inside is of your model. In your case you got lucky that it resolved the inside according to what you think the inside is. But when the sphere got involved you were not so lucky any more. It could be that involving another mesh would solve it.

To illustrate why it's ambiguous, here's an illustration of what the computer is thinking when it sees your model:

ambiguous_internal_geometry svg

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

3 participants