<kintel>
J25K53 The "strange" triangles is just a shading artifact; we use per-face normals, and in this case a non-planar quad was generated which needed to be subdivided into two triangles, and the two triangles are not in the same plane
<kintel>
Btw., I'd love to see that crash reproducible outside of Windows, but we've been unsuccessful so far..
<kintel>
Btw. if the nonmanifold issue is really about double-precision coordinates being merged into the same when converted to floating point, it would be interesting to pass each model through a very strict mesh optimizer. I believe the Manifold folks were also talking about that at some point.
<tja>
I think the docker image update mentioned in #5972 minorly broke the wasm build workflow -- I needed to throw in a reset "WORKDIR /src" at the end of the ephemeral Dockerfile in "scripts/wasm-base-docker-run.sh" to get a build (from earlier this year) working. I haven't yet pulled in upstream changes on my old branch, but as far as I can tell this isn't fixed in master's copy of "scripts/wasm-base-docker-run.sh"
sculptor2 has joined #openscad
<J25K53>
kintel I do understand what is happening when using quads, just wonder why there is only this single region and not symmetrical on the other half. but there is only one area while all other 7 identical regions of the cube are fine. Guess it is ok for higher resolutions.
sculptor has quit [Ping timeout: 248 seconds]
kintel has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
kintel has joined #openscad
<kintel>
J25K53 hmm. I think some careful inspection may be warranted..
Guest98 has joined #openscad
Guest98 has quit [Client Quit]
<kintel>
Wait, where is that screenshot from? Still MeshMixer? ..and it looks good in OpenSCAD?
J25K81 has joined #openscad
J25K53 has quit [Ping timeout: 250 seconds]
mmu_man has quit [Ping timeout: 258 seconds]
howiemnt has quit [Remote host closed the connection]
TheAssassin has quit [Remote host closed the connection]
TheAssassin has joined #openscad
Guest18 has joined #openscad
chancer has joined #openscad
Guest18 has quit [Client Quit]
J25K has quit [Quit: Client closed]
J25K has joined #openscad
chancer has quit [Quit: Konversation terminated!]
sculptor2 has joined #openscad
j45_ has joined #openscad
j45 has quit [Ping timeout: 276 seconds]
j45_ is now known as j45
j45 has quit [Changing host]
j45 has joined #openscad
JakeSays has joined #openscad
JakeSays_ has quit [Ping timeout: 248 seconds]
j45_ has joined #openscad
j45 has quit [Ping timeout: 256 seconds]
j45_ is now known as j45
j45 has quit [Changing host]
j45 has joined #openscad
splud has quit [Ping timeout: 255 seconds]
chancer has joined #openscad
ccox_ has joined #openscad
ccox has quit [Ping timeout: 256 seconds]
chancer has quit [Quit: Konversation terminated!]
chancer has joined #openscad
Guest46 has quit [Quit: Client closed]
sculptor2 has quit [Ping timeout: 248 seconds]
jbd has joined #openscad
chancer has quit [Quit: Konversation terminated!]
chancer has joined #openscad
sculptor2 has joined #openscad
sculptor2 has quit [Client Quit]
mmu_man has joined #openscad
chancer has quit [Quit: Konversation terminated!]
chancer has joined #openscad
chancer has quit [Quit: Konversation terminated!]
howiemnt has quit [Ping timeout: 256 seconds]
howiemnt has joined #openscad
J25K has quit [Quit: Client closed]
J25K has joined #openscad
chancer has joined #openscad
<pca006132>
sorry, I was on leave for 2 weeks with no computer (intentionally)
<pca006132>
is there anything that I should check?
J25K has quit [Quit: Client closed]
kintel has joined #openscad
J25K has joined #openscad
<kintel>
pca006132 I don't think so, but I have one question :)
<kintel>
We've had a few cases where external tools identify OpenSCAD exports as nonmanifold. I suspect it's a precision-related issue where double->float might merge some very close vertices making some triangles zero area
<kintel>
Do you think using Manifold's Simplify() algorithms as a post-process, before exporting, would help mitigate that?
<kintel>
I guess we'd have to choose some tolerance
<pca006132>
not fully, manifold's simplify only works on things that are topologically close to each other
<pca006132>
and does not guarantee the output to be degenerate free, we just try to make it better
<pca006132>
I think discarding degenerate triangles is probably a bug in their tools if they really do so... can openscad import the mesh? is that still a manifold?
<kintel>
In this case, I was hoping to simply remove very small triangles, where two vertices are so close together that they'd be coincident in 32-bit space
<kintel>
Yeah, It seems to be perfectly manifold (i.e. epsilon-valid). I haven't managed to establish a pipeline yet as the only tools complaining so far are Windows-only : /
<pca006132>
I thought people mentioned prusa slicer and meshlab
<pca006132>
those are cross platform iirc
<kintel>
meshlab using STL, but STL isn't great for this
<pca006132>
I think it accepts obj
<kintel>
I haven't yet managed to reproduce using Prosa
<kintel>
*PrusaSlicer
<kintel>
yeah, one report said that OBJ is OK, while 3mf is bad. More work needed to structure the investigation
<pca006132>
ah, weird
<kintel>
I was mostly curious what Simplify() could do for us if the issue is very close vertices
<pca006132>
sounds like a bug either in our export or in the import of that external tool
<pca006132>
I was discussing what simplify should do with our gsoc intern during my trip, I went to hangzhou and met him :)
<kintel>
heh, I try to blame other tools too, but for some reason, people believe that OpenSCAD is better at fixing workflows than other tools :/
<pca006132>
they probably say the same thing when talking to the other project maintainers :P
<kintel>
haha :)
<pca006132>
but yeah, ideally we should have a version of simplify that helps with this
<pca006132>
ideally can also collapse thin gaps etc.
<kintel>
J25K For the issue you had, could you open a GitHub ticket with very specific instructions on how to reproduce? ..but make sure you're using the latest version of all tools, so that we can try to reproduce
<pca006132>
I should start a discussion in manifold's repo
<pca006132>
(about "advanced" simplify)
kintel has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<J25K>
kintel for the crash? or the different export result?
<pca006132>
probably both, if you think both are bugs
<J25K>
well the crash exporting 3mf is already documented but with color not some intersecting face resulting in it
<J25K>
also the polyhedron has an intersecting face - so if you make wrong polyhedra you can't expect clean results - so i am not considering it as a bug
kintel has joined #openscad
<kintel>
pca006132 yeah, that's a better place to discuss the details!
sculptor has joined #openscad
kintel has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
chancer has quit [Quit: Konversation terminated!]
chancer has joined #openscad
Guest25 has joined #openscad
Guest25 has quit [Client Quit]
chancer has quit [Quit: Konversation terminated!]
kintel has joined #openscad
<kintel>
J25K I'm curious about the second issue. Could you open a GitHub issue for that, with exact info on how to reproduce?
<kintel>
If you're able to also reproduce with a more coarsely tessellated object, that would make things easier
<kintel>
..and if any other tools than meshmixer indicates an issue, that would be good info too
kintel has quit [Quit: My Mac has gone to sleep. ZZZzzz…]