Documentation / DrQueue FAQ¶
Here you can find answers to some of the most frequently asked questions about DrQueue.
General things about DrQueue¶
What license governs the use of DrQueue?¶
DrQueue is released under the GNU General Public License (GPL).
Where can I find a summary of features?¶
Have a look at wiki:FeatureList
Installing and Running DrQueue¶
What operating systems does DrQueue run on?¶
DrQueue currently runs on various Linux distributions, Mac OSX, Irix, FreeBSD and Windows 2000/XP/Vista/7 (using Cygwin).
Which software dependencies does DrQueue require?¶
- GCC / G++ (for compiling)
- Python (for Scons, jobscripts, Python bindings & DrKeewee)
- Scons (our build tool)
- GTK2 (for Drqman)
- pkgconfig (for Drqman)
- Ruby (for Ruby bindings & DrQueueOnRails webinterface)
What are the minimal and recommended hardware requirements for DrQueue?¶
There are no special hardware requirements for DrQueue. You need computers with network interfaces which speak TCP/IP.
These computers need some few megabytes of RAM and disk space (DrQueue master and slave). The render machines where the slaves are running need of course some CPU power. But that depends on the rendering job you want to compute. The master process can also run on the same machine as one of the slaves.
Where can I find detailed installation information?¶
Please read the INSTALL file which belongs to every DrQueue source release. Available online here: https://ssl.drqueue.org/redmine/projects/drqueue/repository/revisions/master/entry/INSTALL
A lot of stuff can also be found at Documentation.
Is it possible to mix different versions of DrQueue in one render farm?¶
Although it could be possible to mix different minor versions of DrQueue (for example 0.64.2 and 0.64.3), it is generally not advisable because bug fixes in one major version may break compatibility between them. Mixing different major versions (for example 0.63.x and 0.64.x) will in most cases not work because of structural changes and new features included in recent major DrQueue releases.
Common issues with DrQueue¶
I'm rendering with a renderer which can use more than one CPU/core per machine (multi-threaded renderer). Instead of running one process with all CPUs/cores, DrQueue starts N processes. What's wrong?¶
This happens when you leave 'Maximum number of cpus on one computer' on 'Maximum' (-1). Setting it to '1' causes DrQueue to start only one process on each slave.
This applies for example to Maya when rendering with 8-core machines and using the default Maya script generator which does auto-detection of available CPUs/cores.