Description
Describe the bug
Slic3r creates gibberish/invalid feedrates in exported g-code, in auto-speed mode, but only if the maximum volumetric speed is set high enough (and all line speeds set to "auto" of course). With the attached config, setting this below about 16.5 mm³/s, seems fine, but at 17 mm³/s it gets weird.
This glitch looks somewhat similar to issue #3295.
If you examine the attached g-code, you'll find lines like the following (line 22898):
G1 F241502
G1 X82.789 Y95.243 E8.82378
G1 X82.418 Y95.614 F24000.000
G1 F1.18123e+06
G1 X82.418 Y104.387 E8.82738
G1 X82.809 Y104.758 F24000.000
G1 F245484I'm... pretty sure scientific notation is not allowed in G-code, and anyway it looks like some kind of math overflow, or maybe it's just not applying the configured max feed rate. Normal feed rates for this model are between about 10000 and 17000 mm/min, and should not exceed 24000 (the configured limit).
To Reproduce
- load the attached config.
- load a Benchy and slice it with that config
- Export to g-code and load that into Pronterface, observe the projected print time, and/or compare with the attached g-code file.
3D Model and Slic3r Configuration Export
Model: Just a common Benchy.
Config: slic3r-config-20190328.ini.zip
Benchy sliced with the above config: 3DBenchy.gcode.zip
Desktop (please complete the following information):
- OS: Linux (Debian)
- Version: git commit 05a2f90 plus the bridge angle fix (Fixed that bridge angle is lost on shell layers #4743) and @supermerill's thin walls PR (Thin wall improvements (v2) #4534).