boolean operations

[enri]

regarding plugins for rhino for boleane, there is power solids/booleans, but apparently it goes only on rhino 3, because they no longer updated, if ever informed.
on the graphics card I read that the pictures, not having the drivers specific to rhino, (at least I think, to this page There seems to be a driver, but I don't think it's rhino-related tightmete) go as the corresponding desktops, the fastest currently the gtx 295 geforce, and cost a fraction of the picture.
Then I think about operations is more than a matter of ram, and 64-bit system, and it is always advisable to convert solids to surfaces, without dragging behind the result of various boleanes, correct me if I'm wrong. . : )

 

[teovisi]

the goods are given by mother cio'

 

[teovisi]

Sometimes boolean fails. God damn it. You have to say. This is due: 1 for the non-perfect closure of polysurfaces. 2 above all, with so many stones, I am swallowed. try to put cylinders instead of subtracting the conical shape of the stones. so many times it can be that to carry out subterracings with solids "not simple" (such as the ass of the conical shaped stone) entails much more work of calculation for the program. use a cylinder by orienting it together with the stone into the surface of the object you will have to cash in. then the mixer with the cutters (acades) if we can make it fits great. therefore do not subtract the conical form. Try it later you'll tell me how it goes. Hola

 

[teovisi]

after you have to say that rhino is not at all valid for boolean

 

[Delysid]

There's some confusion, but I'll be brief.

to perform Boolean subtractions also use magics before prototyping, rhino does so many things, knowing how to do well some involves to make it hurt others. It is not the task of rhino to work on solids.
However if you need to put the view in wireframe if you do not have a video card at height (at that point the work is only of the cpu, if you want more performance changes cpu, sanza give account to the number of cores) and eye to the tangences, to degenerate surfaces (the cloud surface is always and only 4 sides) and to the quality of the surfaces in general... it is not enough that the objects are solid closed. it also tries to use the least possible surface, in order to avoid falling into unwanted and unnecessary tangences. uses work tolerances more suitable for the size of the pieces than models. avoids as much trimmed surfaces as possible.

rhino's only fault is to be written on a programming language not at the height, so the memory management is exosa.
regarding the amount of ram 3 gb are fine. rhino is 32-bit and having more rams or 64-bit windows does not involve any benefit. the ram limit that then windows can manage by process is about 1.3 gb, check the task manager to predict in advance the closure of the application.

relative to the software for cashing there is matrix, which is a customized version of rhino just for the goldsmith sector... sold at high price and with a business policy towards the alleged and unflexible customers. . but I heard that the software does what it promises.

otherwise there is a plug-in for more advanced array management on surfaces.