Hi folks,

I’ve used Cura as my main slicer with my Flashforge Creator Pro for several years with no major issues. It was a while since I had upgraded (4.12) and I decided to try out the latest version (5.6).

My printer and slicing profiles seemed to transfer over automatically, but when I tried to slice and print, I encountered a strange issue: It no longer heats the extruders or the bed.

It just starts “printing” immediately with stone-cold extruders and bed. The temperature settings in my slicing profiles seem unchanged from 4.12, so I’m a bit at a loss as to what is happening.

I can verify that this is not a hardware issue with the printer, as I can run print jobs generated in Cura 4.12, and the heaters work just fine.

Anyone else encounter this or a similar issue? Any known fixes or recommended troubleshooting advice?

Thanks in advance!

  • @callccEnglish
    1•6 months ago

    Wtf is that format and why would anyone use it. I guess it’s compressed. That would be the only reason to have a binary format for this.

    Also the who writes the x3g file? Is it cura directly?

    • @[email protected]OPEnglish
      1•6 months ago

      Wtf is that format and why would anyone use it

      I think x3g is the required format for all printers running Sailfish firmware, such as my FlashForge printer. I’d be hesitant to change the firmware, as I don’t want to risk bricking my printer if I do the wrong thing.

      Also the who writes the x3g file? Is it cura directly?

      Cura writes the files using the X3GWriter plugin by Ghostkeeper. Perhaps there is a way to turn off this plugin and compare the gcode?

      • @[email protected]English
        1•6 months ago

        I’m sure there must be a way to temporarily change Cura’s settings to export G-code instead of x3g. Did you figure this out yet?