Rhino Materials
Rhino materials are in need of serious improvement. Here are my main points:
-
Lack of a Native Node-Based Material Editor:
Rhino currently lacks a native node-based material editor. Since Rhino already includes Grasshopper, implementing such a system for materials should be feasible. Even if this functionality were integrated within Grasshopper, it would be a welcome addition. This integration would focus on enabling complex and procedural material creation—without necessarily requiring deep coding with languages like C# or Python. -
Advanced Material Generation:
A native node-based editor could enable advanced material generation by leveraging engine-based procedural maps, Rhino maps, or transforming maps. This would simplify material creation and transform the complex, maze-like wrapping and nesting in the current UI into a more navigable workflow. -
Substance Designer and Other Material Creation Apps Like It:
While Substance Designer demonstrates a powerful node-based workflow for procedural textures and dynamic material variations, merely exporting maps as PBR textures in Rhino results in lost functionality. This approach diminishes the ability to achieve infinitely tileable materials that effectively hide repetitions, by varying each tile. and many more like increasing the feedback loop and reducing user’s ability to mix rhino and other render engines maps.