It Started With My Daughter

My journey into 3D printing didn't start with a hobby or a side project. It started the evening I got home from work and my daughter Hannah met me at the door with that look — the one every parent knows. Something was weighing on her.

She told me her senior project was waiting on the school's single 3D printer, and several other students were ahead of her. Senior projects in Florida are due at the beginning of May, and time was already running short. At the time I was running my own air conditioning contracting business in Central Florida. Free time was not exactly something I had in abundance.

But she's my daughter. So I took on the challenge with her.

We bought a Creality Ender 5 Plus — the build volume was exactly what Hannah's project needed. And like every single person who picks up a 3D printer for the first time, I found myself deep in a rabbit hole of YouTube videos and Google searches, trying to figure out what settings actually worked and why.

The Sticky Note Problem

Here's what nobody tells you about getting started with 3D printing: one print goes perfectly, and the very next one turns into a pile of spaghetti filament on the build plate. And you're standing there asking yourself — what did I change? What did I do differently?

So, you start writing things down. Sticky notes. Scraps of paper. A note on your phone. Maybe a spreadsheet if you're organized — but who has time for that when you're just trying to get one clean print out the door?

I knew the slicer programs had profile libraries you could create and save. But PrusaSlicer alone has around 356 different settings. There was no way I was going to build out and label hundreds of profiles and somehow remember which one matched which print. It just wasn't practical.

What I really needed was something that would just — automatically — read the G-code file, pull out every setting the slicer had embedded, and save it somewhere searchable. With a note attached. And a way to mark whether the print worked or not.

That tool didn't exist. So, I built it.

Why I Built 3DPrintLogPro

3DPrintLogPro is not a tool I built to sell. It's a tool I built because I needed it, used it, and after a few years of refining it — realized other makers probably needed it too.

Here's what it does: every time you slice a print and save a G-code file, 3DPrintLogPro can automatically detect that file, read the 300+ settings your slicer embedded in it, and save them to a searchable log. You give the print a name, mark whether it succeeded or failed, add any notes — and it's saved. Forever. Searchable. Exportable to Excel.

And when you find a set of settings that works perfectly — for a specific filament, a specific part, a specific printer configuration — you can push those settings directly back to your slicer as a new profile library. One click. No re-entering 356 settings by hand.

It supports PrusaSlicer, SuperSlicer, OrcaSlicer, Bambu Studio, and Cura. It runs on Windows.

She Got a Great Score

Hannah finished her senior project. She got a great score. And she was genuinely proud of what she built — we both were.

That printer never went back in the box. I've been using it ever since — through hardware upgrades, filament experiments, and countless projects. And the entire time, 3DPrintLogPro has been running alongside it, quietly keeping track of every setting change, every successful print, every lesson learned.

I'm not here to give you a sales pitch. I'm here because I've been exactly where you are — standing next to a printer at midnight, holding a sticky note, wondering what went wrong. I built the tool I wished I'd had on day one. And if it saves you from wasting one roll of filament or one failed deadline — that's exactly why I made it.

If this sounds like something that could help you, visit my shop page to learn more and grab a copy. And if you have any questions at all — about the program, your printer, your settings, anything — just click here and send me an email. I read every one.

— Danny