search

SoftFever / OrcaSlicer

G-code generator for 3D printers (Bambu, Prusa, Voron, VzBot, RatRig, Creality, etc.)
https://discord.gg/P4VE9UY9gJ
GNU Affero General Public License v3.0
5.93k stars 675 forks source link

Identify Completely Floating Regions #594

Open diginfo opened 1 year ago

diginfo commented 1 year ago

It would be great if as well as this warning, it actually identifies the problem by maybe indicating it with a colour and zooming into the layer, or something similar.

I am getting this error and I cannot find where the problem is, might be that I just don't know how to see it.

Screenshot 2023-03-27 at 10 32 44 AM Screenshot 2023-03-27 at 10 27 54 AM
Ltek commented 9 months ago

Agreed, I got this error today but cant find anywhere that it is floating... I'm suspecting this is a bug but if it is identifying a real issue with the design, it should colorize it so we know where.

github-actions[bot] commented 6 months ago

GitHub bot: this issue is stale because it has been open for 90 days with no activity.

Ltek commented 6 months ago

bump

pacmac commented 6 months ago

It's not stale, the issue still exists but is probably not a priority.

stephbellemare commented 5 months ago

I found that if you slice and it gives a floating warning, change the infill %, reslice and put back to original infill %, slice again, the warning will have disappeared.

Ltek commented 5 months ago

I find the warning has been consistent (and correct) for me... but would like the slicer to color-code the onscreen image so we can see what it has identified. Its often very difficult to see what it thinks is floating vs just a normal overhang

ThrawnyBoy commented 5 months ago

I found that if you slice and it gives a floating warning, change the infill %, reslice and put back to original infill %, slice again, the warning will have disappeared.

This worked for me so definitely a bug somewhere. Thanks for the tip to workaround the error it was annoying me when you can plainly see (and know) there is absolutely no floating regions.

MaDMaCKeM commented 4 months ago

Same here, changed infill setting and the error disappeared

kylek29 commented 4 months ago

I found that if you slice and it gives a floating warning, change the infill %, reslice and put back to original infill %, slice again, the warning will have disappeared.

This worked for me so definitely a bug somewhere. Thanks for the tip to workaround the error it was annoying me when you can plainly see (and know) there is absolutely no floating regions.

Although it's not evident in the OP's part, I have had a few parts that would create a floating path when sliced, and if printed as is it would have printed in thin air. I can't remember the exact settings, but I believe I fixed it by switching from Arachne to Classic. It had something to do with how it was ordering the procedures (coincidentally, there was/is an issue on PrusaSlicer for the same thing). They might be connected.

edit And for anyone curious, the way I found where it was messing up was to slice it, then go layer by layer (showing only 1 layer at a time) until I saw one that would print in air.

If I had to guess on the OP's part, it's the outer edge on the upper portion that overhangs. Possibly it's trying to print that first (depending on which direction the path takes from the seam)?

github-actions[bot] commented 1 month ago

Orca bot: this issue is stale because it has been open for 90 days with no activity.

Ltek commented 1 month ago

ping