Reply 20 of 20, by NeoG_
Lopo wrote on Yesterday, 18:19:That explains the last piece: the error dialog was telling you the truth every time. What varies is only what the repair decides to do with the open edges, and on the loads where it picked something harmless you had nothing to notice. So you probably did reproduce it — it just did not show.
And do not be hard on yourself about the QA. You gave me the one thing I could not get any other way: a screenshot of what a slicer actually did with the file. I had no test for watertightness at all until then, which is exactly why the bug survived this long. There is one now, and it runs over every combination the tool can produce.
Hi Lopo, the tool looks to be very useful, however keep in mind the forum does not allow the content of posts to be generated by AI models, and there is no exception for "my english isn't good". Please write the posts yourself.
98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer