I’ll qualify this with my enthusiasm for Rhino in general.
However, I find this application is often a little bitch.
I expect design applicaions to help me design. I don’t expect to be making sure the application is happy. Surely there’s some means to allow for what’s crudley known as error correction so one does not have to inspect literally every single step.
In this instance, since I’ve been advised repeatedly to avoid the boolean function - being told it’s somehow a second rate solution to creating. Even though the intersections required for the operation were created by the tirm tool using the exact same object they’re somehow not suitable a few steps later.
I’ve exploded an object and went through the tedium of trimming and joining back together about 32 seperate surfaces. But there’s one - there’s always at least one, that will not be split or be trimmed as apparently it’s no longer tangent or whatever friggin condition it was in previously. Instead I get “Split failed, objects may not intersect or intersections may not split object.”
Really?? This is utterly silly. WTF!!!
In this instance, a surface must be trimmed or split in order to make a proper join. However the surface that was use to split other surfaces will not work on this last one.
My point is this: There’s seldom if ever an instance of failure that cannot be attributed to the user. But so what? I don’t use applicaions to keep myself up on technique. The application must facilitate the precision it requires. Otherwise it’s like fitting a biycycle with a jet engine.
Yes. the coding is grand, and the possibiltes endless, but what of pracitcal ease of use?
I’m exasperated with how easily this application runs off the rails.
Why does everyone keep talking about the boolean’s difficult task? As in " -you’re expecting the boolean to …"
Well, yeah, that’s exactly what I’m expecting. Why did anyone bother to make such a command set if it’s so consitently overtaxed?
Nobody involved in design and production is interested in making a tool or a progam look good. It’s a friggin bit of code - an inanimate concept. For fuck’s sake, make it better and quit giving me excuses for it, or blaming me for the .001mm bit of error I managed to make using your program.
Maybe this trouble will all fade away in time, but at this point - and you do solicit criticism, I find aspects of Rhino utterly assinine.