<gbruno>
[github] PinkPandaKatie opened issue #4953 (Using --animate: Maximum number of clients reached / Unable to open a connection to the X server. ) https://github.com/openscad/openscad/issues/4953
<teepee>
for separate model parts in openscad, yes, hopefully thaat will happen
fling has quit [Remote host closed the connection]
R2robot has joined #openscad
R2robot has quit [Read error: Connection reset by peer]
R2robot has joined #openscad
J24k40 has joined #openscad
linext has joined #openscad
linext_ has quit [Ping timeout: 260 seconds]
J24k4 has quit [Ping timeout: 250 seconds]
linext has quit [Ping timeout: 255 seconds]
linext has joined #openscad
<J24k40>
linext the thing with stls is that they are never in several pieces - that are smart algorithm that count triangles into one and other volumes.
<guso78k>
teepee, with "Indexed Mode" in place its quite easy to separate it into single pieces. what will be much more difficult is to handle the pieces separately: they won't have a defined order, they can't be assigned to variables, and theres not scad-language based way to write them into separate files.
linext has joined #openscad
<guso78k>
* assuming that the solids are manifold '=D
<teepee>
yes, it's not so much about the actual splitting, prusaslicer can do that just nicely
<guso78k>
cura also has a "plugin" for that ...
<teepee>
but what do you do with: split() impoert(...);
<guso78k>
yeahh, it can have at most one result ...
linext_ has quit [Ping timeout: 260 seconds]
<teepee>
maybe it could have some sort of point filter similar to ID in svg
<guso78k>
you can do: split(n=3) import("mystl.stl")
<guso78k>
but will be very ineffecitve when importing many times
<teepee>
n by what order?
<guso78k>
order is unpredictable. you increase n , until the result becomes empty :')
<guso78k>
i'd love to write: part1, part2, remainder = import("bust.stl").split()
<teepee>
it's still mostly random
<teepee>
so maybe filtering by "return the object that includes point (x,y,z)" might help
<guso78k>
yeah, but can always sort the result by include the point with the lowest z, y and x coordinate. then it will become predicable
<guso78k>
haha: rather return the result where pt(x,y,z) is inside
<teepee>
yes, that's what I meant
<guso78k>
this would actually be straight-forward und usable. just questioning myself it there is 'need' for that
guso78k33 has joined #openscad
guso78k has quit [Ping timeout: 250 seconds]
R2robot has quit [Quit: Pull the lever, Kronk. Wrong leverrrrrrr!]
R2robot has joined #openscad
guso78k33 has quit [Quit: Client closed]
epony has quit [Ping timeout: 264 seconds]
arebil has quit [Quit: arebil]
snaked has joined #openscad
guso78k has joined #openscad
greenbigfrog has quit [Ping timeout: 260 seconds]
greenbigfrog has joined #openscad
lastrodamo has quit [Quit: Leaving]
Guest48 has joined #openscad
J24k40 has quit [Ping timeout: 250 seconds]
Guest48 has quit [Quit: Ping timeout (120 seconds)]