Direct G-code generation

Direct G-code means the authoring tool emits printer moves (G0/G1, extrusion, start/end scripts) instead of a mesh for another slicer. The path is the design.

The problem this answers

Slicers optimize solids. Some prints are better when you specify travel, spiral Z, or a painted lattice yourself—especially vase walls, fabric-like line stacks, and edited existing G-code.

How people do it without 3dSynth

Hand-written G-code, FullControl, or post-processing a slicer file. That is precise and brittle. A conventional slicer remains the right default for solids with infill and supports.

How 3dSynth does it

Modules that own the toolpath: G-code Sculptor, SynthBlocks (Premium export), Node Sculptor in toolpath mode, Fabric Sculpt, Hex Grid, Predefined models, and Custom G-code. They share printer, material, and nozzle profiles. Preview can skip the collision buffer; export enforces it. You remain responsible for the print.

Example

Fabric Sculpt: pick parallel lines or fabric-weave, stack layers, download G-code fitted to the bed. Tutorial: first fabric stack. To inspect someone else’s file, use Custom G-code: editor basics.

When it works

Spiral vases, line-based sculptures, hex tiles, catalog parts, and G-code you want to see in 3D before sending to the machine.

When another tool is better

Mesh Sculptor and Texturize export STL on purpose. If the job is a solid that needs supports or a multi-part plate, generate or import that mesh and slice it. Do not force every job through direct G-code.