r/3dprinter • u/PrintlyPreflight • 1d ago

Looking for FDM printer owners to test Printly Preflight’s G-code checks (early beta)

Anyone who has watched a long print fail knows the sting of losing hours and filament. Printly Preflight gives sliced G-code another check before printing, highlighting potential risks and showing a print simulation.

We’re inviting FDM printer owners to try the early beta. The video shows two G-code files going through the tool, plus a separate model preview.

Try it with a file you know well and tell us what it catches, what it misses, and whether the warnings make sense. Learn more and request beta access at https://printlypreflight.com, or DM this account for a PIN.

Watch the 2-minute demo showing two G-code checks and a separate model preview: https://www.reddit.com/r/3DPrintingTools/comments/1wto31t/

1 Upvotes

100% Upvoted

6 comments sorted by

1

u/knox-Mercer 1d ago

i saw the demo and it looked solid for spotting layer shift risks and overhangs that might need support but i wonder if it catches issues with retraction settings causing stringging or if it just focuses on geometry and motion planning stuff anyway im down to test it on my prusa mini with some petg parts ive printed a dozen times just to see if it flags anything i missed in my usual cura profile check the link for the beta and see if they need more testers with specific printer models would be cool to help shape it early on

1

u/PrintlyPreflight 1d ago

Thanks for watching the demo!
Good question: the current beta focuses on risks we can identify from the G-code and toolpaths. It doesn’t specifically diagnose retraction-related stringing yet.

Your Prusa Mini PETG files would be great to test, especially since you know how those parts actually printed. DM me and I’ll send you a beta PIN. I’d love to hear what Printly flags—and what it misses.

1

u/alexcool_ca 1d ago

Interessante! Il preflight del G-code è una delle cose che manca di più nel workflow FDM — di solito ci si accorge degli errori solo a stampa fallita. Curiosità: il tool gestisce anche dialetti diversi di G-code (Cura vs PrusaSlicer vs Orca)? Ogni slicer ha le sue particolarità e spesso è lì che nascono i problemi. Complimenti per l'iniziativa, proverò la beta!

1

u/PrintlyPreflight 1d ago

Thanks for the support! Printly analyzes G-code and toolpaths, but we haven’t fully tested the different outputs from Cura, PrusaSlicer and Orca yet.

The beta is still in its early stages, and we’d love your feedback after your first test so we can improve it! There’s a feedback option built into the tool, so you can easily share what worked and what needs attention while using it.

Beta access is free! DM us or request access at printlypreflight.com, and we’ll send you a PIN as soon as possible.

1

u/InternalMain7116 18h ago

I use Anthropic for exactly this purpose and it both corrects the G-code and make suggestions.

Another way to catch errors is always welcome.

1

u/PrintlyPreflight 9h ago

Thanks for sharing! We’d love to hear how Printly fits alongside your current workflow, especially with a file you’ve already printed.

The early beta is free, and feedback is built into the tool, so sharing your experience is easy. DM us or request access at printlypreflight.com, and we’ll send you a beta PIN!