Slicer change -> filament estimation no longer works

Get Help Slicers
1

Slicer

Name, version, operating system

Cura, 5.9.1, linux X64

What is the problem?

I just switched from Slic3r to Cura and now the filament estimation no longer works.
I get: "Tool 0: 0.00m/0.01g" regardless of print time.
Markering_295

Is there a setting in Cura that needs to be turned on, or something in OctoPrint?
I am using Spool manager and this problem might relate to that.

What did you already try to solve it?

I noticed this difference in the slicers to express the consumption:
Slic3r:
; filament used = 668.6mm (1.6cm3) (at the end of the file)
Cura:
;Filament used: 1.6272m (at the beginning of the file)

So I tried editing the gcode file to use the Slic3r notation (except the volume), but it had no effect.

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)

octoprint-systeminfo-20250330114314.zip (1.9 MB)

Example GCODE file

Please upload here, the forum supports file uploads of GCODE files

UPLOAD HERE

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

WRITE HERE

2

While this doesn't help solve your issue, I tested using Windows 10, Ultimaker Cura 5.9.0 and 5.10.0 (looks like I skipped 5.9.1) and PrusaSlicer 2.9.1 (which is based on slic3r).

I sliced 3DBenchy.stl on all three slicers, uploaded the .gcode to OctoPi 0.18, OctoPrint 1.11.0rc5 and printed them with the Virtual Printer. All three showed the Filament info. For Cura 5.10.0:

image

I'll have to see if I can get Ultimaker Cura running on a Linux system but I suspect that the gcode will be similar to that produced by the Windows version.

1 Like
3

The 3DBenchy gcode produced by Ultimaker Cura 5.10.0 on Linux Mint 21.3 also showed the correct value.

I also checked safe mode just to eliminate any influence from plugins. You might try safe mode on your end.

4

I just tried safe mode, but it did not have any effect. When seeing that you had Cura 5.10.0, I upgraded and whaddayaknow - that helped!

Thanks for your help!
//

3 Likes