After installing 3.10.01 I could not get distributed rendering to work.
All assets (bitmaps, Xrefs, proxies) which are on the network are not rendered.
When I open scene on server machine - all is fine, so all pahs are set correctly.
But when I try to use this machine as render server - assets are not rendered.
I also have problems to make DR work with 3.10.01. I have a simple scene that I use to test DR and it worked with that scene, but with my complicated scene, it does not work.
I get “server is not responding” error on my nine servers and only my local compute is rendering.
Can you check the log file on those machines for any clues? We’ve generally done quite a few tests with DR for the release but there’s always a chance that something slipped through. It might also be useful to get a scene that breaks so that we can fix it.
Check what ports your DR slaves are set to use.
They should use 20204 but I had issues with some of the nightly builds that would try to use different port numbers
My system was working fine for long time, distributed render with 3DS Max 2015 Design SP2, VRay 3.10.01, Phoenix FD 2.2.0 Rev 25375 from nightlies. Manually starting VRay DR spawner every time each slave machine is restarted following windows updates, etc. Also registered VRay RT Spawner server on slaves.
Like a fool, I did not check and rushed to installed update for 3DS Max 2015 SP3 to my workstation and all five slaves. Distributed render broke on all slaves. No error messages in logs.
First tried reinstall VRay and Phoenix on all slaves, still failed to respond on distributed render. No error messages in logs, just crash and reset.
On slave 1 which is also my VR license server, went to control panel - view installed updates, uninstalled Max SP3, reinstalled vray, reinstalled Phoenix, reboot, restart VRay DR spawner. Success! now that slave works again.
On other slaves, went to control panel - uninstall programs, click on Autodesk 3ds Max Design 2015, repair or reinstall, select reinstall. Did not fix.
Now trying to uninstall SP3 from other slaves from control panel - view installed updates. Will let you know later if successful.
Are you going to release another patch (3.10.03 ?) in the coming days to address those issues with max 2015 extension 2 ?
Bercause I was about to update max and vray this weekend, but maybe it’s wiser to wait a bit ?
I was thinking the same as theedge. I’m really looking forward to rolling out V-Ray 3 SP1 in the office, but the constant cycle of max patches that cause vray issues is holding me back. Do Autodesk warn you guys that they are changing code that will break 3rd party renderers? Or would that just be wishful thinking? And is there a rough eta on a V-Ray build that will fix the problems introduced by max 2015 EXT2?
It’s unfortunate timing as almost everyone is away for the holidays now; we will release a patch, but it will have to wait until the beginning of January. We can get you an update if you email us to support@chaosgroup.com or if all else fails, to me personally at vlado@chaosgroup.com
So far I have only installed SP3. Have not tried Ext2 yet, which that installer first requires and includes SP3 to install.
Check the autodesk readme for SP3 and Ext2 (link here). Notice the instructions that say 3ds Max will crash after uninstalling SP3 unless you also make changes to or delete Workspace1.se.ini. Don’t know if or how this affected the slaves, but they are working now after uninstalling SP3.
I am having the same issue. I upgraded the farm with SP3 to remedy one issue and it made another. Looks like there is no simple uninstaller for SP3 either. I contacted vray support and they’ve pointed me to sales for some reason. Hopefully whoever answers that can get me the patch even if it is temporary.
joelly3d
I am having the same issue. I upgraded the farm with SP3 to remedy one issue and it made another. Looks like there is no simple uninstaller for SP3 either.
You can go to your Windows Command Panel and uninstall EXT 2. Sp3 is also listed there under installed plugins. It took almost 2 hours to uninstall it on one of my slaves, but afterwards DR worked again.