STL-GCODE

[bbrown64]

I print using Cura. I load a model's .STL file to print. I have never saved a GCODE. Is it important to save GCODES along with the .STL of any certain parts I print?

[thawkins]

I print using Cura. I load a model's .STL file to print. I have never saved a GCODE. Is it important to save GCODES along with the .STL of any certain parts I print?

No, as lomg as you have the settings for your printing program and the stl file, you have the gcode. CURA creates gcode automatically and sends that to the printer when you print. The only time you need to save gcode specificaly is if you are printing via an sdcard instead of using usb.

[Mach-Chris]

It's worth noting that if you're experimenting with settings, saving the gcode could be beneficial as you can go back and read off your settings from the files. Comes in handy sometimes

[RetireeJay]

It's kinda yes and no. I have often experimented with settings, for example to get the walls to fill in just right or get the support to do what I want it to do. So the ability to save the G-code and give it its own descriptive name is helpful. On the other hand, the G-code has been generated with a specific filament diameter (and optimum extrusion temperature), and it won't be as useful for doing a print at a later date if you are using a different spool of filament.

For those who are using Repetier instead of Cura (including myself), I strongly prefer to generate a G-code file with Slic3r and then load the G-code into Repetier - because I get more (or easier) control over the slicing process that way. That's not an issue with Cura because Cura is first and foremost a slicer with in-depth controls, and only incidentally a User Interface to the machine.