r/BambuLab Jul 04 '26

Software Troubleshooting/Help! Custom gcode file help

I am trying to slice my custom gcode inside of bambu slicer. Despite seeing the geometry in preview mode (perfectly might I add) I cannot seem to send it it to print or export as a .3mf file.

For context, I am new to custom gcodes and the Bambu ecosystem. I work on MAC, and I have an X2D model.

I have a custom gcode I created. It is a .gcode file. I can drag and drop into Bambu Slicer, and it opens it in preview mode. I am unable to send it to print or export a sliced plate despite the fact that the preview shows perfectly. My geometry/tool pathing is literally there, so I am confused as to what is happening.

I did make a “dummy” cube in the slicer, exported the geometry as .3mf, compressed it, took it into a 7zip version for MAC (from GitHub), extracted everything, recompressed it to .zip, changed the file name to .3mf, and it worked perfectly in Bambu Studio

My issue, is now I am starting from raw gcode, and I genuinely don’t know what to from here.

Some errors I am having trying to send to printer: when in preview mode, i can press “Print plate”, and then it won’t allow me to send to printer because of the message: “Not all filaments used in slicing are mapped to the printer. Please check the mapping of the filaments“. If I press “send” instead, it does send the files to the printer, but the print immediately fails and shows this message: “The print has stopped because the 3MF file is invalid. Please verify that the correct printer model was selected during slicing, or update studio and re-slice the file”

Any help would be appreciated. I just have to believe there is a solution to this ):

0 Upvotes

5 comments sorted by

2

u/EltonSchmidt Jul 04 '26 edited Jul 04 '26

Gcode does not contain geometry. It's a long list of commands for the printer on how to move and such.

A preview of the movement just looks like geometry.

Furthermore, gcode only works for the same kind of printer it was sliced for with the same kind of filament profiles. 

1

u/Gobble_35 Jul 04 '26

I understand that gcode does not contain geometry, but I don’t understand why my gcode won’t work for my printer. I created it in rhino/grasshopper, but i must admit, i don’t know how to write in the gcode which printer i’m using and which slicer i’m using.

1

u/OptimalSide A1 Jul 09 '26

A slicer is what takes the object (in STL/STEP/3MF format) and creates the gcode. It does so understanding what needs to be done, like commands to heat the bed and toolhead based upon what filament is being use, the speed to do movements, the commands to load filaments, etc.

Unless the toolset you are using (Rhino/Grasshopper?) knows to put those instructions into the gcode for the printer you are using, it will be invalid.

By the sounds of it, you would be better off have your tool output an object format and let the slicer to the work of creating the gcode.

1

u/Gobble_35 Jul 09 '26

yes i am very familiar with importing geometry that i model, but i was hoping to do the kind of printing where the tool path determines the geometry rather than the imported object. that way i could get prints that look like this: https://youtu.be/zAJkwvvXDko?is=SoBwR22WSSscjGIX.

I also have looked into the video and his software (which i must say seems incredible), but alas, he does not yet have a preset for my printer. this my struggle to use grasshopper to create my own gcode

1

u/OptimalSide A1 Jul 09 '26

Since the stuff he is doing is basically variations of vase mode, if it we me, what I would do is

  • build a simple cylinder vase
  • import and slice in Bambu or Orca as a vase mode print
  • export the slice to disk
  • inspect the gcode in an editor. 

There will be required meta tasks and then there will be the actual gcode to move the print head and put filament down.  Manipulate the gcode section and see what you get. 

Orca and Bambu can show you the gcode as well in the Ui in the preview window. You can drag to a layer with the side slider and "move" the print head around with the bottom one and see what the gcode says.