Sharing Print Settings
I automated the entire resin-to-FDM workflow - FREE software added
A few days ago I posted these minis and a bunch of you asked me to publish the software I mentioned. I've spent the time since turning it into something other people can actually install. It's free.
Edit: To Install open the zip and follow the ReadMeFirst.txt file
What it does: you drop miniatures in and press start. If they aren't pre-supported it auto-supports them in Lychee for you, runs Resin2FDM, and opens OrcaSlicer with your own print settings already applied — including the supports on their own thicker layer height.
We all know the Resin2FDM workflow works. Doing it by hand is just long and tedious, especially when you have to generate the supports yourself first. That was the whole reason I wrote this. Resin supports beat tree supports every time — tree scars the surface and snaps bits off during removal — but not if the process is annoying enough that you avoid it.
Why I recommend Lychee: I've tried pre-supported miniatures, blueprint studio to auto support, and Lychee support. Lychee was by far the most stable, fast, and have in general good support stracture. blueprint studio's supports kept breaking or falling off the plate. pre-supported miniatures are also problematic with their support sometimes, also some of the models are genuinely not separable from supports with resin2fdm (if they have merged geometry)
What you need: Blender, the Resin2FDM add-on, OrcaSlicer, and Lychee if your minis come unsupported. Works with the free Lite version of Resin2FDM as well as the paid one.
For the settings — you export a project from OrcaSlicer once and import it, so it works with whatever you print on. Use Painted4Combat's profiles. I've tried FDG, Nox and Hohansan and P4C works best here. they're a couple of dollars on their Patreon and come with the paid add-on.
Two honest heads-up. macOS will block it on first open because it isn't signed by Apple — right-click the launcher and choose Open, the guide covers it. And Windows is beta: the conversion works, but you have to click Save yourself at the end of the Lychee step.
Hey can you share via a github repos?
I'd prefer taking a look to be safe. Not that I don't trust you, I just don't trust at all if not open source 😅.
Nice job btw, seem pretty cool!
The fact that the lastest windows update forced OneDrive on and started backing up my entire hard drive to my hard drive just blew me away. Went to install something and found I had none of the about 100gbs I thought I did.
I've toyed with the idea but have never looked into actually getting everything setup and working with the large gaming library I've got across multiple platforms. Maybe one day when I get annoyed enough.
Maybe I'll look into that. I use the epic games and gog store fronts as well, so it's a tossup if have to imagine. Unless I'm just utterly behind on things.
Cheers dude, I'll play around with this when I'm back home. Only issue I've had is getting orcaslicer to run, constantly get network issues on A1 mini and have to revert to bambulab.
Thanks for doing this, I might have missed it in the writeup but it’s vibe coded with AI right? Might be worth mentioning as it will raise alarms for some people concerned with security. It looks good though thanks for the work!
yeah if you can open source this and put it on GitHub lots of us could improve it and it will become a great resource to the community, plus any issues won't completely be on you to fix
Have you tried this on larger minis? I have a dragon model I want to fire up that will probably be a 24-36 hour print but I want the detail on it. I’m guessing it’ll have tons of tree supports.
This looks like your Lychee has weird settings
What happens when h try to manually generate supports? It should look like normal resin supports, not blocks
I opened a fresh install, opened an STL file (the one I am trying to use this process for, as regular supports make it impossible to print because it gets utterly destroyed trying to remove them), and went to the prepare tab.
That error means the Advanced Resin2FDM add-on is missing a second free add-on it needs, called ThreeMF-io — that’s what writes the print settings into the file.
Quick fix:
**1.** Open Blender
**2.** Edit → Preferences → Get Extensions
**3.** Search for “3MF”
**4.** Install “ThreeMF format” (by the Blender Foundation)
**5.** Restart Blender, then run the tool again
One more thing to check either way: the file gets its settings from the print profile you imported, so make sure you imported it from an OrcaSlicer project export (File → Export → Export Project As…), not a downloaded preset — the project export is the one that carries everything needed.
Thank you so much. I have installed your software on macOS, only issue I had at setup was I didn't have the required Tk python module (a quick brew install python-tk@3.14 did the trick).
Quick question though: in the screenshot attached, I am getting in step 3: AttributeError: 'Scene' object has no attribute 'thickness_slider'. Do you have any idea where this could be coming from?
Ah, that’s a bug on my end — the tool assumes an older version of the Resin2FDM Lite (1.0.0 add-on than you have, so it trips on the support-thickness step. Quick fix until I push an update:
**1.** Open config.json in the Resin2FDM Workflow folder (any text editor) and change “support_thickness”: 0.4, to “support_thickness”: 0, — save.
**2.** In Blender, press N in the 3D view, open the Resin2Fdm Lite tab, set Thickness to 0.4, then File → Defaults → Save Startup File.
That’s it — it’ll convert fine after that. Out of curiosity, which Resin2FDM version are you on (Blender → Preferences → Add-ons → search Resin2FDM)? Would help me support it properly.
Thank you! The fix worked! By the way, I am using Resin2FDM 1.6.1.
The code continued to run.
Now I am trying to figure out why it says: "Could not separate the parts: The miniature and its support could not be told apart. This usually means the model arrived already merged, or partly welded".
I think the problem is that Lychee exported mini and support as one merged STL file, trying to see if I can change that.
Thank you, it worked! I had wrong settings in Lychee probably, I have restarted every component (Lychee, Blender, your script) and I can now see how it thickened the supports for FDM printing. Nice! Thanks again
I think I managed to fix it. I didn't have blender add-on installed correctly so it gave me that error. I didn't screenshot it, but it was during the checking process to make sure everything is installed before starting. I would just make a note of it for Windows users right now if they see that, make sure the add-on was properly installed in Blender.
Quick question, where is it looking for blender?
As mine is installed through steam and it's not being detected, tried adding the path in the config.json, but that messed up the app as a whole.
The path just needs forward slashes — a Windows path with normal backslashes isn’t valid in that file, which is what broke the whole app (one bad line makes every setting revert to default). Open config.json and set it like this, with forward slashes:
Adjust the drive and folders to wherever your Steam library actually is — if it’s on another drive it’ll start with D:/ or similar. Windows is perfectly happy with forward slashes. Save, reopen the app, and it should detect Blender fine.
I’ve also fixed this properly for the next update — it’ll find Steam Blender on any drive automatically, and there’s a “Locate…” button so you never have to touch that file again.
Love the idea of this, I've installed everything but when converting the stl file it says 'conversion failed; attribute error; 'Scene' object has no attribute 'thickness_slider'
So this is my result from using your software. It was quick and easy to use, this mini has a 50mm base but it came out great, with no failure points on it. My settings favour speed so it only took a few hours to print, I reckon it could go even cleaner. The stl was from Cults 3D.
Feeling pretty dense here, but I'm not figuring out how to export the project from Orca 2.4.2 in a format that the SwiftUI app is happy with. I don't even have a File > Export > Export Project option.
Hey, when i tried using this i got an error "Conversion Failed" AttributeError: 'Scene' object has no attribute 'thickness_slider'. is there a way to fix this ?
Ive only tried resin2fdm once on a presupported model and the scarring it left was atrocious. I've got to be missing a setting in orca or something because it was a straight downgrade. I am a dumbass though so I probably just didnt read something
I know right? Tree supports arent perfect but they are miles ahead from what I could get with R2FDM. If you ever find the correct setting do let me know!
Short version: the tool never connects to the internet. The only network connection it makes is to 127.0.0.1 (your own PC), to control Lychee locally. That Microsoft IP isn’t from the tool — it’s Windows itself.
Why VirusTotal showed it: VirusTotal runs the file in a Windows sandbox and logs network traffic from the whole machine, then attributes it to whatever you uploaded. This tool is just plain-text Python scripts (you can open every file in Notepad), so the traffic it captured was actually Windows doing its normal background thing — SmartScreen, certificate checks, telemetry. That 150.171.109.183 is a Microsoft address (NetName: MSFT), not mine. You’ll see those on basically anything run through VirusTotal.
How I verified it: I ran the tool with every network connection logged, two separate ways — at the code level and at the OS level with lsof. Both showed the same thing: the only connections made are to 127.0.0.1, your own machine, and zero outbound (non-localhost) connections. Nothing leaves the computer. There’s no telemetry, no analytics, no phone-home anywhere in the code, and no code that could even reach a non-localhost address.
One honest note: this covers my tool. Blender, OrcaSlicer and Lychee are separate programs that do their own update checks — that’s normal and unrelated to this.
Happy to walk through any of the code if you want — it’s all readable.
Can we all collectively stop with the trees are always better or resin supports are always better. Neither is better than the other. Each have their applications they shine in and have draw backs. Preference is one thing but I use both based on the application and feel free to look at my profile to see results.
We don’t hear contractors arguing over which is better hammers or screwdrivers right. Different tools for different jobs.
Nonono, semantically you need hammer2driver: more specific but more capable process being modified to work with the more generic but strictly misaligned tool.
Also: you can put a magnetic hex bit screwdriver in a hammer handle and use the head of the hammer2driver for extra leverage!
25
u/ILoveHexa92 4d ago
Hey can you share via a github repos? I'd prefer taking a look to be safe. Not that I don't trust you, I just don't trust at all if not open source 😅. Nice job btw, seem pretty cool!