You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there an existing issue for this feature request?
I have searched the existing issues
Is your feature request related to a problem?
Currently infill combination height seems to be tied to nozzle width, e.g. always 0.4mm when using a 0.4mm nozzle. This makes some 3d infills unstable especially at low infill percentage. I want to combine infill every 2 layers when printing at 0.1mm layer height.
Which printers will be beneficial to this feature?
All
Describe the solution you'd like
Add a custom config option that changes how many layers got combined/combined infill layer height.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
I don't have examples of worsening infills right now but this post illustrates what I meant: https://www.reddit.com/r/FixMyPrint/comments/1cxdgmw/
Basically not enough layer adhesion between infill causing gyroid to form this grid-like pattern.
I cannot use infill combination in my prints because of this. I have max layer height set to 0.2mm on my 0.4mm nozzle and infill combination still wants to print 0.4mm high infills.
Is there an existing issue for this feature request?
Is your feature request related to a problem?
Currently infill combination height seems to be tied to nozzle width, e.g. always 0.4mm when using a 0.4mm nozzle. This makes some 3d infills unstable especially at low infill percentage. I want to combine infill every 2 layers when printing at 0.1mm layer height.
Which printers will be beneficial to this feature?
All
Describe the solution you'd like
Add a custom config option that changes how many layers got combined/combined infill layer height.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: