-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Dynamic overhang speed does not respect pressure equalizer limits #9485
Comments
Thank you for your cooperation issue was tested. The fix will be part of the next release. |
Issue appears unresolved in the latest alpha. I still get abrupt speed change on overhang perimeters despite the volumetric slope being enabled. |
This pull request fully fixes it. I have manually merged it on my local machine and compiled it and the problem is solved: |
@murk-sy can you retest with new 2.6.0-alpha5. There are fixes to this issue.
Thanks |
@kubispe1 Does not appear to fix the issue |
in 2.6.1 has same problem, change pressure equalizer value not effect overhangs speed. project: |
Your best bet is to use orca slicer to be honest. I have ported over the pressure equalizer feature (extrusion rate smoothing) and have implemented the fixes proposed a year ago to respect pressure equalizer limits on external perimeters. Don’t think prusa will address this as, from what I see, don’t see the need for pressure equalizer on external perimeters at all. |
Fixed in PrusaSlicer 2.7.3-alpha1, thanks to @MGunlogson for the implementation. Closing. |
Description of the bug
When enabling both Dynamic overhang speed and Pressure equalizer, the max volumetric slope is not respected when entering the dynamic overhangs. Both settings are experimental.
Side note: Dynamic overhang speed is not listed as experimental in the slicer, while Pressure equalizer is.
Project file & How to reproduce
Checklist of files included above
Version of PrusaSlicer
2.6.0-alpha2
Operating system
Windows 10
Printer model
Prusa Mini
The text was updated successfully, but these errors were encountered: