Q100055: Nuke render from command line fails with "No such feature exists." "Feature: nuke_r"

Follow

SYMPTOMS

Nuke render from command line fails with "No such feature exists." "Feature: nuke_r"

CAUSE

If there is a nuke_r license available, then there is a license installation problem, but usually, the user has only an interactive license and is not using the correct command line to render with it.

RESOLUTION

When launched from command line, Nuke will seek EITHER an interactive (GUI workstation) license OR a render-only license. It depends on which command line option you include:

-x
or
-ix

The first seeks a nuke_r (render license), the second seeks a nuke_i (interactive license).

There is no provision for precedence or fallback from one license type to the other. The presence or absence of "i" as a flag on the command line is the determining factor in which license is requested.

You could possibly script a render manager to run the command line that's appropriate for the license(s) you have and that you want to use, but this is beyond the scope of Nuke functionality.

Note also, that a plug-in license type (interactive or render) always follows the type used to license the host that called it. Nuke renders (nuke_r) will only ask for plug-ins licenses of type _r.

Was this article helpful?
0 out of 0 found this helpful