supermerill / SuperSlicer

G-code generator for 3D printers (Prusa, Voron, Creality, etc.)
4.08k stars 517 forks source link

G1 F-nan(ind) in gcode #2866

Closed filotto78 closed 6 months ago

filotto78 commented 2 years ago

Bug description SuperSlicer generated a gcode with G1 F-nan(ind) instruction.

Expected behavior Don't see this instruction on the generated gcode.

!!>> Project File <<!! In the zip file you will find only the gcode since 3mf file zip was too big.

gauntlet_cover gcode.zip

The emf file can be downloaded here: https://drive.google.com/file/d/1wGfEeGs8THRr6s8CxewHMWvDQ3GtUQSF/view?usp=sharing

To Reproduce Steps to reproduce the behavior:

  1. Open the 3mf
  2. Slice the model (this is a multimaterial model)
  3. Export the gcode
  4. See error on gcode

Screenshots image

image

image

Desktop (please complete the following information):

Additional context This is a multimaterial file.

filotto78 commented 2 years ago

Access to the file stored in Google Drive has been granted.

Slabity commented 2 years ago

I am seeing this as well, and for me it appears to be related to either the length of time of the print or the number of objects I am trying to print.

Here is the STL

Here is the 3mf

I am able to place 5 of those objects in a single print, but the moment I add a sixth one it seems to screw up the processing and show the following for times:

image

Not sure if it matters, but I am using Linux in case it is specific to that platform.

marcuswu commented 2 years ago

I am experiencing something similar that I believe is related.

Instead of nan, I'm getting inf for used filament: Sliced Info

The gcode has a G1 F0 which the printer doesn't like and inf extruder movements. gcode

Note that the print begins with the purge / wipe tower and the first layer of that prints successfully before the printer encounters the problem gcode. The relevant files are linked below:

ball halves.3mf ball halves.gcode ball half 1 stl ball half 2 stl

supermerill commented 2 years ago

can't replicate on latest nithgly. Should be fixed in next release

Slabity commented 1 year ago

I can confirm this has been fixed on my end (using 2.4.58.3). No longer running into the same issue.

If nobody else is having this problem then I think it's safe to close.