Output files of size zero

[mihai-stanimir]

GFormer is an awesome idea with this code, first of all.

Seems to work for very simple manipulation, but often once I want to export the new g-code I get a file of size zero, and I also lose any modifications to the g-code. Running this via Live Server. Any ideas where I should look or how to fix it?

Edit: I sliced my Benchy with PrusaSlicer with pretty much stock settings.

[zalo]

Were any errors printed to the javascript/browser console?

[mihai-stanimir]

None that I could find. But it seems to quickly reload afterwards.
Doing more tests, it doesn't seem to happen with the provided g-code. But with my own slicing of the Benchy in PrusaSlicer 2.4 I get weird results. I managed to get some deformed output, but the model doesn't look printable, with travel moves apparently replaced by extrusion moves. Not sure why this happens, and I imagine it could be caused by something in the original slicing.

[zalo]

Could you upload your GCode?

The amplification should only multiply existing (positive) extruder movement; perhaps the slicer is creating small positive extrusions during travel moves...

[mihai-stanimir]

Sure. I've attached the GCode from PrusaSlicer 2.4.0 and the output of GFormer after adding one deformation point. Hope this helps.

3DBenchy_0.1mm_PET_MK3S_2h53m.gcode.zip
one.zip

[zalo]

Ahh, so it does.... I'll take a look to see why that is happening here...