Odd g-code output

So I have been downloading G-Code generated by Slic3r using Astroprint…

I got few odd surprises when I ran that code locally…(I do this when recalibrating the printer)
What happened was after the print finished it seems like a new print job started crashing into the first print.

What I found is that where Slic3r puts in comments at the end of the file with all the parameters (which is really nice)
it also puts in the start and stop G-code…now this would not be a problem but the cloud slicer seems do something
odd…somehow the stop and start g-codes are not commented out so they start to run…

What seems to be the case is that on the line above where the G-code would go there is no carriage return…thus
when my g-code which contains comments and carriage returns is inserted it is somehow not marked as a comment but is real code…you can see this if you load the downloaded file into Repetier Host which is what I typically use locally.

This is not a huge big problem but seem like maybe it is something that should get fixed at some point.
I actually think this is a problem with Slic3r so I will put up a similar post in their forum.

1 Like

I do not believe this error occurs in the prusa3d fork of slic3r version 1.33.8, at least when slicing locally…
Probably it is a problem with the either the version of slicer on the Cloud or maybe something to do with how the G-Code is sent to Slic3r from the web page…

On a side note it would be nice to have bigger box for editing start and stop code, something more like what is seen if you just preview the printer profile.