We’ve just got Vue Infinite 6.6 with 5 renderbull licenses for a job we’re currently working on but I’m unsure of the correct procedure for submitting an animation from Vue to Deadline 2.7 so that we can utilise our 5 renderbull licenses.
I think the Deadline documentation on this is incorrect as it specifies files which do not exist in our Deadline repository, for example;
We do not appear to have the VueSubmission.py in our Deadline repository so the above command will obviously not work.
Any clarification on the correct way (or alternative procedure) of getting our Vue animations rendering across our 5 nodes through Deadline would be appreciated.
The online documentation reflects Deadline 3.0 which now uses Python scripting. We started shipping 3.0 two weeks ago so the website has been updated to the new version, and VueSubmission.py is obviously a Python script filename.
You will probably have to wait until Monday to get a response from Ryan Russell (our lead developer) about the correct steps when using Deadline 2.7.
Anyway, in the meantime I’ve managed to submit a vue scene to the renderbulls using the submission dialog in the deadline monitor, it renders fine for a single frame but I’m now having issues rendering a 250 frame animation.
The option to render full animation does not appear to work but I can specify a frame range to render (0-250) however the problem is that every frame renders out to the same file (eg:vueoutput_.jpg) - there is no frame numbering (eg:vueoutput_0001.jpg). Any ideas?
I believe if you set this up in the Animation Render Options as explained here, the frame padding should be appended to the output filenames properly: franticfilms.com/software/su … ne/vue.php
Thanks for the response, however I’m still having a bit of a problem.
Using the string you supplied and following the procedure detailed in the help, I cannot get Vue to submit more than one frame to Deadline (always frame 0). I’ve obviously tried making sure “render animation sequence” is checked and I’ve also tried manually specifying the animation range but without luck.
When manually submitting from within the Deadline Monitor, I can get the whole frame range to render but then I get the problem with the frame padding not being appended correctly.
What Vue options are you using in the submission dialog? Is the Render Full Animation option selected? I believe when this option is selected, you will still only see one task in the Monitor, but Deadline will render all the frames of the animation in one go. We know that it would be nice to split up one frame per task, but this isn’t possible in Deadline 2.7.
In Deadline 3.0, it should be possible to split up a sequence into individual tasks.
To be honest, I didn’t let it render more than one frame as I thought only seeing the single task meant it was only rendering a single frame!
So assuming that it will render every frame of the animation in one task, I’m guessing that the limitation is that only one machine can render an animation unless I split up the animation sequence into ranges manually and submit seperate jobs?
Does this issue stem from Vue? (it wouldn’t surprise me given the amount of “issues” I’ve had in the 3 days I’ve owned Vue).
I’m gonna push for an upgrade to Deadline 3 this week if you think that this issue is resolved in the new version I’m guessing we’ll need to contact sales for an 3.0 license?
It was more of a mixture between Vue’s limited command line rendering options and our understanding of how it worked. In 3.0, we refactored the Vue plugin a bit. Now we find that if you submit from within the Animation Render Options dialog within Vue, you should be able to split up the frame sequence between multiple machines.
Yes, just send them an email. If your support and upgrade contract is up to date, you can upgrade to 3.0 at no additional charge.
I’m guessing we’ll need to contact sales for an 3.0 license?
In 3.0, we refactored the Vue plugin a bit. Now we find that if you submit from within the Animation Render Options dialog within Vue, you should be able to split up the frame sequence between multiple machines.