The OctaneRender network render slave is fairly dumb and all the render data processing is actually done on the Primary Render Node side. If that does not help, also try switching off the firewall on the slave computer for home/work networks. This can be done, for example, by turning off the firewall for home/work networks on the Primary Render Node. Also ensure that the Primary Render Node and the slave are not blocked by the Operating System firewall or any firewalls in the network. It is best to copy the whole folder of the released archive onto the slave computer. Since an OctaneRender slave currently requires an activated Standalone license, it is advisable to run the Standalone first to activate a Standalone license on that computer, if necessary. The OctaneRender instance that drives the rendering is referred as the “ Primary Render Node ” and the OctaneRender instances that are helping are referred as the rendering “ Render Nodes”. Network rendering requires a Primary Render Node and one or more Render Nodes on different computers. Conceptually it is similar to working with additional GPUs by allowing the distributed rendering of single images over multiple computers connected through a fast local area network. OctaneRender distributes compiled render data and not scene data, so no file management is required by the user. Network rendering allows additional GPUs in other computers to be utilized in rendering images. For today’s article, let’s go with iRenderto find out how to set up Network Rendering on Octane for Blender as well as Octane’s Network Rendering feature.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |