Tweet
DR works in 2009 but not 2010
Hi,
I've read a number of potentially relevant posts in this forum, repeatedly, over several weeks trying to find a solution to get V-Ray 1.50 SP3 DR to work in 3ds Max 2010, to no avail. It works fine in 3ds Max 2009 on the same machine. The XP Pro 32-bit SP3 PC is current with the latest SW versions, patches, OS service packs and updates, etc.
Uninstalled all versions of Backburner, cleaned out registry, and reinstalled BB 2008.1. - Works just fine with 3ds Max 2009; all CPU cores from all render slaves show in the client frame buffer as expected.
Basically, it looks like the V-Ray Spawner on the slave is going to do something at first. The taskbar tab name changes briefly to Untitled, but it's always a false hope. Eventually it seems like the slave has given up for most but not all successive attempts during that session, as the Task Manager CPU usage sits fairly still and the filename doesn't change again in the Taskbar tab, although it sometimes might. Ticking the option in 3ds Max 2010 on the client under V-Ray Distributed Rendering to restart the render slaves has no effect.
Resaved the VRay dummy max file and replaced it on the slaves but nothing changed.
2010 SP1 just released by AD had no effect.
The V-Ray error logs show nothing useful. The job was submitted but there were no errors, other than the obvious issue that no DR buckets were filled by any of the slaves.
Moving out the AutoCam plugin files had no effect.
Setting UNC paths in Asset Tracker had no effect.
Isolated all third party plugins to test for conflict.
Tried running with no firewall or anti-virus but no difference.
Tried a super simple scene with a teapot and a V-Ray light, plus some of the sample V-Ray scenes. None of three identically configured render slaves would provide a single bucket to the VFB at any time. Given the scene simplicity, I don't think this is a memory issue, so the 3GB switch is unlikely to matter. Each PC has 4GB of RAM.
The V-Ray license server status webpage does indeed show that a DR license node is in use at the time that a render slave is supposedly working on the scene, but there is minimal CPU activity on the render slave and no output is returned to the client.
The only errors that possibly might be worth mentioning were in the max.log file on the render slave:
2009/08/01 05:03:45 WRN: Gamma Correction Settings are Being Changed
2009/08/01 05:03:45 ERR: An unexpected exception has occurred in the network renderer and it is terminating.
Can anyone suggest what might cause this last error? It seems to be the only clue I have at this point. I'm just baffled as to why V-Ray DR works in 2009 but not 2010, given the minimal variables between them and especially that Backburner 2008.1 works with both, for both individual frames of an animation and even split renders for a single frame.
If anyone has anything left worth trying, thanks in advance!
I've read a number of potentially relevant posts in this forum, repeatedly, over several weeks trying to find a solution to get V-Ray 1.50 SP3 DR to work in 3ds Max 2010, to no avail. It works fine in 3ds Max 2009 on the same machine. The XP Pro 32-bit SP3 PC is current with the latest SW versions, patches, OS service packs and updates, etc.
Uninstalled all versions of Backburner, cleaned out registry, and reinstalled BB 2008.1. - Works just fine with 3ds Max 2009; all CPU cores from all render slaves show in the client frame buffer as expected.
Basically, it looks like the V-Ray Spawner on the slave is going to do something at first. The taskbar tab name changes briefly to Untitled, but it's always a false hope. Eventually it seems like the slave has given up for most but not all successive attempts during that session, as the Task Manager CPU usage sits fairly still and the filename doesn't change again in the Taskbar tab, although it sometimes might. Ticking the option in 3ds Max 2010 on the client under V-Ray Distributed Rendering to restart the render slaves has no effect.
Resaved the VRay dummy max file and replaced it on the slaves but nothing changed.
2010 SP1 just released by AD had no effect.
The V-Ray error logs show nothing useful. The job was submitted but there were no errors, other than the obvious issue that no DR buckets were filled by any of the slaves.
Moving out the AutoCam plugin files had no effect.
Setting UNC paths in Asset Tracker had no effect.
Isolated all third party plugins to test for conflict.
Tried running with no firewall or anti-virus but no difference.
Tried a super simple scene with a teapot and a V-Ray light, plus some of the sample V-Ray scenes. None of three identically configured render slaves would provide a single bucket to the VFB at any time. Given the scene simplicity, I don't think this is a memory issue, so the 3GB switch is unlikely to matter. Each PC has 4GB of RAM.
The V-Ray license server status webpage does indeed show that a DR license node is in use at the time that a render slave is supposedly working on the scene, but there is minimal CPU activity on the render slave and no output is returned to the client.
The only errors that possibly might be worth mentioning were in the max.log file on the render slave:
2009/08/01 05:03:45 WRN: Gamma Correction Settings are Being Changed
2009/08/01 05:03:45 ERR: An unexpected exception has occurred in the network renderer and it is terminating.
Can anyone suggest what might cause this last error? It seems to be the only clue I have at this point. I'm just baffled as to why V-Ray DR works in 2009 but not 2010, given the minimal variables between them and especially that Backburner 2008.1 works with both, for both individual frames of an animation and even split renders for a single frame.
If anyone has anything left worth trying, thanks in advance!
Comment