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
first, a number of parameters are changed, which include setting the nozzle height to an inappropriately high number for the nozzle diameter (ex. 0.4mm for a 0.4mm nozzle):
Upon slicing, the models grow in size suddenly:
Before:
After:
Slicing preview:
These do not print properly, as the layer gaps are too large for proper layer adhesion. It is useless for flow cal because the huge gaps cause massive under extrusion on anything other than the first layer.
Expected results
I would expect the flow tiles to not only retain their original as-sliced size (and not grow), but also that the calibration would not alter layer heights unnecessarily
more developments: the bug described happens inconsistently, and does not always resolve itself when restarting the slicer. Sometimes changing to a different printer profile, and then back again fixes the issue.
Is there an existing issue for this problem?
OrcaSlicer Version
2.2.0
Operating System (OS)
Windows
OS Version
Win10
Additional system information
No response
Printer
Creality K1C
How to reproduce
Actual results
first, a number of parameters are changed, which include setting the nozzle height to an inappropriately high number for the nozzle diameter (ex. 0.4mm for a 0.4mm nozzle):
Upon slicing, the models grow in size suddenly:
Before:
After:
Slicing preview:
These do not print properly, as the layer gaps are too large for proper layer adhesion. It is useless for flow cal because the huge gaps cause massive under extrusion on anything other than the first layer.
Expected results
I would expect the flow tiles to not only retain their original as-sliced size (and not grow), but also that the calibration would not alter layer heights unnecessarily
Project file & Debug log uploads
Flowrate Test - Pass1.zip
Checklist of files to include
Anything else?
No response
The text was updated successfully, but these errors were encountered: