After a couple of days of trouble free dr rendering my nodes are now ‘giving up’ rendering and just sitting there doing nothing.
On two of my machines they can be encouraged to render again by killing the spawner and max process’ and running the spawner service again. This seems to work ok for a few buckets and then it drops out again.
The other machine refuses to join in again once it’s dropped out.
I’m also getting sporadic loss of licence when starting max.
Yeah, I’m getting the same problem and haven’t been able to solve it.
I had a few other things happen but Vlado was able to help with those, but I’m sitting here with a perfectly good machine doing nothing because I cannot get it to recognise the other machines over the network.
I have noticed over the past two or three weeks that there are more people reporting the same problem and would appreciate if the guys at Chaos would have another look at it as I am sure they have looked at it already.
..well, I turned all the machines off for 6hrs last night, tried it again this morning and all seems ok.
The only difference from what I was doing yesterday was that I was accessing the internet on one of my machines while DR’ing. Didn’t do that this morning, so I wonder if that’s got something to do with it? I’ll try DR while browsing the internet a bit later and let you know what happens…
We too are having the same issue with our rendering farm. We have an animation and we are trying to calculate the IR Map using DR but what happens is that the IRmap starts it’s calculation and then after the second frame the nodes drop off at sit idle. What are we doing wrong.? Can the Irmap be calculated using DR? Is there a way to calculate the IRmap with multiple computers?
Spawners giving up for no reason and sitting idle.
Again, some will re-start for a while, others just refuse to join in again.
c:\vraylog.txt.server.txt file on one of my machines has data from july2007!.. so I guess that won’t be relevant…
I’m no where near hitting max ram on these scenes.
Renders are 3000pixels wide. Smaller renders don’t seem to be affected.
Irradiance map gets calc’d ok.
Usually after 25% of image has been rendered spawners start dropping like flies.
The only way I’ve found to combat this so far is to calc the ir map and then save it. Distribute the ir map to all the machines, then render from the saved ir map. Spawners seem to like that. I’m guessing this shouldn’t be nesessary though??
I am having similar problems with 1.5 sp1 and 2008. My solution is to run a script I have that kills and restarts the DR spawner on all nodes, and most nodes will rejoin and stay on. Also, if the problem persists, I create a new scene, merge everything, redo the settings, and it usually fixes the problem… for a while.
What’s weird is that the problem only occurs in some files. Its as if there is some particular kind of geometry or object that is causing the nodes to drop off… I need to figure out what it is. I’m fairly certain that the issue is with Max, not Vray.
Cilfton, funny you should say that, i had a file i was testing DR with the other day which i knew rendered fine with max 9 x64, but 2008 wouldn’t touch it until i removed all Vray proxys from the scene.
But I tried the same on another scene and it just still would not render…
Vlado, i’ll get something over to you.
Ok I’ve found the problem, it’s not the proxies, it appear’s to be a car model i use quite abit in my scenes.
The model its self is open within a group, with alot of turbo smooth modifers applied to it, as soon as i convert it to an editable poly/mesh the scenes render fine. If i delete everything except the car and do not convert it, it also renders, strange?!
Vlado, do you want me to send the car model over to test??