RE: PrusaSlicer produces empty layers. Any way around it?
I was not aware about the fact that a valid STL (or at least a STL that was imported into PrusaSlicer without warnings) could produce invalid submodels, when manipulating it in the slicer. But this is obviously something that I have to keep in mind.
As I am using the Windows version, this is quite easy by using the netfabb feature. The OP is using Mac OSX, so unfortunately this is not as comfortable.
RE: PrusaSlicer produces empty layers. Any way around it?
Usually PS picks up most errors but I have seen several examples of models that PS declared to be okay but netfabb found errors with. I don’t know what makes those cases special. I’d be inclined to accept that as a valid bug complaint with Prusaslicer.
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
RE: PrusaSlicer produces empty layers. Any way around it?
The original plant pot is actually a pretty good model compared to a lot of them. Blenders 3d print tool only found 2 intersecting faces. One of these is on the bottom and the second is next to it on the inside of the bottom pentagonal hole. Depending on how you rotate it to slice the cut may or may not pass through those intersecting faces.
The other factor here is this is actually a very simple model. with their being 2 way symmetry that changes angle between top and bottom its possible that the cut could intersect one of the vertices too when you select the middle. While I'm not sure how slicer handles the cut internally I do know that cutting through a single vertices with a boolean is one of the most common causes of faulty models in other software. Its why you usually extend a boolean cut beyond a surface. Cutting a line between 2 vertices its quite easy to add in an extra vertice on either side of the 2 parts, I think if you get unlucky enough to cut through the vertices itself though that it has a greater chance of messing up.
I'm more concerned with why there appears to be different results on different operating systems. I know they use different libraries but unit testing should have made sure that the output is the same from each. Of course it could just be people rating it different directions and some miss the intersecting faces while other dont.
RE: PrusaSlicer produces empty layers. Any way around it?
Thank you for this explanation.
Actually the problem occurred for the OP (Mac OSX) and for me (Windows 10).