Hello, I'm currently evaluating Qube for our facility, and I have a couple of questions.
- First of all, I had some problems getting the XSI jobtype to install. I'm guessing changes have been made to XSI in version 6.5 which breaks the current code. I found a problem in xsisubmit.js which may be the reason for it. Since render options have drastically changed since 6.x, some objects are renamed. Passes now inherit options from the main render settings instead of having one per pass, but changing line 62 to something like this seems to work:
oPSet_new.ImageFramePadding = Application.GetValue("Passes.RenderOptions.FramePadding");
There were other problems, like the returned frame padding number doesn't mean the same thing anymore so the fields in the Qube dialog in XSI isn't always filled with the correct values from the scene. I changed line 62 manually on all nodes, and it's rendering now.
- The frames I got from my first successful render with the xsi jobtype returns a slightly scrambled sequence, the frame numbers isn't correct in some of the frames, which makes the animation jump back and forth when played back, any idea what causes that?
- I was trying to use Qube to install the jobtype through a command line job with the /passive switch, but since there's no UNC path support in CMD I couldn't do it, is there a way around that? I tried using pushd and even a mounted Z: drive but couldn't get it to work.
- I'm also wondering how you set up groups of computers and what the difference is between groups and clusters? I found the manuals somewhat confusing there, and couldn't locate the qbwrk.conf file anywhere, or where to create it.
- Lastly I would like to know how to use both CPUs of a node for one frame, often it's more efficient to render one frame per computer instead of per CPU, especially memory-wise, currently there are two xsibatch processes running simultaneously, doubling the memory usage.
Thank you,
Arvid
Stockholm Post Production
