Help with Network Render Slave Machine...

Sat Aug 01, 2015 10:06 pm

...and rebooting didn't change anything. Clearly I am missing something here...

Sat Aug 01, 2015 10:09 pm

Man... That is frustrating.
At this moment the sun rises in New Zealand, so hopefull someone takes a look on your thread om sunday and helps you out.

Might try an older version of Octane, but that would be a hopeless try.
I have the same version as you working.

To be sure, I am asking again... Did you try enable your firewall, ans allow the in and outgoing of Octane in the firewall settings... and when trying to make connection with daemon hopefully the firewall will ask your permission for outgoing?
(That was in my case the last thing I did after having the other thing correct)

I cannot think of anything anymore.
Anyway, good luck and hopefully you get more help from other.

Greetz

Sat Aug 01, 2015 10:12 pm

Thanks for all of your help, rappert. the whole firewall thing is a bit of a mystery to me. I disabled the firewall on both machines, and I thought that should be enough? I am not sure what you mean about "in and out settings" though. I will dig around and see what I can find out about that.

Sat Aug 01, 2015 10:18 pm

Last thing: the whole time you were testing fom standalone and not on master with plugin?
(I had that and having plugin running older version)

Sat Aug 01, 2015 10:56 pm

I have been testing with both. I believe that my plug in version is also current.

Just to add to the mystery: In Octane Standalone, I now see the following message in the status bar next to OctaneLive: connected

"Using 3/3 GPUs of 1 slaves"

That has not been there previously. That said, my preferences window does not show anything at all listed in the Network Rendering list... unfortunately, my plug in still shows no other gpus available.

Sat Aug 01, 2015 11:24 pm

OK, the plug in still doesn't see the slave at all, and even though Standalone said it saw the slave, as soon as I loaded the scene directly into the plug in, the message changed to "using 0/3 slaves", and when I activated the prefs again, the message went away completely...

Sun Aug 02, 2015 2:21 am

That is cool... it works, but not stable

On slave you can kill the daemon with Ctrl-C and start daemon again
Are you trying with small scene?
When having 0/3 connection is there, but might be laoding
Is Vram the same on master and slave?

Sun Aug 02, 2015 2:23 am

jayroth wrote:OK, the plug in still doesn't see the slave at all, and even though Standalone said it saw the slave, as soon as I loaded the scene directly into the plug in, the message changed to "using 0/3 slaves", and when I activated the prefs again, the message went away completely...

Did 0/3 occur on the plugin or on the standalone?
Are you running both at the same time?

Make sure the plugin version is written against the same standalone version!

Sun Aug 02, 2015 2:49 am

I'm using the most current version of both. The message disappeared after I ran the live view in Cinema.

Sun Aug 02, 2015 6:54 pm

I have relocated my my work to the render slave machine, so at least I can run projects through it now. But that means I bought the extra Octane Standalone license for nothing. I'm not happy about this at all, and I may seek a refund on that license if I can't get this to work soon. I am going to submit a tech support request later today. Hopefully we can resolve the issue in a couple of days, but I won't have as much time to dedicate to a solution as I did up to this point.