<linext>
it would be nice if i could have the 3d print button launch prusaslicer with the last exported .stl
<linext>
preview > render > export stl > launch slicer > generated gcode > send to 3d printer
kintel has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
erectus has quit [Remote host closed the connection]
erectus has joined #openscad
erectus has quit [Ping timeout: 255 seconds]
erectus has joined #openscad
kow__ has joined #openscad
drkow has quit [Ping timeout: 255 seconds]
Bambukah has joined #openscad
<Bambukah>
Hello ! Have a nice day :)
arebil has quit [Quit: arebil]
arebil has joined #openscad
drfff has joined #openscad
kow__ has quit [Ping timeout: 256 seconds]
R2robot has quit [Ping timeout: 240 seconds]
jonasbits has quit [Ping timeout: 256 seconds]
califax has quit [Remote host closed the connection]
<Bambukah>
Someone use BOSL 2 ? I try to create a thread (and the hole) but they doesn't fit :'(
califax has joined #openscad
jonasbits has joined #openscad
califax has quit [Remote host closed the connection]
califax has joined #openscad
hyperair has joined #openscad
drfff has quit [Ping timeout: 255 seconds]
<pca006132>
how large is the thread and the hole?
<pca006132>
if you are doing 3D printing, did you leave enough tolerance?
<pca006132>
or are you talking about thread pitch?
mmu_man has joined #openscad
<Bambukah>
pca006132, I tried to copy the M16 thread. I don't do anything about tolerance, how can i add it with BOSL2 ? Do'nt know what is the best thread pitch for this diameter (I'm a real beginner)
<J24k54>
but adding the option for a command string shouldn't be too hard - not sure about security if we start external programs
Bambukah has quit [Quit: Connection closed]
Bambukah has joined #openscad
pca006132 has quit [Remote host closed the connection]
pca006132 has joined #openscad
mmu_man has quit [Ping timeout: 255 seconds]
mmu_man has joined #openscad
Bambukah has quit [Quit: Connection closed]
J24k54 has quit [Quit: Client closed]
J24k54 has joined #openscad
califax has quit [Remote host closed the connection]
califax has joined #openscad
erectus has quit [Remote host closed the connection]
erectus has joined #openscad
cart_ has joined #openscad
snaked has quit [Quit: Leaving]
TheAssassin has quit [Quit: No Ping reply in 180 seconds.]
TheAssassin has joined #openscad
dostoyevsky2 has quit [Quit: leaving]
dostoyevsky2 has joined #openscad
TheAssassin has quit [Remote host closed the connection]
TheAssassin has joined #openscad
califax has quit [Ping timeout: 255 seconds]
TheAssassin has quit [Remote host closed the connection]
TheAssassin has joined #openscad
califax has joined #openscad
califax has quit [Remote host closed the connection]
TheAssassin has quit [Remote host closed the connection]
TheAssassin has joined #openscad
califax has joined #openscad
cart_ has quit [Ping timeout: 240 seconds]
cart_ has joined #openscad
califax has quit [Remote host closed the connection]
califax has joined #openscad
snaked has joined #openscad
snaked has quit [Remote host closed the connection]
snaked has joined #openscad
snaked has quit [Client Quit]
pca006133 has joined #openscad
pca006132 has quit [Ping timeout: 264 seconds]
pca006133 is now known as pca006132
califax has quit [Remote host closed the connection]
califax has joined #openscad
pca006132 has quit [Remote host closed the connection]
califax has quit [Remote host closed the connection]
pca006132 has joined #openscad
califax has joined #openscad
califax has quit [Ping timeout: 255 seconds]
califax has joined #openscad
guso78k has joined #openscad
arebil has quit [Quit: arebil]
califax has quit [Remote host closed the connection]
califax has joined #openscad
califax has quit [Remote host closed the connection]
califax has joined #openscad
aiyion2 has quit [Ping timeout: 255 seconds]
aiyion2 has joined #openscad
<guso78k>
I believe, that there could be an issue with the Reindexer class used in OpenSCAD. Points which are at the same coorindate are probably just off by a tiny bit and still not recognized as the SAME point for the Reindexer.
<guso78k>
This could lead to many situations where openSCAD thinks that surfaces are not closed whereas they actually are.(should be)
TheAssassin has quit [Ping timeout: 255 seconds]
TheAssassin has joined #openscad
J24k54 has quit [Quit: Client closed]
J24k54 has joined #openscad
califax has quit [Remote host closed the connection]
guso78k has quit [Ping timeout: 250 seconds]
califax has joined #openscad
kintel has joined #openscad
califax has quit [Remote host closed the connection]
TheAssassin has quit [Remote host closed the connection]
califax has quit [Remote host closed the connection]
TheAssassin has joined #openscad
califax has joined #openscad
<pca006132>
no, I think the real problem is collapsing vertices that should not be collapsed... although reindexer is not to blame because its only function is to collapse vertices...
<kintel>
quantization otoh, is a good candidate
<kintel>
I want to see if we can kill quantization, at least when using Manifold, since Manifold already solves those problems
<pca006132>
I think if you don't reindex the vertices, quantization doesn't change the topology?
<pca006132>
and will not cause mesh not closed issue
<pca006132>
it can only make things self-intersecting, at most
<kintel>
it can join two separate objects into a non-manifold one
<kintel>
I cannot remember what the "mesh not closed" checks actually do : /
<pca006132>
it is the self-intersecting problem
<pca006132>
in that case
<pca006132>
mesh not closed is independent of coordinates, just a topology thing
cart_ has quit [Ping timeout: 240 seconds]
cart_ has joined #openscad
califax has quit [Remote host closed the connection]
<guso78>
Kintel i have Seen equal Displayed vertices getting two different Indices with reindexer. When writing my own ineffective Code wothz tolerante 1e-6 Problem appears solved
califax has joined #openscad
cart_ has quit [Ping timeout: 256 seconds]
<guso78>
I cannot find the tolerance Used in reindexer. How much IS IT?
<kintel>
zero :)
<kintel>
If the vertices are displayed equal, my guess it's a display issue
califax has quit [Remote host closed the connection]
<guso78>
If two Points are Just Off bis Tony 1e-9, their Hash IS different and they can never be Matches.
<guso78>
Quantisation does Not Help Here either because Inspektor random will find the Edge cases and will yield hard to find Errors.
califax has joined #openscad
pca006132 has quit [Read error: Connection reset by peer]
pca006132 has joined #openscad
<kintel>
guso78 I would expect the hash to not have collision on very similar numbers. Do you have any indication that this is actually happening?
hyvoid has quit [Quit: WeeChat 4.2.1]
<kintel>
guso78 Perhaps if you backtrack and describe what you're trying to solve, it will be easier to understand :)
<guso78>
Kintel i think i create a Testcase for you later
califax has quit [Remote host closed the connection]
califax has joined #openscad
califax has quit [Remote host closed the connection]
<guso78k>
here is a simple testcase which shows, that reindexer creates another index when input is just 1e-9 off in one coorindate
<guso78k>
the result will not be manifold anymore, the surface is not closed, the triangles dont have any opposite. various algorithm will fail
<guso78k>
an alternative to use a hash mapping would be to search for points which are near the searched point within a search 3d sphere radius, which can be smaller than 1e-6
<guso78k>
this can be done very effectively when not storing the points in a list, but in a binary tree(actually octant tree) as the tree is split into 2^3 subtrees for 3 dimensions)
<pca006132>
ah, so you are having a triangular soup where coordinates do not match exactly
<pca006132>
not sure why you will have that as input
<guso78k>
yes, exactly, this can happen very easily
<guso78k>
the points could be the result of 3 planes cutting each other but the order of the planes is changed in the 2nd case e.g.
<pca006132>
is this mesh import?
<pca006132>
i.e., how can you have this triangular mesh as input into openscad?
<guso78k>
nope. i coded nef intersection myself and each plane has a polygon on it.
<pca006132>
ah
<pca006132>
maybe try not to use the reindexer?
<guso78k>
however the points on adjacent polygons do not match exactly
<guso78k>
I feel the reindexer is a important member of openscad, but it should be better
<pca006132>
the problem is that I don't think reindexer is supposed to support this
<pca006132>
feels like an issue of your nef implementation rather than a general problem that needs to be addressed
<pca006132>
in general we should probably avoid using the reindexer
<pca006132>
e.g. for stl we use mesh repair from CGAL
<pca006132>
otherwise we just avoid triangle soup
<guso78k>
i believe such errors can happen in many places, not only in nef
<guso78k>
i feel this is a weakness of the reindexer and i believe it should be improved as it can yield problems in other scenarious, too
teepee_ has joined #openscad
<guso78k>
i will definitely need the "improved" reindexer in my algorithm. i was just wondering if you feel it should be used more globally XD
teepee has quit [Ping timeout: 255 seconds]
teepee_ is now known as teepee
teepee has quit [Remote host closed the connection]
<pca006132>
why there are many places that can have this problem?
teepee has joined #openscad
<guso78k>
i suspect, but can browse the code and maybe give you reasonable examples ...
<pca006132>
it is used in the polyset builder, hull, and polyset construction from CGAL nef polyhedon
<pca006132>
and after tessellation
<pca006132>
if we switch to the triangulator in manifold, we don't need this reindexing after tessellation
<guso78k>
yep, i also realized
<pca006132>
for hull, I have no idea why we need the reindexer...
<guso78k>
after all the reindexer is not implementing what I thought, it does ... so I cannot use it for my purposes
<pca006132>
for polyset builder, we should look into ways of keeping manifoldness, or try to fix the triangle soup with CGAL, and retire the polyset builder
<pca006132>
and I have no idea about nef polyhedron thing, maybe reindexer is still needed in that backend
<pca006132>
so you probably want something else instead of the reindexer... I think we should slowly remove reindexer if possible
<guso78k>
when reading in ascii stl you cannot rely on the exporting program to code thousand as 1000 or 1.000E3 which might end up in different binary double codes ....
<guso78k>
as long as you cannot ban STL from openscad , you will not get rid of the reindexer ...
<pca006132>
the problem is that the reindexer will not magically make STL a manifold