There a lot of threads about DR with Max 2009 and Vray. Does it work or not?
I´m using winxp64, max2009 and vray sp2. Backburner works fine.
When i open the vrayspawner at the slave-machine the vraydummy starts and goes down into the task-bar.
When i start the rendering - vraylog says connectet to host (name of the slave) with ip.
- everything seems fine but not more buckets and after 2 minutes it says
Warning: renderhost …(ip) is not responding.
same problem with 3ds max 2009. Any help here would be appreciated. Everything was working fine with Viz 2008, and now ‘render host not responding’ with 3ds max 2009. Here’s our setup:
Installed fresh 3ds max design 2009 and Vray 1.5 SP2 on render machine and nodes.
Start vray spawner on render node and get the minimized vraydummy file in the taskbar (cool looks like it’s going to work smoother than viz did for us
Start the render from the render computer
the vray messages window says render host xxxxxxx added
no extra buckets show up in the rendering window
then the vray messages windows says 'render host unknown xxxxxxx is not responding.
then this cycles over and over about every 5 minutes.
See the attached image for details. Running Windows XP SP3 32bit on every machine.
We’re running on 5 vray licenses and we’ve got a 20 computer render farm we’re looking to get set up as soon as possible. Our production is slowing due to this problem and any help is much appreciated
M-
PS no firewalls or switch problems. Seeing as how DR worked fine yesterday with all of our Viz2008 setups, I’m thinking this is not a networking problem.
PS2 - about the task manage on the slave machine - when the render is sent to the slave machine, there is about a 25% processor spike, with no change in RAM allocation, then it dies down and nothing, until the main render machine tries to send it again…then another spike…repeat.
not exactly, I was suggesting that solution if you’re having trouble connecting to the other hosts ‘at all’. As for the random dropouts, I’m not sure what’s up there. I haven’t run across that problem yet = fingers crossed…