Page 1 of 3
OcDS and Network Rendering - what is needed?
Posted: Wed Jun 24, 2015 9:01 am
by birdovous
So I have the standalone and OcDS installed on my main computer and I would like to use my other computer as a network render slave.
Do I need just another standalone license for that node or do I need both standalone and OcDS licenses for the network node?
Re: OcDS and Network Rendering - what is needed?
Posted: Wed Jun 24, 2015 4:17 pm
by bepeg4d
hi,
you need a standalone licence for every slave on your network, no additional plugin licence is needed, and there is a limit of max 12 GPU per master.
ciao beppe
Re: OcDS and Network Rendering - what is needed?
Posted: Mon Aug 17, 2015 1:47 pm
by gaazsi
i bought one more standalone license today, was pretty easy to set it up... now master and slave finding each other... BUT its not showing up in the plugins window. is there some hint that i missed?
there seem to be 2 lines on the bottom... vnc executable path and vnc arguments... i am used to vnc itself, but is it neccessary to set up something in those 2 fields? if yes... what?
Re: OcDS and Network Rendering - what is needed?
Posted: Mon Aug 17, 2015 2:11 pm
by birdovous
gaazsi wrote:i bought one more standalone license today, was pretty easy to set it up... now master and slave finding each other... BUT its not showing up in the plugins window. is there some hint that i missed?
there seem to be 2 lines on the bottom... vnc executable path and vnc arguments... i am used to vnc itself, but is it neccessary to set up something in those 2 fields? if yes... what?
You don't need to fill the VNC related lines. Those come into play only in case you would like to be able to instantly connect to the remote desktop of the slave node using the VNC terminal application/service.
I would say - check your firewall settings on both machines and then check the ports you have set in the plugin and then on the slave node where you need to install the daemon using the OcDS plugin installation package. The slave node rendering daemon then has own simple GUI where you can set the port and few other things.
Problem is that there seems to be some sort of a bug with the network rendering feature of the plugin. I, for instance, after fiddling with it for quite some time was able to make the master and slave to see each other so in the Plugin window the slave was visible and "ON" but the rendered data the slave sends are missing textures and the final render then gets extremely desaturated very quickly, making the output totally unusable.
For example in my case, I have more than one network card in my master PC and until I disable all of them except the one that leads to the slave node I can't use the network rendering feature at all as the slave is visible but in "OFF" state. Problem is that even after I disable all other network cards and the slave switches to the ON state, the render output is broken and not usable anyway.
So at the moment I'm using a workaround where I prepare the scene in DAZ Studio using just my cards in the master node itself and when I'm happy with the setup I use the orbx export feature of the plugin to export entire scene including camera settings and then I just quit DAZ Studio, launch the standalone Octane Render and in there the network rendering works flawlessly so I let the final render run on the standalone (you need to install the standalone network daemon on the slave for that).
Good thing about the workaround is, that the standalone network rendering daemon supports Out of Core textures, which, at the moment, is not an option in the daemon that comes with the OcDS plugin.
Re: OcDS and Network Rendering - what is needed?
Posted: Mon Aug 17, 2015 2:28 pm
by gaazsi
hi
firewalls are set to off on both machines, i was aware of your posts in the beta thread, no worries

also ports are the same and fitting to each other... even in plugin.
i just wondered where you found THIS menu...
if it is the slave daemon installer... for me, it was a simple dos prompt

or is this menu hidden somewhere else?
the funny thing is... when i start daz studio a second time... i get network render errors, that those ports are already used by another program. so it seems to work... but i cant see those frikking render slave in the plugin window
Re: OcDS and Network Rendering - what is needed?
Posted: Mon Aug 17, 2015 2:57 pm
by birdovous
gaazsi wrote:hi
firewalls are set to off on both machines, i was aware of your posts in the beta thread, no worries

also ports are the same and fitting to each other... even in plugin.
i just wondered where you found THIS menu...
if it is the slave daemon installer... for me, it was a simple dos prompt

or is this menu hidden somewhere else?
the funny thing is... when i start daz studio a second time... i get network render errors, that those ports are already used by another program. so it seems to work... but i cant see those frikking render slave in the plugin window
You need to run the Octane Plugin for DAZ installer on the slave and pick that you want to install just the daemon. Then it will install the daemon which is specific to the Plugin (the standalone DOS prompt daemon does not work with the plugin).
Re: OcDS and Network Rendering - what is needed?
Posted: Mon Aug 17, 2015 3:14 pm
by gaazsi
oooh! i guess THAT could be the reason/solution maybe

lets hope the best! just one little problem remaining... if i try to download t_3s link i get the message
Request expired. Email
[email protected] if you continue to see this message.
is there any mirror out there?

Re: OcDS and Network Rendering - what is needed?
Posted: Mon Aug 17, 2015 3:26 pm
by birdovous
Not any I know of. I could upload it to my Dropbox and send you a link if it helps. Or of course you can mail the Otoy admins and wait until Otoy fixes the issue

Re: OcDS and Network Rendering - what is needed?
Posted: Mon Aug 17, 2015 3:35 pm
by gaazsi
then i take the dropbox solution please, thanks for the efforts!

Re: OcDS and Network Rendering - what is needed?
Posted: Mon Aug 17, 2015 3:39 pm
by birdovous
gaazsi wrote:then i take the dropbox solution please, thanks for the efforts!

Check you PMs
