Although network rendering looks simple and usually just "magically" does it's work, it's quite complex inside. So there are many things that can go wrong here.
One thing you can do to help us understand the problem better is to enable logging on the slave and the master.
For that you have to enable logging for the master, slave and daemon by copying
into the Standalone directory on the master and the slave computer. This file will enable logging for the Standalone as well as the slave into the file
into the Standalone directory on the slave computer. This file will enable logging for the daemon into the file
To make sure that logging really gets enabled (the flag files are only checked during startup), you have to close all Octane stuff. Then launch the daemon, the master, enable net rendering, enable the slave in the net render preferences and then open a simple scene and render it for let's say a few minutes. If the slave didn't render or just very slowly or got killed or crashed, you can close the master, stop the daemon and then either send us the created log files via PM or post them here. There should be 3 log files:
octane_log.txton the master,
octane_log.txton the slave and
octane_daemon_log.txton the slave.
The same way you can enable logging for the Standalone (master), you can do it for the plugin (master) and for the slave. You just have to copy the octane_log_flags.txt file into the directory where the octane.dll is. Make sure that this is in a directory where you have write permissions (otherwise Octane can't write the log files). To kick off logging the application needs to be restarted (because the flags file is only read once in the beginning).
Thanks a lot
Users browsing this forum: Bing [Bot] and 5 guests