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.

different mechanism to pull out render results.

rhino-specific image/environment mappings.

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. Let me know if any further instructions are needed.I am currently working on updating our Cycles codebase to the 2020.09.10 version that is in the Cycles standalone repository. This way your V-Ray Render Node license will be activated and you will be able to work with V-Ray in Blender and render.

Note: Please make sure to activate your V-Ray license on the web page - 127.0.0.1:30304Īfter the installation of the V-Ray license server, make sure to open the web page 'localhost:30304' and click on Online licensing>Enable and sign in with your account. You can find more instructions on our documentation web page below: V-Ray Standalone could be downloaded here(your V-Ray Standalone should be 3.x version according to your V-Ray Render Node license):

In order to use V-Ray in Blender you will need to download Blender with included V-Ray addon,V-Ray Standalone, and V-Ray license server from the links below:

Vray standalone blender