raft does not cover the full object area

[goofyseeker311]

Cura Version

5.4.0

Operating System

Win11 RTX3060

Printer

elegoo neptune 3 pro

Reproduction steps

trying to slice the project file with raft only (no supports).

Actual results

does not raft the whole object area, leaves parts of the model without raft.

Expected results

should raft selectively under the whole object area with default settings

Add your .zip and screenshots here ⬇️

EN3PRO_fsfsd3-v13-chassis.zip

[goofyseeker311]

it will slice correctly if using raft + supports touching bed, which should be the default raft + no supports behaviour.

[fieldOfView]

I am 99% sure the bottom of the model is not 100% flat. Looks like the circular sections start just a little higher than the rectangular section, even if the difference is less than the first layer height.. By adding supports, the circular sections are extended downwards and touch the buildplate all the way.

[goofyseeker311]

its cad flat (pending a check), lol 0.5mm height difference, so raft will not raft that? I mean raft does not make printability arc tests? the print literally floats above nothing with nothing. it collapses down when printed. arc support test raft algorithm? should it not make like tree supports so its actually printable?

anyways there is a bug when the older 5.3.1 is installed, and its saved to "raftonly #2" profile but does not show "raftonly" profile in the 5.4.0. cant rename to "raftonly" even after uninstalling the 5.3.1, it wants to put #2 or #3 forcibly after the profile name.

yep flattening the bottom will make it raft properly without even "touching bed" supports.

[MariMakes]

Hey @goofyseeker311,

Welcome to the UltiMaker Cura Github 🚀
Sorry, it took us a while to get back to you 😞

I'm agreeing with @fieldOfView, the model itself is not flat.
To me, it doesn't seem like a bug in Ultimaker Cura anymore.
Would you still like to keep this issue open or do you agree that we can close it?

If you run into another issue like the numbering of your profiles, so we can track it separately in our issue tracker.

[github-actions]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.