USER FORUM
(you are viewing a thread; or go back to list of threads)
Too mush circles for extrude? (by CodeName33)
Hello everyone, I'm trying to create PC back wall for 3d printing and I need perforation in this wall. So I'm trying to do it with many 3mm circles. Somtehing like this:
OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
But, when circles count become more than 500 my wall paints in red and export errors appears. If I delete some circles in any place all stays good. I'm trying to split circles in different extrude groups but it doesn't helps. Is there some limit for objects count in SolveSpace?
P.S. I'm using lastest version.
OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
But, when circles count become more than 500 my wall paints in red and export errors appears. If I delete some circles in any place all stays good. I'm trying to split circles in different extrude groups but it doesn't helps. Is there some limit for objects count in SolveSpace?
P.S. I'm using lastest version.
(no subject) (by E A)
I am too new at this to be of much help, but if you look at EDIT>Configuration you have some selections regarding piecewise linear segments. One of them is set to export curves as piecewise linear segments.If there is a solution, it lies somewhere in those settings. I suspect that hardware resources would be the limiting factor in maximums for some if not all of the settings. That and computational speed. Some of these experts will have a better idea.
As a thought, though, I wonder if using hexagons rather than circles might at least get you further. Next to the tringle, it is the most efficient shape in nature (IMHO). Draw one, translate to three or five and set your spacing, then increase the number of translations. Then you can copy and paste.
But why not omit the holey grid and specify a material that is already punched. :)
As a thought, though, I wonder if using hexagons rather than circles might at least get you further. Next to the tringle, it is the most efficient shape in nature (IMHO). Draw one, translate to three or five and set your spacing, then increase the number of translations. Then you can copy and paste.
But why not omit the holey grid and specify a material that is already punched. :)
more thoughts (by E A)
You might make a small piece of perforations in a rectangular or hexagonal pattern as a separate file. Lint and translate that file to a larger than needed area, then cut it with an extrusion to be placed into your model.
(no subject) (by Andrew)
I tried assembling from smaller parts, and it runs into the same problem. As far as I can see, this problem is at least in part a memory problem, A program using swap space slows down dramatically, and if no swap, stops because it is out of memory.
(no subject) (by E A)
@Andrew
I may be mistaken, but I think that if you make one part, say a small tile and save it, then link one instance of it, then translate that piece many times, you simply have one set of geometry in the final assembled file--of course in addition to other things you constructed in the file.
Once again, I may well be incorrect due to lack of understanding of the inner workings of the programs engines.
Someone around here has an answer for you, though.
Good Luck!
I may be mistaken, but I think that if you make one part, say a small tile and save it, then link one instance of it, then translate that piece many times, you simply have one set of geometry in the final assembled file--of course in addition to other things you constructed in the file.
Once again, I may well be incorrect due to lack of understanding of the inner workings of the programs engines.
Someone around here has an answer for you, though.
Good Luck!
(no subject) (by CodeName33)
> As far as I can see, this problem is at least in part a memory problem, A program using swap space slows down dramatically, and if no swap, stops because it is out of memory.
I found that program uses about 250mb -300mb RAM and ~100mb video memory on my project. It's very low for memory limit.
Thanks for answers I'll try to find solutions to resolve this problem. For now I found workaround with putting check "force NURBS surfaces to triangle group" but it takes too much time. Exported model looks good but in SolveSpace it appears very strange (screen)
I found that program uses about 250mb -300mb RAM and ~100mb video memory on my project. It's very low for memory limit.
Thanks for answers I'll try to find solutions to resolve this problem. For now I found workaround with putting check "force NURBS surfaces to triangle group" but it takes too much time. Exported model looks good but in SolveSpace it appears very strange (screen)
Post a reply to this comment: