We submitted a job, but its not switching to it tho its priority is set higher than the rest(with a group and a pool assigned to it).
Is the pool it’s assigned to higher or lower than the other job that’s rendering? This lets you set up the order in which machines will render.
So if you have Render01:
Urgent, 3D, 2D, global
and Render02:
Urgent, 2D, 3D, global
You can submit a nuke job in the 2D pool and Render02 will it before rendering any 3D jobs. And if you submit a maya scene with the 3D pool it’ll render the maya scene before the nuke jobs regardless of priority. This is nice for setting aside dedicated machines to ensure every department gets some render time but still let the machines help out other departments when they’re free. Or you can submit to the urgent pool in this example and every machine will jump onto that task.
Thank you I understand but this is not what i meant,
The problem is that it’s not switching to the job we want to render, this is the first time it happens, we never had this issue before.
There is some kind of problem, and we don’t know whats preventing the switching.
Ok, I’ve manage to make it work but in a weird way,
I’ve entered the job properties, machine limits and i switched all the slave on the left to the right side and i made it whitelist(never had to do that before for a job to work)
maybe its a bug i don’t know.
The problem is that beta 9 allows jobs to be submitted with empty whitelists. In previous versions, empty whitelists were ignored, and this functionality will be restored in beta 10.
Cheers,
- Ryan