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

Feature request: make bridging over infill selectablebased on infill density. #1986

Open
wolfmanjm opened this issue Apr 28, 2014 · 6 comments
Assignees
Labels
Feature request This is an idea for a new feature in Slic3r Fixed with PR available to merge There is an update to address this issue in an open pull request. Gap Fill or Infill
Milestone

Comments

@wolfmanjm
Copy link

Currently the first solid layer on top of an infill layer is always done as a bridge at bridging speed and bridging flow rate.

This is unnecessary if the infill density is around 30% and really slows the print down if the surface is large.

A nice feature would be to use normal solid layer speed and flow rate as the first solid layer if the infill was over a certain selectable percentage.

@SystemsGuy
Copy link

I've noticed the same - I think I would prefer to have the option to enable/disable it as the level of "bridging assistance" I need does vary with filament type.

@Ccecil
Copy link

Ccecil commented Nov 8, 2014

Agreed. The only time I really need this slowdown in my prints is in cases of very low infill...such as <10% honeycomb.

@iXce
Copy link
Contributor

iXce commented Nov 8, 2014

Likewise. I have a setup where the fan is used for both hotend and filament cooling, and bridge speed works great for short periods, but for long periods it clogs the nozzle. Given that it really does not seem necessary (at least when infill is dense enough), I would be in favor of adding an option for this behavior.

@Rom1deTroyes
Copy link

I use to add some M220 S200 at the beginin of my prints to over-ride this...
... But sometimes forget to get normal speed after first layers been printed )-:
Will be great to have the ability to chose what we need, when we need it !

@lordofhyphens lordofhyphens added Feature request This is an idea for a new feature in Slic3r Gap Fill or Infill labels Aug 19, 2016
@lordofhyphens lordofhyphens modified the milestones: 1.3.5, 1.4.0 Aug 19, 2016
@lordofhyphens lordofhyphens self-assigned this Aug 19, 2016
@lordofhyphens
Copy link
Member

lordofhyphens commented Aug 19, 2016

Yeah, I can see where this would be useful (especially if you know your machine very well), and it looks straightforward to implement. I'll have a branch + pull request up shortly if someone wants to give a hand testing :)

I'll have the configuration default to 100% (which is the current trigger for not doing bridging infill).

@alranel
Copy link
Member

alranel commented Dec 19, 2016

Hm, I had actually addressed this issue in 38a9e32 (after this issue report). And I have one more improvement for making this logic even stricter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature request This is an idea for a new feature in Slic3r Fixed with PR available to merge There is an update to address this issue in an open pull request. Gap Fill or Infill
Projects
None yet
Development

No branches or pull requests

7 participants