Bambu Studio, OrcaSlicer and PrusaSlicer can run a script on every G-code file they write, passing the file’s path as the last argument. tessafab rewrites that file in place, so set it as the script and every slice comes out patterned.
- Make the project in the app: assemble the pieces, choose the pattern, save the
.tessafab.json. - Add the hook in your slicer (below), with the full path to
tessafaband to the project. - Slice and export as usual.
With the app’s own tessafab, the hook patterns every piece when the app is activated on this computer (or on the trial), and one chosen piece otherwise.
Bambu Studio and OrcaSlicer
Open Prepare → Process, switch on Advanced, open the Others tab, and in Post-processing Scripts enter one line, with quotes because of the spaces:
"/Applications/TessaFab.app/Contents/MacOS/tessafab" --project "/path/to/model.tessafab.json";
On Windows:
"%LOCALAPPDATA%\TessaFab\tessafab.exe" --project "C:\path\to\model.tessafab.json";
Save it as a custom process preset, so you can switch it on per print.
PrusaSlicer
Print Settings → Output options → Post-processing scripts:
"/Applications/TessaFab.app/Contents/MacOS/tessafab" --project "/path/to/model.tessafab.json" -q
Things to know
- The slicer’s preview doesn’t show the pattern. It shows the toolpaths before the hook runs. Check the pattern in the app’s Preview step first.
- Turn Ironing off. Ironing would flatten the pattern.
- If the hook fails, the slicer says so and the G-code is left unchanged: nothing prints with a wrong pattern.
- Re-slicing is fine. The plate is matched to the project by its pieces, even after small changes.
- Not tested yet: the hook from inside the Bambu Studio app (its command-line slicer ignores post-processing scripts). Try it on a small part first.
Your path may differ. The Windows path above is the default (installed for the current user); if your slicer doesn’t expand
%LOCALAPPDATA%, write the folder out in full. If you installed TessaFab elsewhere, usetessafab.exein that folder, besideTessaFab.exe.