Blender’s creators have made some useful strides since it’s advent, in that newer versions do not inundate users with controls for functions they won’t use a lot while hiding those for basic shapes, so I no longer get a headache looking at it worse than those Bubsy 3D evokes, but the program still is simply not self-explanatory. It feels much too arbitrary in how so much of it uses keyboard shortcuts instead of prominent buttons. In case you are interested, there are a couple of dev talks from last month on the subject published on Autodesk’s youtube channel close to 1h of content each.I don’t feel Blender is a good program for late learners. I do think it would be good to consider interoperability for shaders, including the use of OSL and Material X, when it is fully deployed in other packages as well.ģds Max’ dev’s are making great strides to implement both. If I may add my 2 cents to this: it seems like a reasonable way to implement materials with a consistent UI, although I can see it being useful to have the materials in a different Grasshopper canvas than Grasshopper itself as to not convolute the canvas with all sorts of things. That said we have of course our existing material descriptions engines use to create their own representations. How useful it is for other rendering engines depends of course on the correspondence of nodes between the different engines. We are thinking of adding node-based materials using an embedded grasshopper canvas. But a 100% exchange between materials is not possible due to the fact that we have some features in our Cycles version that do not exist in Blender.
I hope to be able to improve the import_3dm add-on I created by using Rhino Inside in the near future. This means an exact match between Rhino and Blender is not possible unless all patches are landed in upstream Cycles - which is not very likely to happen for a number of reasons that I won’t go in here.
Our version of Cycles has a number of features that do not exist in upstream Cycles
Lots of changes, including a number of code rewrites that will take a time for me to adapt our patches to. From our previous version that is 330 commits. I am currently working on updating our Cycles codebase to the 2020.09.10 version that is in the Cycles standalone repository.
0 kommentar(er)
