I am a recent convert from ACAD3d to RHINO. I loved RHINO up until recently , when I reliazed that it doesn;t handle Boolean operations so well, namely differencing ...
My problem: at some minor level of complexity in the model , boolean differencing fails. I never had such probelms with CAD.
For years I could slice and dice all day with cad's >subtract and >join commands...
ff33, there is a slice command in the main 2 toolbar, depending on your construction plane orientation with respect to the surface you are slicing you can get away with a line/curve as the operand, if youre "out of plane" you need to use a extruded solid that is capped and fully intersected with the object you are trying to cut
I guess you mean split...
and it does work pretty well. so..lemme ask you..aseid...
If you have say a wall mass model for a prototyping ( ultimately an .stl)...
and say you want to cut lots of reveals , some continuous , differing depths, some not ,..and windows holes...
For years in cad , I was modeling with solids and osnap-ing...non orthogonal geometry project have brought me to learn rhino, ..I think the whole compsotion of faces is making me more careful about my approach.
Admittedly, the differencing issue is probably due to some factor of slop.
So I think , I ill go back to CAD for now. Solids are more predictable and stable, then all this surface based modeling
In the (less-than-legal) copy of Rhino I used to use, the boolean functions were reversed, somehow. I can't explain it - if you wanted to join something, it was 'booleandifference', etc.
Rhinoceros only seems unstable if you dont fully understand how to operate the program. Rhinoceros can be your best friend if you know how to use it right.
Dec 14, 07 4:56 pm ·
·
Block this user
Are you sure you want to block this user and hide all related comments throughout the site?
Archinect
This is your first comment on Archinect. Your comment will be visible once approved.
Problems with RHINO :Boolean Differences Failing
I am a recent convert from ACAD3d to RHINO. I loved RHINO up until recently , when I reliazed that it doesn;t handle Boolean operations so well, namely differencing ...
My problem: at some minor level of complexity in the model , boolean differencing fails. I never had such probelms with CAD.
For years I could slice and dice all day with cad's >subtract and >join commands...
Any advice?
use slice
yeah, slice. I use that in my cubicle while my 70 year old boss and I make fun of good work!
well, i agree, >slice is a good command ..in ACAD..in fact
>slice
>join
>subtract always work , and take less time to excute in model space...
no matter what in CAD.
.in Rhino, there is no slice...only boolean commands..and I get failures alot on less-than-platonic shapes.
youre a douchebag sg
Steve,
...look, you made the local rag!
http://www.theonion.com/content/node/38734
ff33, there is a slice command in the main 2 toolbar, depending on your construction plane orientation with respect to the surface you are slicing you can get away with a line/curve as the operand, if youre "out of plane" you need to use a extruded solid that is capped and fully intersected with the object you are trying to cut
takes some getting used to but is really smooth
I guess you mean split...
and it does work pretty well. so..lemme ask you..aseid...
If you have say a wall mass model for a prototyping ( ultimately an .stl)...
and say you want to cut lots of reveals , some continuous , differing depths, some not ,..and windows holes...
how would you approach that problem
just curious...thanks again.
yes split, lol, end of day brain fart
send me a sketch, and ill let you know the best way to do it
gotta catch my train
Union all the "holes" and then subtract then all at once.
sometimes i have to scale 1d up the item to get a proper boolean operation and most of the time it is my fault for not using proper tolerances
yeah...I think the key word there is "tolerances"
For years in cad , I was modeling with solids and osnap-ing...non orthogonal geometry project have brought me to learn rhino, ..I think the whole compsotion of faces is making me more careful about my approach.
Admittedly, the differencing issue is probably due to some factor of slop.
So I think , I ill go back to CAD for now. Solids are more predictable and stable, then all this surface based modeling
In the (less-than-legal) copy of Rhino I used to use, the boolean functions were reversed, somehow. I can't explain it - if you wanted to join something, it was 'booleandifference', etc.
Slice or Trim work in stead of the booleans...
Its Pie
Just draw a cutting line in one of the views (except perspective) and then use the trim command..
Simple....PIE
on this note
just today Rhinoceros 4 gave me message 2x "doubling tolerance to make boolean work" and it worked...
Rhinoceros is 100x more stable and with more power than autocad j
Rhinoceros only seems unstable if you dont fully understand how to operate the program. Rhinoceros can be your best friend if you know how to use it right.
Block this user
Are you sure you want to block this user and hide all related comments throughout the site?
Archinect
This is your first comment on Archinect. Your comment will be visible once approved.