Page 1 of 1
netrendering - subnet scan range cannot be set
Posted: Wed Jul 09, 2014 4:19 pm
by a3d
if the slave adress is too high, the renderslave won´t show up.
it shows up in standalone, (in my case x.x.x.0-x.x.x.254) but not in max (x.x.x.0-x.x.x.24).
Re: netrendering - subnet scan range cannot be set
Posted: Wed Jul 09, 2014 9:33 pm
by abstrax
a3d wrote:if the slave adress is too high, the renderslave won´t show up.
it shows up in standalone, (in my case x.x.x.0-x.x.x.254) but not in max (x.x.x.0-x.x.x.24).
3ds max uses the same code and UI as standalone so if it works in the standalone, it should also work in the plugin.
One important fact to remember is that the master port can be used by
only 1 process so if the standalone is running with network rendering enabled the standalone process is occupying the socket and the plugin can't use it and the daemons won't show up either.
-> Make sure that only one Octane process at a time has network rendering enabled.
Re: netrendering - subnet scan range cannot be set
Posted: Fri Jul 11, 2014 9:23 am
by a3d
unfortunately it is not as you say with my installation,
guis differ.
max version:
https://www.dropbox.com/s/9sex7yr9vceq2e3/max-gui.jpg, slave not found
standalone version:
https://www.dropbox.com/s/95dliu99zte4a ... ne-gui.jpg, slave found
as you can see, there is not way to set the scan range in the max version.
slave-ip is out of scanrange for the max version and therefore not found.
it just that it 24 instead of 254 that causes the trouble.
