Slic3r should check if users model is merged into purge block - MMU2

[mylife4aiurr]

Bug:
Slic3r should check if purge block is merged with users model in mmu2 prints, and not allow this. Currently slic3r will merge skirt and model into purge block on mmu2 prints and not warn user, so you get this:

This model took more than a day of printing time
@Kuntry3d

1.41.1-rc+win64
Win10

[AbeFM]

Similarly, the skirt can run under the block - and supports also.

All three should be looked for. The skirt, in particular, can just be set up to include the block. It seems the block size should be calculated, then it added as an object to the bed and the normal pre-slicing checks (and skirt planning) done.

[lukasmatena]

the normal pre-slicing checks (and skirt planning) done

The "normal" checks do not include (and never included) intersection of objects. This issue is not specific to the wipe tower. Closing as a duplicate of #2501 and #2378

[AbeFM]

One could argue that the block is a special case - since it changes size after hitting slice, it is easier for a build plate to have a failure that is not obvious from the set up screen.

[mylife4aiurr]

Yea i cant understand why this isnt something the slicer should check 4 and either correct or at least warn about.

[lukasmatena]

One could argue that the block is a special case

In that case supports are also a special case (they also do not show in 3D view, not even after slicing). Which makes the case not so special.

slicer should check 4 and either correct or at least warn about.

Possibly it should, I'm not arguing about that. We may improve this in future. I just don't think we need another issue to track it, having #316, #1275, #684 and #2598 all open.

[AbeFM]

Agreed. I think your response is adequate: It's not something we do, but we're aware of it.

I'd agree the issue should be closed as it's well captured in existing ones.