Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.9.0-alpha1 - part cutting improper behaviour #13637

Closed
2 tasks
EricPobot opened this issue Nov 24, 2024 · 3 comments
Closed
2 tasks

2.9.0-alpha1 - part cutting improper behaviour #13637

EricPobot opened this issue Nov 24, 2024 · 3 comments

Comments

@EricPobot
Copy link

Description of the bug

When cutting a part on an additional bed, the new parts are created on the default one and thus must be moved afterwards.

The logical behavior would have been to create the parts on the same bed the original one was located.

Project file & How to reproduce

  1. Put a part on an additional bed
  2. Apply a cut to it

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.9.0-alpha1

Operating system

Mint 21.3

Printer model

i3 MK3S

@Jan-Soustruznik
Copy link
Collaborator

Hello, @EricPobot , Thank you for your featback. We created insternal issue no. SPE-2583. We will try to fix in some next release. Thank you

@EricPobot EricPobot changed the title 2.9.0-alpha1 - part cutting improper behavious 2.9.0-alpha1 - part cutting improper behaviour Nov 25, 2024
lukasmatena pushed a commit that referenced this issue Dec 13, 2024
The cut arrange updated the Plater without the new objects
being on any of the beds. This led to mutliple beds reducing
the bed count and activating a previous bed. This in turn
ment that get_active_bed was temporarily wrong and the subsequent
arrange placed items on a wrong bed.

Improve this by explictly setting which bed is going to be
used for the arrange and than restoring the originally
active bed.

If there is just one instance, simply choose the bed the
instance is on. If there are more instances, use the active
bed for arrange.
@FidelCapo
Copy link
Collaborator

This issue should be fixed in version 2.9.0-beta1.
Closing.

@EricPobot
Copy link
Author

Works fine in latest beta. Thanks a lot for fixing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants