![]() After 7 years, Rhino is a gray program for me unless adding solid colors that don’t need variations. That can’t be right, or if it is, it’s pretty stupid? It’s why I almost never do color/texture modeling. Of course I end up with 10-12 versions of the same material in the material palette. The last time I pointed that out someone (NOT McNeel crew) felt insulting my tech ignorance would help.Īnyhoo, I have been able to add texture to models making duplicates of a material and setting scale and rotation, then assigning to individual surfaces. Same with other mind twisters like G0, G2, etc, (I do kinda understand those) WTF is a Brep? I get that Rhino is really an art to math convertor, but for me it’s weak in helping those of us not from the math side of that equation. I don’t speak the language and everything about the lexicon is the opposite of what is obvious in my pencil/marker/paint world. I get this warning “Some of the assigned material are using WCS/OCS or WCS (Box-style) blah blah blah…” I already glazed over. This unifies a lot of work that render engines each otherwise would have to do themselves: meshing objects, handle block instance hierarchies, worksessions, and so on. It probably has to do with how I assign materials or some such. For rendering solutions we’ve introduced the ChangeQueue mechanism in Rhino 6.
0 Comments
Leave a Reply. |