Prusaslicer Version 2.3.0+win64 - Netfabb "repair" breaks Tinkercad .stl files for import back into Tinkercad
In Prusaslicer Version 2.3.0+win64, Prusaslicer/Netfabb "repair," is breaking my Tinkercad .stl files for import back into Tinkercad. I've been repairing Tinkercad designs in PrusaSlicer, prior to printing. No problem with prints. But I have also been exporting the "repaired" .stl file immediately after the repair, replacing the original Tinkercad .stl. I discovered when I import the Prusaslicer/Netfabb repaired .stl, back into Tinkercad, the design is now corrupted beyond being easily fixed, containing strange, and severe gaps, across many planes. I am assuming this is not expected behavior, but I am pretty new to all of this (1 yr.,) so welcome enlightenment. I've included an image that demonstrates the issue, corrupt .stl on the left (white.)
With the high volume of designs I am creating in Tinkercad, despite trying, they aren't the best organized, so recreating the Tinkercad compatible .stl files for my library (to sit alongside "repaired," .stl files for printing, I suppose,) is not going to be a small chore.
My goal with this post is to document my experience as I go forward, experimenting with ways to address the problem, and of course to whine a little bit. With the whining done, my first step will be to update to the latest stable Prusaslicer.
RE: Prusaslicer Version 2.3.0+win64 - Netfabb "repair" breaks Tinkercad .stl files for import back into Tinkercad
I wouldn't be surprised if the Netfabb function wouldn't work properly but it would help to post an example 3mf project or a specific stl so we could replicate this behavior. Also, you may want to check out https://tools3d.azurewebsites.net/. It's basically Microsoft's frontend to the Netfabb engine, at least it could provide hints whether the issue is with the Netfabb engine, Prusa's implementation of it, or your model.
RE: Prusaslicer Version 2.3.0+win64 - Netfabb "repair" breaks Tinkercad .stl files for import back into Tinkercad
Tinkercad files are not stl files. When you export a tinkercad design it exports as stl but the underlying file doesn't change as stored on their servers.
Many software don't export valid stl files (depending on the model obviously) and so that's why they need repairing. Once its fixed the stl is usually suitable for printing but they may still contain errors.
When you import an stl file into tinkercad you are then also relying on how well its import function works. Generally you cant expect to export to a different file type and then load that back in and have it behave as the original model with ANY 3d modelling software. The export to a different format pretty much loses some information, especially to a simple format like stl.