Vray DR server 'busy' message

[Penry]

Hi guys,

This is a new one to me but I am sure it has been covered in the forum somewhere before...!
I open a scene in max with everything set up as normal and hit render with vray DR activated and all is good! If I try and do exactly the same thing again I get the attached message. If I check on the server the vray dummy has changed to vray server scene.max and I can't use DR. I can close this programme and restart the vray dummy server on the render slave and once again all is good, but for one render only then I get the 'busy' message again. This has only started since I installed some more memory this afternoon....could this have caused the problem? I have restarted both my PC and the render slave but this is still happening.

Your assistance...PLEASE! It's doing my head in!!!!

[Svetlozar Draganov]

This issue usually happens if the new job is submitted before releasing the previous one.
VraySpawner needs some time to prepare itself for the next job which depends on the scene complexity.
Try to give it more time before submitting the next job.

What is the status of Restart Servers On Render End option from DR settings?

[Penry]

There is definately something wrong. I have waited ten minutes before sending a new render via DR and it's still saying 'busy'! I don't have the restart slaves option on, never have, and have never needed to. Think I'll do a full clean install on MAX and Vray. That usually sorts it all out.

Thanks for the response

[Svetlozar Draganov]

Try to activate Restart Slaves option and see if there is any change.

[samuel_bubat]

We have this problem sometimes with scenes that bring the slaves to their memory limits. After the rendering is finished they will stay using roughly
half the memory of the machine and don´t respond to new renderings. Also restart on render end doesn´t help. We have refamo so it´s just one click
to restart them all manually. (Vray 2.4 btw.)

[Penry]

OK. Performed a complete clean re-install of MAX and Vray..........no change. Still getting the 'busy' message on the render slave using DR. Ticked the retsart slaves on render end option.....still no change! Any ideas?

[Penry]

I am re-setting the spawner manually now and even that isn't working anymore!!!!!!!!Damn it!

[Penry]

FOUND IT!!!!! It was the additional memory I had installed yesterday! The only problem I have now is trying to work out why this is happening. I have tested the memory and all is good. I upgraded to 16gb from 8gb so now my PC and the render slave both have the same DRAM. Anybody got a solution to this problem? I need the extra memory to speed up my workflow as most scenes I work on are pretty detailed.

Thanx

[Svetlozar Draganov]

In case you are running the VraySpawner manually (not as a service) before starting the job please check if you have vraydummy.max stable in the taskbar tray.
Also , please send us vraylog.txt from the render node machine right after the issue appears.

[Penry]

I don't, and never have, run the VraySpawner as a service because it's never been stable with the office network. I have just removed the new memory and done a test render through DR and all is Ok. Are there any settings I should be changing/checking once the new memory is installed........dynamic memory limit for example? Kind of lost on this one. I will, however, run a test render with the new memory installed and post the vraylog.txt when it's done.

Thanx

[Penry]

I HATE MAX!!!!!!!! After all that, having checked the scene over for errors before going down the 'memory problem' route and done the whole memory in and out song and dance it turns out a simple box element in the scene was the problem!!!
AAAAAAAAAARRRRRRRRRRRRRGGGGGGGGGGGGGGGGGGHHHHHHHHH HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH

Thanx everyone for all your help......Autodesk you suck!

[Svetlozar Draganov]

Glad to hear you sorted it out.
Let us know if the same issue appears again.