I exported a model from blender, and “repaired” it with this online tool:
When I imported it into Bambu Studio, I got the alert that said it had “non-manifold edges” (over 1450 of them), so I right-clicked the part and selected “Fix Model”.
It’s been working on fixing the model now for 20 minutes and it’s still not done. How long should it take to “fix model”? Is it based on the size of the model? In this case it’s 21x90x10.
FWIW, Orca repairs the model in about 2 seconds. However, even when I ”fix” the model in Orca and export it, and then re-import it to BS, BS still thinks is has non-manifold edges (granted less than 10 edges, but still).
If Orca is based on Bambu, why doesn’t Bambu work at least as well as Orca?
UPDATE===========================
After an hour, I canceled the repair dialog. I simply don’t have the time to wait for buggy software.
It’s going to depend on the model and not just the physical size of the model. If the mesh is really fine it can take longer than if the mesh is coarse.
(Deleted a backwards progeny thing about BS and Orca.)
Meshes can be a bit tricky and can be extremely complex. If it’s a big model with fine mesh, and if the computer isn’t especially powerful, all that data may take a while to sift through. It’s all handwaving without the actual model though.
I’m running Windows on a 6-core CPU at 3.2ghz and 32gb RAM. Like I said,Orca does the repair in about two seconds - BS has never finished the repair, even after 1.5 hours of letting it work. There’s something wrong in BS.
I’m pretty sure Orca talks to Bambu printers at least in generating usable G code. You may have to sneakernet the file onto the printer SD card though. I’ve not used Orca to have experience with it specifically but have exported the G code out of Studio and copied it onto the printer SD card and printed that. Presumably you could print/export the G code out of Orca.
If it is working in Orca that might be a path forward. There’s others here with much more experience with Orca though.
Sorry to quote you there, but actually is the other way around. Orcaslicer is indeed based on Bambu Studio.
Yes i also noticed that repairing a model is faster with Orca. Bambu does the job “ok’ish” but takes much more time and sometimes it gets “stuck”. There is something wrong with Bambu Studio in regards to performance in their latest versions and i don’t think it will be corrected soon, from my point of view.
Try and repair the model in Bambu Studio once more and see if the problem persists. If it does, or you want the faster route, then repair it in Orcaslicer but don’t export it. Instead save it as a new 3mf file and try to open it in Bambu Studio to see if it works.
Totally ok to quote me. I said it and don’t mind being corrected. Actually I prefer being corrected. I wasn’t wanting to spread misinformation.
I thought Orca was open source and Bambu customized it for Bambu printers. So Bambu Studio was the first and Orca was derived from that? I swear I saw it said the other way.
Just searched and found this: OrcaSlicer is a popular, open-source 3D printing slicer developed by SoftFever. It is a direct fork of Bambu Studio, which itself is based on PrusaSlicer. While both share the same core engine and user interface layout, OrcaSlicer is specifically designed with advanced “power-user” capabilities.
So I stand corrected. So Prusa was 1st, Bambu Studio was derived from that, and Orca was forked from Bambu.
From my knowledge, Orcaslicer is a community driven fork of Bambu Studio. Of course it has long gone from Bambu Studio as a whole since it implemented lots of cool features. This is where the community driven forks do their wonders.
From my point of view, it would be way better if Bambu started forking Orcaslicer as their own slicer since they are faster to implement new and useful things, and also other printers (very fast).
There’s not “mine is better than yours”, both excel in their functions but Orca is more advanced at the moment, while maintaining that friendly to use UI and functions. Just the calibrations by themselves are amazing
Studio actually calls out to a remote Microsoft service to do the mesh repairs (I thought Orca did the same, but that could be old news). So it is a bit surprising it takes that long, as it’s generally not dependent on the local computer very much. It could (have been) a network issue or an Azure (MS cloud) glitch. It can take a while, though I certainly would also cancel it after > 10 minutes.
I’m not sure why Blender can’t export a watertight model in the first place, but some other tools to try may be Meshmixer or pretty much any other CAD software (that can work with meshes… like Fusion).
There’s also a small chance Studio is wrong about there being non-manifold edges. How does it slice? Or maybe it “can’t” be fixed properly automatically by current tools.
“I’m not sure why Blender can’t export a watertight model in the first place, but some other tools to try may be Meshmixer or pretty much any other CAD software (that can work with meshes… like Fusion).”
I’m right there with you. Studio will slice the model. I don’t know why it evaluates it the way it does. I’ve been fighting this for the last five hours.
In the process, I discovered that Orca’s stable release shares the same AppData folder (on Windows) with the nightly build. That means you can’t install/run both versions side-by-side without wondering if settings and data from one is being used by the other. I noticed this when both versions know project I had previously loaded. I’m getting seriously chuffed over this stuff…
“Try and repair the model in Bambu Studio once more and see if the problem persists. If it does, or you want the faster route, then repair it in Orcaslicer but don’t export it. Instead save it as a new 3mf file and try to open it in Bambu Studio to see if it works.”
Can’t do that because the 3mf in Bambu is different than the one used in Orca (because Orca has more features). It’s kinda annoying…
To repair a model in Blender, I highly recommend this tool, which is specifically designed for that purpose. This particular add-on specializes to fix “non-manifold edges.” I’ve been using this tool for many years now, and it’s always worked so far - even in the worst-case scenarios:
I would strongly advise against using online solutions like nano3dtech, because you’re essentially leaving the repair to an unknown black box.
You can also forget about the repair function in BambuStudio or Orca when dealing with complex objects, but that’s just a side note. These are slicer tools and aren’t optimized for repairing objects; they also lack essential settings.
