2.7.0-alpha1 generates invalid gcodes

[sammcj]

Description of the bug

Testing out PrusaSlicer 2.7.0 Alpha 1 and I found it to generate invalid gcodes.

No config changes have been made from 2.6.x, the same project is loaded in, gcode is generated and Klipper shows it to be invalid.

I suspect some config changes need to be made perhaps relating to the commonly used preprocess_cancellation script, if that is the case I think PS should probably pop a warning up.

If you take the project that has been saved in 2.7.0-a1 and open it in 2.6.1 - the generated gcode prints without issue.

Gcode and Project attached.

Project file & How to reproduce

• foot-for-foot_2h26m_0.24mm_234C_PETG_ENDER5S1.gcode.zip
• foot-for-foot.3mf.zip

gcode.CommandError: Malformed command 'EXCLUDE_OBJECT_DEFINE NAME=foot-for-foot.stl id:0 copy 0 CENTER=110.000,110.000 POLYGON=[[112.732,56.987],[116.400,57.292],[119.571,57.774],[122.707,58.447],[125.796,59.308],[128.681,60.304],[131.791,61.582],[134.675,62.986],[137.468,64.562],[140.162,66.303],[142.363,67.923],[145.209,70.257],[147.544,72.456],[149.743,74.791],[151.796,77.255],[153.697,79.838],[155.438,82.532],[157.014,85.325],[158.418,88.209],[159.645,91.172],[160.537,93.755],[161.553,97.293],[162.226,100.429],[162.708,103.600],[162.999,106.794],[163.096,110.000],[162.999,113.206],[162.708,116.400],[162.297,119.102],[161.553,122.707],[160.691,125.796],[159.645,128.828],[158.418,131.791],[157.221,134.248],[155.438,137.468],[153.697,140.162],[151.796,142.745],[149.743,145.209],[147.544,147.544],[145.209,149.743],[142.745,151.796],[140.287,153.605],[137.468,155.438],[134.675,157.014],[131.791,158.418],[128.828,159.645],[126.132,160.576],[122.707,161.553],[119.571,162.226],[116.400,162.708],[113.206,162.999],[110.355,163.085],[106.794,162.999],[103.600,162.708],[100.898,162.297],[97.293,161.553],[94.204,160.691],[91.508,159.761],[88.209,158.418],[85.325,157.014],[82.532,155.438],[79.838,153.697],[77.541,152.006],[74.791,149.743],[72.456,147.544],[70.257,145.209],[68.204,142.745],[66.303,140.162],[64.562,137.468],[62.986,134.675],[61.582,131.791],[60.355,128.828],[59.424,126.132],[58.447,122.707],[57.774,119.571],[57.292,116.400],[57.001,113.206],[56.904,110.000],[57.001,106.794],[57.292,103.600],[57.774,100.429],[58.447,97.293],[59.309,94.204],[60.355,91.172],[61.582,88.209],[62.986,85.325],[64.562,82.532],[66.303,79.838],[67.994,77.541],[70.257,74.791],[72.456,72.456],[74.791,70.257],[77.255,68.204],[79.456,66.584],[82.532,64.562],[85.325,62.986],[88.035,61.667],[91.172,60.355],[94.204,59.308],[96.836,58.575],[100.429,57.774],[103.600,57.292],[106.794,57.001],[110.000,56.904]]'

As a side note, it seems that 2.7.0-alpha1 generates larger gcodes that 2.6.x:

That doesn't look much bigger - but earlier I had a file I tried that was 1.2MB with 2.6.x and 1.8MB with 2.7

Checklist of files included above

• Project file
• Screenshot

Version of PrusaSlicer

Version 2.7.0-alpha1+MacOS-arm64

Operating system

macOS 14.1

Printer model

Ender 5 S1

[rtyr]

Thanks, we will fix it for next release. It happens with combination of Klipper g-code flavor and label objects set to "octoprint-comments" (it was the only option in older PS versions).

It should work fine if you switch to "firmware-specific"

[lukasmatena]

SPE-2006

[sammcj]

Ah, glad you knew about this one! Thanks and keep up the amazing work - you're all appreciated greatly.

[lukasmatena]

Fixed in 2.7.0-beta1. Closing.