USER FORUM
(you are viewing a thread; or go back to list of threads)
Bugs (by Andrew)
While playing with printablocks, I ran into a solver bug. in the attached file, the solver goes wrong if the number of repeats in the second lost translate is 8,15 or 16. This may help find the bug.
The slightly funny directory structure is due to another bug. When setting up the files to create the zip, with both files in the same directory, it couldn't find the .stl, and when it opened the file dialogue, it was set to look for .slvs, so the required file could not be found. It would be useful if this was fixed.
The slightly funny directory structure is due to another bug. When setting up the files to create the zip, with both files in the same directory, it couldn't find the .stl, and when it opened the file dialogue, it was set to look for .slvs, so the required file could not be found. It would be useful if this was fixed.
(no subject) (by ruevs)
Do you mean the naked edges and missing polygons (one can see the red inside through them)? The ones that are visualized when doing "Analyze | Show Naked Edges"?
It is not a solver problem, but (most probably) a triangle mesh intersection problem. Or a problem with the triangulation itself.
Since "000a_connectorneg_flat.stl" is a triangle mesh the whole model is forced to triangle mesh mode (this is normal) and the difference operations are also done on triangle meshes (instead of NURBS surfaces).
It is not a solver problem, but (most probably) a triangle mesh intersection problem. Or a problem with the triangulation itself.
Since "000a_connectorneg_flat.stl" is a triangle mesh the whole model is forced to triangle mesh mode (this is normal) and the difference operations are also done on triangle meshes (instead of NURBS surfaces).
(no subject) (by Andrew)
Whatever is going wrong, it is dependent of the number of instances in the indicated translate group. Interestingly, using 12 instances in that group, and then adding the rest of the required connectors by another pair of translates got a usable model, . I did get warning on export of the STL, but nothing that the slicer couldn't fix.
I suspect that something is going wrong in the working structures used to build the mesh.
I suspect that something is going wrong in the working structures used to build the mesh.
(no subject) (by Paul)
>> ... and when it opened the file dialogue, it was set to look for .slvs, so the required file could not be found
That has been fixed. It currently defaults to .slvs .emn .stl file types when linking. This will be in the next version.
Like ruevs says, the big problem here seems to be a triangle-mesh boolean issue. Unfortunately I don't think those will be addressed for a long time due to lack of resources.
That has been fixed. It currently defaults to .slvs .emn .stl file types when linking. This will be in the next version.
Like ruevs says, the big problem here seems to be a triangle-mesh boolean issue. Unfortunately I don't think those will be addressed for a long time due to lack of resources.
Post a reply to this comment: