Hi,
Using the 3DSMax submission script to submit a job to Vray DBR requires at least 1 idle server to be selected before the render will start.
This is a problem, as in an ideal situation all of our nodes will be actively working on a different job, and thus we cannot select an idle server and the render cannot start.
This isn’t an issue with the similar Corona DBR script, as the job starts even with no servers selected, allowing Deadline to adjust server assignment based on priority and pool assignment on the fly.
Is there a workaround to this? Having the VFB on the local machine is very important for us.
Are you sure it works for you with corona? Because for me deadline will show the jobs as rendering but the master will only actually start Max once EVERY open dr task is picked up by a worker.
@ThomasCoote Have you tried using the off-load option in the submitter? That should let you add a DBR job to the queue without needing to pick idle machines from the list.
@Kevin_N If you want your DBR jobs to start rendering immediately after task 0 is picked up by the master Worker, then Dynamic Start for V-Ray or Auto-start local Worker for V-Ray RT needs to be enabled in the Plugin Configuration of the 3dsmax or 3dsCmd plugin depending on which render plugin you are submitting your off-load DBR jobs to.
Hi Justin,
I’ve been using the dedicated DBR submitter, attached image.
As you can see, no servers are available because they’re currently rendering someone elses job. If possible, I’d like to be able to hit Start Render, have the job start locally, then pick up nodes as they become available. I can do this with the Corona DBR submitter, but not with the Vray submitter - it throws an error.
For my office it’s very important that we render locally with a visible VFB, so can’t offload renders unfortunately.
Ah, gotcha!
From what I’ve figured out about Vray DBR the render cannot be started until there are running Vray workers attached to the Vray render queue. The submitter is enforcing this limitation, as until there are Vray workers running the ‘Start Job’ command will go nowhere.
Corona doesn’t use a configuration file to hard-code the identities of workers like Vray does, which is likely why Corona is behaving differently.
