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 Alpha1 - Avoid crossing perimeters - better, but not fully fixed #13669

Open
2 tasks done
marsmanp opened this issue Nov 26, 2024 · 2 comments
Open
2 tasks done

2.9 Alpha1 - Avoid crossing perimeters - better, but not fully fixed #13669

marsmanp opened this issue Nov 26, 2024 · 2 comments

Comments

@marsmanp
Copy link

marsmanp commented Nov 26, 2024

Description of the bug

The same as seen here: #13445

The Avoid crossing perimeters being enabled does not always force travels to be within the object even if it is possible to do so. In the attached file you can get great/good/poor/bad results depending on other settings like number of perimeters, seam location, and infill type. There may be other settings that help/hurt the behavior, but these are the ones I know of

Project file & How to reproduce

ACP.zip
A few examples of different settings for perimeters/infill causing changes in travels crossing/not crossing perimeters.
Slide1
Slide2
Slide3
Slide4

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.9.0 alpha1

Operating system

Windows 10

Printer model

Anycubic MegaPro

@SachCZ
Copy link
Collaborator

SachCZ commented Nov 26, 2024

Hello @marsmanp, thank you for the report. We know about this and it will be fixed in the next iteration.

@Jan-Soustruznik
Copy link
Collaborator

SPE-2578

lukasmatena pushed a commit that referenced this issue Dec 13, 2024
…):

- Turn off external motion planner when the instance is the same for layer
change.
- Properly set the instance shift for travel_to_first_position. Affects
  simple rectangular layer change.
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