As title would suggest we have a problem with DR slaves locking mid render and refusing to move.. this is constanlty happening now and is becoming a real headache ! again this didnt happen in SP1 ! Thank god for Refamo .. we are able to restart the slave’s and the render carry’s on..
Natty
Is this on any scene or just this particular one? How many (and what kind of) machines are you using for DR?
In our tests here, DR runs fine generally, so we will need to troubleshoot what is causing the issues in your particular case.
Best regards,
Vlado
Hi Vlado,
Random scene’s to be honest, 78 Slaves all quad core max9 sp2.. Gig Lan, this problem has only been aparent in sp2. Its very odd, just a total lock, cpu’s still running @ 100% all cpu’s are monitored
Ok, I may have a clue for this and I will email you later today.
Best regards,
Vlado
same here, I have to rollback to sp1..
some times thay start to render at mid render and then stops there..
I am having a similar problem.
I am using Max Design 2009 and have just installed SP2. When i first render everything seems fine but on the second render the dr nodes seem to hang until the light maps are built then after a while i get messages saying.
“warning: Rendernode host unknown (IP address) is not responding.”
render host (IP Addess) added
Scene transferred to es-5
Server 192.168.1.108: Scene loaded; starting render.
Server 192.168.1.108: Starting frame 0.
Then the dr render starts fine.
The point is that the dr nodes don’t contribute towards the Light maps & the first part of the render.
Hope I am explaining this properly Does anyone have any ideas?
I just noticed that on each render node instead of having vraydummy2009.max on the task bar I have vray_server_scene_2.max then when I get the above message this closes and a new instance seems to start and it starts to render. Obviously it takes time for this to occur so this is taking a lot of time out of the rendering process.
Is vray not getting a message that the previous render is finished?
In summary - It seems to be hanging then rebooting the spawner half way through the render then starting the render.
I am suffering the same problem..
As soon as i change anything in the scene the render doesnt match, it hangs on to the previus scene.
If i restart my renderslaves everything works great.
Im sending the renderjobs from an dual quad-core 64bit machine to two dual-quad slaves.
We are now in a state where we dont really know what workflow we should have now.
We dont want vray sp2, or rather, we want a working sp2.
So then we’re back to working with max 2008 and sp1 but i never want to touch 2008 again, so its max 9 and sp1…
We was hoping for a working combination of max 2009 and vray sp2..
Well unfortunately I can’t roll back as i am working with someone elses files created using max 2008 and I don’t have 2008. (I’m a new 3dsMax convert from Viz). All our workstations are 32bit and all render nodes are started manually. I’m just going to have to work through it unless Vlado comes up with some suggestions/resolutions
same problem here as Yohan, I need to restart the spawner for every render.
both machines are max 2009 64bit and 1.5 SP2
In previous versions I think this was to do with the increment on save option in max, but I don’t have that checked.
Anyone with these issues willing to send a scene with these problems over to vlado@chaosgroup.com for investigation and test a potential fix for this? The scenes we tested here were fine, so it seems to me that this is relating to something specific in your scenes (the existing 3ds Max copy started by the spawner will only close if 3ds Max chooses to crash at some point).
Best regards,
Vlado
thanks vlado!
email sent. from peter@peterguthrie.net
Hi, Did you ever find any resolution to this problem as I am having continuing issues particularly with files created in earlier versions.
Problem seems to be solved for natty, but I had to compile a new build for him. I still want to take a more careful look at this and make sure that the issue is indeed resolved.
Best regards,
Vlado
Hi Vlado,
We still seem to have a sporadic problem with DR locking some machines, which is still causing a problem, this problem will not happen every render and not on the same slaves, seems to be totaly random, when this happens, if we restart the locked machine / machines so they reboot (still in mid render) these machines will then render the locked buckets.
Its odd because this problem was not in sp1 or before, can you not port the code back to those builds or is a Licensing problem?
I have just resolved the current scene by merging it into a new scene and reapplying the render settings. Seems to have worked for this time.
When the render finishes & I have a minute i’ll zip up the before and after and email them to you (Vlado) hopefully it might help you work out whats going on.
This is precisely what I did; the DR code was 1:1 what was for SP1 for the build that I sent you.
or is a Licensing problem?Nope, if V-Ray cannot obtain a license it will not render at all; it will not look for the license again until the render is finished.
Best regards,
Vlado
Any forth coming patch for Sp2?
Once we are sure the issue is resolved, yes.
Best regards,
Vlado