Generated model containing errors (not manifold???) leading to filled out holes in letters in cura

[electr1cBugaloo]

First of all thanks for this free tool 👍

The ä generated with the settings below lead to an errornous print with cura. This is likely an error in the generated model. Running the model through an STL Repair tool leads to a working model. Error reproducable with settings below and at least Cura 5.1 and 5.2.1. I have attached the STLs (output from your tool / fixed output from STL Repair) below .zip file.

Top model in Cura screenshot below is the output from your tool. Bottom model is the fixed version, notice th belly of the a not being filled any longer. I removed support layer in this view to make the error more visible. Also please notice, that in Cura preview, both models look identical.

References: https://community.ultimaker.com/topic/38747-why-is-cura-filling-in-my-holes-please/ https://formware.co/OnlineStlRepair

Output STL Fixer

-> In queue. Waiting before you in the queue: 0 (refreshing each second)
-> Reading file and indexing vertices
-> Analysed your file:
--> 0 Naked edges (?)
--> 0 Planar holes (?)
--> 0 Non-planar holes (?)
--> 528 Non-manifold edges (?)
--> 263 Inverted faces (?)
--> 8 Degenerate faces (?)
--> 792 Duplicate faces (?)
--> 0 Disjoint shells (?)

-> Repairing: 100.00%

----- Repair completed in 2448ms ------
-> Vertex count changed from 1640 to 1724 (+84)
-> Triangle count changed from 3804 to 3444 (-360)
-> ae.stl available for download. Click the button below to download

STLs.zip

[romgere]

Hey @thatSecOpsGuy first thx for the super detailed issue ! (if all issue could be reported as your ❤️ )

Second, sorry for late answer, but I have very limited time to spend on this tool.

I'll probably take a look at your issue later, but given you added the workaround to fix it with the external tool, I think it will wait a little bit more...

Thx for your patience

[electr1cBugaloo]

Since this is a free tool for which I am opening a report and since I am not providing a PR, a good and detailed issue is the least I can do 😊 But I am glad you appreciate it, it was a bit of time to reduce the test case and provide all the info.

And regarding fix - sure, no worries. It is not like it is not usable or there is no workaround. Just thought I'd document it so you have a good test case / something easily reproducable whenever you have the time to fix it.