In the past, I had a tendency to use one little square unit to equal one inch when modeling in Rhino. The reason is simple--I have a lousy sense of depth perception, so if I draw everything very carefully to scale, then I can just move things around and trust that the perspective is correct. One unit to one inch seemed like a reasonable enough thing to do.
I've had trouble in the past with the Fillet Edge command, and hadn't put much thought into why. So when I started working on the quickie console table idea, I wanted to take chunks out to represent possible joinery in the wood. Splitting seemed like the obvious thing to do, until I started poking around at commands, and had duh moment that BooleanDifference would be more appropriate.
Only it didn't seem to work for me! No matter how carefully I aligned things! I checked all the possible problems that seemed most obvious, and really had no idea how to get it to work. The idea of splitting and then rebuilding all those surfaces individually sounded tedious and silly.
I stumbled on the answer accidentally while perusing the Rhino forum on R'osity. I don't post there much, and lurk fairly infrequently, but I was skipping through the posts when I saw it mentioned that scale can affect a lot of commands. Well huh. That made a lot of sense, as I thought about the geometry at a high level.
So I decided to retry the console table, from scratch, only much larger. And...what a surprise...both the fillet and boolean operations worked easily. Sheesh. Now I feel silly for having been doing it the hard way all this time!
Dimensions:
36" length
20" deep
32" tall
No comments:
Post a Comment