FAQ
Whatever you create with Rhino Nature can be rendered by any render engine. To do that you simply need to bake selected ecosystems into the document and make the RN::Export layer visible. By default on the first bake, this layer is set to be hidden to prevent performance issues due to high object counts being placed at once in the scene.
Some render engines take advantage of direct integration with Rhino Nature allowing their users to get the most out of both worlds, allowing seamless workflow without any additional manual operations, saving huge amounts of RAM and disk space making your work better and quicker.
Every distribution by default follows a normal of the provided domains. In some cases, Rhino can create a surface that looks like every other usual surface, with one difference - its normal is flipped. To change that simply select this object, run
_Dir command and flip its normal to the desired state.Whenever you add an entity Rhino Nature is checking the type of picked geometry. In case when regular geometry is provided (extrusion, polysurface, mesh, etc.) it will encapsulate picked geometry into a block behind the scenes. In case when a block is provided it will reuse this block. To change entity geometry or its properties you have to edit the corresponding block. In some circumstances, it may be not present in your scene and you will need first run
_Insert command, place it in the scene, and then edit.In some circumstances, it may take much more time to calculate than actually needed. This happens most likely to new users who often forget about optimization like keeping distribution origin near the average center point of used domains or when a very small distance value is used along with enabled collision detection. Such a setup may be very inefficient as Rhino Nature may create millions of objects and discard most of them. It is very easy to diagnose and fix such things using statistics as a guide.
Last modified 1yr ago