Hole locations go wrong when doing a split and adding dowels (aka "holes both sides")

[NKT00]

Description of the bug

I couldn't find an open issue for this one.

I have a U shaped part with round cross section, and when I split it in half, in the slicer, everything works. If I add pins to it, that also works. But, if I ask for dowels, it doesn't do the combine before moving the split part, so the holes aren't generated in the right place.

I'll post an image later, and dig into it a bit more.

Project file & How to reproduce

Steps to reproduce:
Import the STL from Assem1 - shackel2-1.zip

1. Turn it 90 degrees so it is "flat" and parallel to the bed.
2. Initiate a split. It will by default want to cut it neatly in half. Leave it like that.
3. Select "Edit connectors". Don't change the default settings.
4. Add 1 or more "holes" by clicking on the model.
5. Click "Confirm connectors"
6. Perform the cut.
7. Note that the "holes" are in the wrong place, and not on the model.

Checklist of files included above

• Project file
• Screenshot

Version of PrusaSlicer

2.6.0 alpha5

Operating system

Windows 10

Printer model

Prusa 3S

[NKT00]

I haven't found a work-around yet. Will keep looking.

Edit: Ok, looks like it is related to the rotation of the part prior to the cut. I emptied the bed and added a built in square, and the cut performed as expected, with the holes where they should be. I then rotated the cube 90 degrees and tried the same cut, and it didn't work.

Playing around, it appears the holes are somehow moved after the preview but before the cut, resulting in, for example, this result where the pins are correct, but the holes they should go into are rotated incorrectly.

[neophyl]

I think this one is related #9991

[NKT00]

Yes, very closely! I'll look into it on the laptop. (I've asked if it occurs only after rotating a part, as here)

[NKT00]

Ok, I found a workaround. Do the split first, then move, arrange or rotate the split parts, and it works fine.

[kubispe1]

The issue should be fixed in the next release alpha6.
I am closing this issue as a duplicate of #9991