

In this case, two materials were imported: bark.vrmat and leaves.vrmat, both of which are built by adjusting standard V-Ray materials. If you have V-RayMaterial (.vrmat) files available for the object, you can import those, which will add the needed materials to your V-Ray assets.

At this stage they will have generic names built from the proxy file name ("dense-tree Material sub material 0", etc.) and will render some uniform color. Importing the file (using the "Import Proxy" tool in the V-Ray Objects tab) will force these materials into existence if they aren't already defined in the model. In the images here, dense-tree.vrmesh contains two sub-objects (bark and leaf geometry) each with their own material ID. vrmat files used to set material properties. The geometry of the proxy and the material IDs used to render it cannot be changed, but the actual material definitions can be changed. vrmesh file geometry is substituted for the Rhino geometry before rendering. Using the V-Ray "Import Proxy" tool, this file may then be inserted into the model repeatedly. A low-polygon-count "proxy" is created during this process and inserted into the Rhino file in place of the original geometry. In much the same way that procedural geometry such as fur helps with pre-render setup and reduced geometrical complexity, proxies help by storing or caching the render geometry of a complex object in an auxillary file which then replaces the simpler ("proxy") Rhino modeling object at render time.Ī Rhino V-Ray proxy is created by first modeling an object in Rhino and then using the V-Ray "Export Proxy" tool to save the VRay render-mesh geometry to a. TAPESTRY: The Art of Representation and Abstraction Symbols: Proxies
