Question Internal Geometry appearing on top and bottom layers

[Taco_Bob 1]

Hello, I'm creating checker pieces with embedded magnets using the pause at height extension.  The internal cavity's geometry is affecting how the bottom layer and the first layer above the cavity is printed such that the layer above the cavity will print on nothing in the gap above the magnet.  See picts.  

 

Model x-ray:

 

Bottom Layer:

 

Second layer:

 

First layer above cavity, might drop into it:

 

In Cura 4.2.1, I somehow changed settings so that this would not happen, but I can't find that setting. 

 

Same model, 1st layer above cavity in 4.2.1:

 

I'd just use 4.2.1 but the pause at height feature doesn't work for me, 5.1.0 is better.  I see that some of the settings in 5.1.0 are labeled differently.  

 

Does anyone know how to get the top/bottom layers to not be affected by internal geometry?  As is, the first layer above the cavity won't be connected to the cavity wall.

 

Thanks for any help!

Checker 25.obj

[MariMakes 203]

Hey @Taco_Bob,

 

I recognize this issue. We have a known bug with Union Overlapping Volumes in Cura 5.0 and 5.1
But if I try with Cura 4.13 I get this printjob without any changes:


Can you try Cura 4.13.1 for me? 
You can get it here:
https://github.com/Ultimaker/Cura/releases
 

[gr5 2,230]

In 4.X you might have to make sure that remove empty first layers is unchecked.  In 5.X they hid that setting so you are screwed.  I assume because the hollow for the magnet is too close to the bottom of the print.

[GregValiant 1,351]

Hello @Taco_Bob

Try setting your "Top Surface Skin Layers" to 0 or 1.  (I'm using 5.2beta.)

This is Top Surface Skin Layers at "2".

 

This is with it set to "1".

 

 

Edited October 12, 2022 by GregValiant

[Taco_Bob 1]

Thank you all.  Now I know what to call it thanks to MariMakes.  As it turns out, the version of Cura on my Raspberry pie has the pause at height features of 5.1 and doesn't have the union overlapping problem.  It's 4.(something) so that works, might be 4.13 actually.  It actually slices faster and better than the versions on my Win10 machine where I'm having these issues, go figure.  Its probably faster because Microsoft is so clodgey.

 

Thanks!