Is anyone else running into problems here? I’d gotten used to using DR in max9 with both the 1.5 final and the SP1, as it was running rock solid.
Upon switching to max 2008, with VraySP2, i’m having a lot of problems with DR. Mainly that it will hang on the slave machines, and show the buckets from the slave on my master rendering, but they will never finish, and max on the slave machine takes up 0 CPU. leading the render to not even finish.
I haven’t had a chance yet to try out SP1 on 2008 to see if i can narrow down the issue. hopefully can get some idle time on the farm to try that in the next 2 weeks.
Sadly its done the opposite here. and i’m really starting to miss dr test renders >
I think we need some sort of ‘Timeout/max time per bucket’ that we can set as a user where it will ditch that machine and assign the buckets to a different machine.
Is this specific to some machines in the network only or to some scene? Do you have heavy network traffic at this time?
The only situation I can think of for this to happen is when a slave machine completes its bucket, sends the result back to client, but the client never gets it, for whatever reason. The slave has done its job and sits there waiting for more data, and the client is waiting for data that will never come.
so then shouldnt it be programmed then that the client send a confirmation to the slave that it received the data, and if the slave doesn’t get this confirmation in XYZ time, then it sends it again to the client?
So many people are having problems with DR on this forum and it makes me think of a recent thread by somebody ranting about the license that should be easier to install and just work. This is how I feel about DR and I said it before. I think we need a serious programming overall or even rewrite for DR…
On any scene, or on this particular one? For all our tests with DR here it has worked fine generally, so we will need some help from you to troubleshoot these issues.
Well that was damn quick… TO fix this issue, I went to my slave and click “Register Vray spawner service” and went to “Change vray client license settings” and clicked that.
I didn’t change any settings whatsoever, just clicked thru those two apps.
My slave is running 32bit max, my workstation is running 64bit max. I was having problems with my workstation max so I installed 32bit on it to test some scenes out. That is when the problem first arose.
Well, that let me use 1 of the machines out of the 3 that i tried. the other two appear to be hanging up at the Light Cache stage if the vraylog is any indication.
change1: changing the services to log in to the domain so they could see my networked maps
Annnnnd that appears to have worked for me! thanks! the only other thing i saw odd on the machines that weren’t working was in the plugin.ini there was a ;=; above the vrayplugins.
I was having some problems too (Max9 VraySP2)
for some reason I couldn’t get one of my nodes to start rendering…the buckets were just stuck in one position.
I tried restarting the spawner and also rebooting the machines…nothing seemed to work!!!
In the end I found a SOLUTION!!!
Go to the task manager and end all processes that have anything to do with max or vray…restart the spawner…and voila…DR is working again!!!
