Slic3r G-code snippets for FlashForge Creator Pro

by DrLex, published

Slic3r G-code snippets for FlashForge Creator Pro by DrLex Jun 5, 2017
0 Share
Download All Files

Thing Apps Enabled

Order This Printed View All Apps


Liked By

View All

Give a Shout Out

If you print this Thing and display it in public proudly give attribution by printing and displaying this tag.

Print Thing Tag

Thing Statistics

578Views 327Downloads Found in 3D Printer Accessories


These are the G-code snippets that belong with my Slic3r profiles for the FlashForge Creator Pro. Although I think the G-code is quite mature now, it is possible I will update it separately from the rest of the profile. Therefore use the ‘Watch’ button to stay notified of updates.
If you see that only this G-code was updated. you can copy-paste the updated snippets into the printer settings section of Slic3r, as explained in my article.

This code has the following features:

  • Z homing with the same speed as plate levelling procedure
  • Reliable tool change when printing with left extruder
  • Only heat nozzles to 140°C while waiting for the bed to heat, and then continue heating, to avoid baking filament inside the extruders when the bed needs a long time to heat
  • Before printing the priming line, chop off ooze on front edge
  • Extrude a line across the front of the bed to prime the nozzle
  • Do an extra wipe on the extruded line
  • No dubious fiddling with stepper VRefs
  • Work around typical extruder lag when the actual print starts

It is probably easy to adapt this code for other slicers like Simplify3D, if you know how to substitute the parameter names.

(Again, I attached an STL file just because Thingiverse only allows Things with some kind of 3D model.)

Print Settings

Printer Brand:



Creator Pro



Tweaked start G-code: wait slightly farther away from the front edge to reduce risk of ooze not being properly chopped; improve sideways chop and add another final move for another small wipe across the extruded line; set all speeds to sensible values (although some are simply overridden by firmware limits anyway).


No longer disable Z stepper in start G-code, because this could cause the platform to drop if the Z axis is very well lubricated (it could also introduce a small error due to microstepping being interrupted). Also slightly reorder options summary to better group items that I care the most about.

More from 3D Printer Accessories

view more

All Apps

Auto-magically prepare your 3D models for 3D printing. A cloud based 3D models Preparing and Healing solution for 3D Printing, MakePrintable provides features for model repairing, wall thickness...

App Info Launch App

Kiri:Moto is an integrated cloud-based slicer and tool-path generator for 3D Printing, CAM / CNC and Laser cutting. *** 3D printing mode provides model slicing and GCode output using built-in...

App Info Launch App
KiriMoto Thing App

With 3D Slash, you can edit 3d models like a stonecutter. A unique interface: as fun as a building game! The perfect tool for non-designers and children to create in 3D.

App Info Launch App

Print through a distributed network of 3D printing enthusiasts from across the US, at a fraction of the cost of the competitors. We want to change the world for the better through technology, an...

App Info Launch App

Quickly Scale, Mirror or Cut your 3D Models

App Info Launch App

3D Print a wide range of designs with Treatstock. Easy to use tools to get the perfect result. The global 3D printing network that connects you with high-quality and fast working print services nea...

App Info Launch App

Hi DrLex,

Have you use MatterControl with your FFCP? I use 3 different slicers, all have their pros & cons.
FFCP's built in second extruder offset does not seem work with MatterControl or maybe it is getting overridden, it looks good on the GUI but not in printout, I fix printout by adding X offset -34.003, but now the generated GUI view is off.

No, I haven't used it. Your slicer should not be aware of the offset between the nozzles, it should be set to 0 because the firmware handles the offset. If you perform a T1 command, the printer will shift the carriage, but only if there is enough room (this is why my start code first makes a move of at least 34mm to the left).