OrcaSlicer icon indicating copy to clipboard operation
OrcaSlicer copied to clipboard

Filament Flow Ratio is not getting passed into the slicing

Open QuackenAudio opened this issue 10 months ago • 1 comments

Is there an existing issue for this problem?

  • [x] I have searched the existing issues

OrcaSlicer Version

2.3 Beta

Operating System (OS)

Windows

OS Version

indows 11

Additional system information

AMD Ryzen 5 5600 6-Core Processor 3.50 GHz 64g Ram

Printer

Creality K2 Plus

How to reproduce

open filament edit Flow Ratio from 1.0 to anything else (0.6 as an example)

check print

Actual results

doesnt slice at changed flow ratio I have to manually change it in the klipper fluidd intrface after it starts to print

I have a filament that prints best at 0.6 flow tested by making a big square, and adjusting flow down till first layer looked great prints a perfect layer at 0.6

but when I enter that into the filament flow ratio, it doesnt appear to work when I print, it prints the same as if I have a flow ratio of 1.0 in orca. when I manually turn it down, it looks great

Expected results

Flow ratio should transfer to the gcode if I select 0.6, it should change flow to 60% either directly in the G-Code, or in the klipper flow ratio

Project file & Debug log uploads

no file to upload

Checklist of files to include

  • [ ] Log file
  • [ ] Project file

Anything else?

No response

QuackenAudio avatar Mar 07 '25 06:03 QuackenAudio

Flow ratio of 1:

Image

Flow ratio of 0.5:

Image

Works as expected. Check the flow number in the bottom of the screenshots above.

The Klipper UI does NOT change to reflect the filament flow by the slicer - the slicer directly controls the G1 X Y En commands by adjusting the number n (ie the length of material extruded over a distance). The klipper UI places a modifier on top of the slicer command.

For example if you set your filament flow to 1.00 and the klipper UI to 98% it would simulate the same as if the slicer was set to 0.98 and the klipper UI to 100%.

So all in all, not a bug.

igiannakas avatar Mar 07 '25 09:03 igiannakas

I found where the issue was.... somehow I had a messed up value in the first layer filament flow and it was messing things up

QuackenAudio avatar Mar 13 '25 18:03 QuackenAudio

Orca bot: this issue is stale because it has been open for 90 days with no activity.

github-actions[bot] avatar Jun 12 '25 00:06 github-actions[bot]

Orca bot: This issue was closed because it has been inactive for 7 days since being marked as stale.

github-actions[bot] avatar Jun 19 '25 00:06 github-actions[bot]