03 September 2008
Supported Operating Systems
• Mac OS X 10.5 “Leopard” (32-bit only)
• Windows XP SP2, XP64
• Linux CentOS 4.5 (32- and 64-bit)
• Support for 64-bit operating systems on Windows and Linux.
• Mac OS X 10.5 (Leopard) is supported.
• The Nuke Personal Learning Edition (PLE) is now available. The PLE is a special version of
Nuke you can run without a valid license key. It is aimed at students, industry professionals,
and others interested in Nuke. To get the PLE, you need to install Nuke as usual and launch
the PLE in a special way. For more information, refer to the Installation and Licensing chapter
of the user guide.
• There is a new Light node that can be set to act as a spot light, point light, or directional
light. The old Light node that only supported point lights has been relabeled to Point
node to distinguish it from the new Light node.
• You can import cameras, lights, transforms, and meshes into Nuke from .fbx files
created in other applications. This option is available on Nuke’s Camera, Light, Axis, and
ReadGeo nodes. Nuke uses FBX 2009.1.
• The Card node has extended bicubics (bicubics with more control points). They allow
you to subdivide a card, giving you finer control for warping an area. You can subdivide
the card into an evenly spaced grid, or pick a location to add a row, column, or both.
For more information on the above features, see chapter 12, 3D Compositing, in the
• Stereo workflow:
• The Views > Stereo menu in the Toolbar has a new node called MixViews. The
MixViews node displays a blend between two views, allowing you to easily check how
elements in these views are aligned. For more information, see Displaying Views in the
Viewer in the Working with Stereoscopic Projects chapter of the User Guide.
• In the Views > Stereo menu, there is now a ReConverge node. It lets you shift
convergence (the inward rotation of the eyes or cameras) so that any selected point in
the image appears at screen depth when viewed with 3D glasses.
To change convergence, you need a disparity field that maps the location of a pixel in
one view to the location of its corresponding pixel in the other view. You can create a
disparity field using The Foundry’s O_DisparityGenerator plug-in, which is included in
the Ocula plug-in set, or a 3D application.
If you have Ocula installed, you can choose to use it when changing convergence. If you
select to use Ocula, extra refinements are done when performing the convergence shift
to produce more accurate results with disparity fields that are estimated by a software
process (like Ocula) rather than generated from a renderer where they are assumed to
For more information, refer to chapter 13, Working with Stereoscopic Projects, in the
• In the controls of the Paint node, Bezier node, and any nodes, groups, or gizmos that
have controls for x and y coordinates, there is a new Correlate function. It lets you
reproduce changes made to one view in the other.
To do so, you need a disparity field that maps the location of a pixel in one view to the
location of its corresponding pixel in the other view. You can create a disparity field
using The Foundry’s O_DisparityGenerator plug-in, which is included in the Ocula plugin
set, or a 3D application.
When Ocula is available, you can choose between using Nuke’s Correlate function or
Ocula’s O_Correlate plug-in. If you use Nuke’s Correlate function, the changes are
reproduced by adding the disparity vectors in the disparity field to the current values.
If you use Ocula’s O_Correlate, extra refinements are done to improve the results
where the disparity map is not perfectly accurate.
For more information, refer to chapter 13, Working with Stereoscopic Projects, in the
• Colour picker:
• Changed the Colour Picker slider order to TMI HSV RGB A.
• The colour wheel now offers the Nuke 4 style hue wheel. It can also be zoomed and
panned like the Node Graph and Viewer.
• You can show or hide the colour wheel by means of a button, rather than by resizing
the window. Clicking on the colour wheel button cycles through three states: the colour
wheel, the colour square, and hide the colour wheel/square.
• You can Ctrl/Cmd+click on the colour wheel to only affect the hue of the selected
colour, and Shift+click to only affect the saturation.
• The colour picker window includes colour swatches that can remember colours. There is
a button that lets you show and hide the swatches. To use a colour from the swatches,
left-click on a swatch. To save a colour in a swatch, right-click on the swatch.
• Removed the lock icon from Colour Picker to save screen real estate. When you have
one Colour Picker window open, you can now Ctrl/Cmd+click on a colour picker button
to open another.
For more information, see chapter 2, Using the Interface, in the Getting Started section
of the user guide.
• Geometry objects now have their own transform controls. You no longer need to add a
TransformGeo node after the object to manipulate its position, scale, and rotation in
• The Spotlight node now has a “cone penumbra angle” parameter, which controls the
softness along the edge of the area of illumination. This feature is only visible in the
rendered objects and not in the 3D OpenGL viewer.
• The Spotlight and Point nodes’ “falloff” toggle has been replaced with a “falloff type”
pulldown menu. It controls how much light the object gets from the light source, and is
based on the distance between the light source and the object. A Linear type will
diminish the light at a fixed rate as it travels from the object. Quadratic and Cubic
types will diminish the light at an exponential rate.
For more information, see chapter 12, 3D Compositing, in the user guide.
• Stereo workflow:
• You can set up views for stereoscopic projects simply by clicking the “Set up views for
stereo” button on the Views tab of the project settings. This deletes the view called
“main” and creates views called “left” and “right”.
• You can assign colours to all views that exist in your project settings by clicking on the
colour bar next to the view name. If you also check “use colours in UI?”, the colours are
used in Node Graph connections, split views indicators on nodes, and the controls of
certain nodes and the Viewer, making it easier to differentiate between views.
• You can now split all the controls of a node by right-clicking on the controls and
selecting “Split all knobs”.
• Split controls can be expanded to show the value for each view that exists in the
project settings. This allows you to give separate values for each view. To expand a
control you have split off, click on the small triangle on the left side of the control.
• Added “views” controls to the Anaglyph node properties panel. These controls let you
select which views you want to use for the left and the right eye.
• Removed the “stereo” check box on the .exr writer; it now figures out whether to do
this or not based on the filename and views to be rendered.
For more information, see chapter 13, Working with Stereoscopic Projects, in the user
• The default sys.path in Nuke now includes NUKE_PATH. Paths should be added in init.py
for this change to be reflected in Nuke. Alternatively, you can also use the environment
variable before starting Nuke.
• If you now add knob defaults using the command nuke.knobDefaults(), it is
recommended that you place them in init.py rather than menu.py. This ensures that
they are set for command line start-up as well as GUI (graphical user interface). If
these statements are not processed until menu.py (GUI start-up), then nodes created
from the command line Nuke Python prompt (i.e. starting as 'nuke -t') will not have the
• There is now an object in the Nuke module called env that gives information about the
particular Nuke environment the user is running on. It can be accessed in a dictionary
form, nuke.env ["key"].
You can find out what's in the Nuke "global environment" by entering the following in
the Script Editor:
Some of the items are read-only (for example, ‘64bit’ and ‘ple’), and others can be set
(for example, ‘threads’).
• The nuke.nodes syntax has been augmented. It can now also take name and input
parameters, for example:
r1 = nuke.nodes.Read(file = "<file path>")
r2 = nuke.nodes.Read(file = "<file path>")
t = nuke.nodes.Merge(name = "My Merge", inputs = [r2, r1])
• Python removeKnob() command no longer asks for verification.
• Instead of nuke.animation(...), you should now use the following syntax:
#create the node
b = nuke.nodes.Blur()
#get the size knob
k = b['size']
# create an AnimationCurve for the channel 0
# access all animation curves for the knob
a = k.animations()
# set the animation keys
For more information on AnimationCurve and AnimationKey objects, refer to the NDK.
• Simplified Group node bindings.
Before, when you created a node, for example, it would always be created inside the
If you used nuke.nodes.Blur(), the node would show up in the Node Graph.
If you then added nuke.nodes.Group(), wanted to create a node inside the Group, and
tried nuke.nodes.Blur(), the node would still open in the Node Graph window (Root
To solve this issue, Group nodes (this includes the Root) are context objects and
nuke.nodes.Blur() is effectively equivalent to:
from __future__ import with_statement
r = nuke.toNode("root")
For a group node:
from __future__ import with_statement
g = nuke.nodes.Group()
• Added a Python scriptClear() function to clear out the current script.
For more information on the above improvements, see the NDK as well as chapter 17,
The Script Editor and Python, in the user guide.
• Renamed “flipbook cache” preference setting to “disk cache”, which describes it better.
• You can have all Python commands executed by yourself or Nuke appear in the output
pane of the Script Editor when you check “echo python commands to output window”
on the Script Editor tab. For example, if you select a node from the Toolbar, the
corresponding Python command is displayed in the output pane.
Note that this does not apply to all actions you take in the GUI, only those that are
performed by executing Python script commands.
• You can change the type, weight, angle, and size of the font used in the Script Editor.
For more information, see chapter 15, Setting Interface Preferences, in the user guide.
• Node Graph:
• You can now press F on the Node Graph to zoom to selected nodes. As before, if no
nodes are selected, pressing F on the Node Graph fits all nodes in the space available.
• The Node Graph is now drawn in OpenGL for improved speed.
• When expanding the Node Graph with the space key, the nodes are now kept in the
same place on the screen.
• By default, the alpha channel from the mask input is used as a matte whenever the
node’s mask input is connected. You can change the channel by using the “mask”
pulldown menu in the node’s controls. To use a channel from the main input as the
mask, you need to make sure nothing is connected to the node’s mask input, and select
the channel you want to use from the “mask” pulldown menu. The mask input arrow
disappears as it is no longer being used. You can get it back by setting the mask
channel to “none”. For more information, refer to chapter 2, Channels, in the user
• There is a new predefined channel for masks called mask.a, and a new "inject" option in
mask controls. If you check inject, the mask from the mask input is copied into the
predefined mask.a channel. This way, you can use the last mask input again
downstream. You can also set a stream of nodes to use mask.a as the mask, and then
change the masking of all of them by simply connecting a new mask into the mask input
connector of the first node. For more information, refer to chapter 2, Channels, in the
• User knobs dialog:
• You can now delete multiple knobs at once. You can also delete an entire tab by
selecting all the items including the tab name.
• Manage User Knobs now offers a script button that can execute Python code in
addition to the existing TCL script button.
• Read and Write nodes:
• Added support for # in filenames for frame number.
You can now use, for instance:
img#.jpg for img1.jpg
img##.jpg for img01.jpg
img###.jpg for img001.jpg
img####.jpg -> img0001.jpg.
The old way of using, for example, img%04d.jpg for img0001.jpg continues to work,
• When rendering multiple Write nodes, they are now all executed before advancing the
frame, rather than rendering each Write all the way through the sequence. This can
help to improve caching performance.
• QuickTime codec options are now exposed on the Write node.
• Added support for reading alpha channels from and writing them into QuickTime
movies. Note that some codecs (such as YUV-based codecs) may not honour this.
• Overhauled .dpx reader/writer to handle many more dpx variations. Support for 16-bit
• When an execute command fails, it now traces the error message to the console.
• Added exr support for B44 compression (OpenEXR 1.6.0).
• Merge node:
• The operation types are now listed in alphabetical order.
• Channel sources have been moved to the second tab.
These changes make the properties panel more intuitive and easier to use.
• Added extra directories to the licence file search path on Windows Vista
(C:\ProgramData\The Foundry\FLEXlm) and Mac OS X (/Applications/TheFoundry/
FLEXlm, /Library/Application Support/TheFoundry/FLEXlm).
• License error messages now show the lmhostid number.
• Improved the icons in node properties panels and the Viewer controls. Less frequently used
controls in the node properties panel title bar have been moved to the Node tab. Hotkeys
and Edit menu entries have been added for the postage stamp and hide input actions.
• Added Revert, Cancel, and Close buttons on floating Control Panel windows. The Revert
button reverts any changes made after the control panel was opened. The Cancel button
does the same as the Revert button but also closes the control panel. The Close button
simply closes the control panel.
• Colour sampling: you can now Ctrl/Cmd+click to sample a colour from the Viewer, and Ctrl/
Cmd+Alt+click to sample a colour from the node’s input while viewing its output. Primatte is
a special case and always samples from the input.
• Transform > Tracker node: added an “update viewer” checkbox. When checked, the entire
image is redrawn during processing. If unchecked, only the search area is updated.
• You can now apply tracking (and other transform) data to individual Bezier points.
To do so, Ctrl/Cmd+drag and drop the track’s animation button on the Bezier point.
• VIEWER_INPUTs can now transform modify the image data.
• At user request, turning “reformat” on in the Crop node controls deactivates "black outside"
(and vice-versa) since this is the most common use pattern.
• Animating parameters: the properties panel right-click menu now includes a “Set key on all
knobs” option that you can use to set a key on all controls of the node at their current
• The SphericalTransform MirrorBall now uses a technically correct transform. The old transform
maths is now called 180 degree FishEye, and is still available in the node.
• Nodes in the Color > Math menu: you can now split the ‘value’ control into four fields to
edit the values assigned to individual channels.
• Added support for tiled rendering of OFX plug-ins that are capable of it, which often
results in significantly lower memory usage.
• Improved interactive performance by caching inputs to nodes open for editing.
• The default Truelight node now uses FilmLight’s v3 libraries. A Truelight2 node is also
included for backwards compatability and for customers who only have a v2 license.
You only need to be concerned about this if you are using Truelight profiles that require
advanced features made available by an additional license purchased from FilmLight.
If you want the Truelight menu item to continue to create the old version of the node
(Truelight 2), you will be able to override the node creation by putting the following in your
You can also create a Truelight2 node by pressing X and running the TCL command
"Truelight2" (without the quotes).
• Default start menu folder names on Windows now add “(32 bit)” when appropriate to avoid
overwriting 64-bit shortcuts.
• OFX plug-ins now pass through channels not being operated upon.
• Fixed version support commands to handle a variable number of digits.
• Fixed an issue with wacom pen driver losing events.
• Increased the LUT size to prevent quantisation in the blacks with the Kodak DLAD.
• Tidied up menu item labels, documentation, and tool tips.
• BUG ID 1394 - Grain node should keep the incoming bounding box if set to "Apply only
• BUG ID 1418 - The Nuke icon only appears on the first opened script.
• BUG ID 1701 - Resize widget not appearing in the corner of the main Nuke window.
• BUG ID 1811 - Text node’s font path defaults to /job/common.
• BUG ID 1937 - Bezier / Draw nodes: fixed inconsistent output when ‘invert’ is on. The ‘clip
to’ control decides exactly how far the invert fills out to. The default stops at the current
• BUG ID 2067 - Time > FrameRange node not taken into account in proxy mode.
• BUG ID 2094 - Text node: knob_default Text.font "/some/path/to/fonts" command fails.
• BUG ID 2351 - Artifacts and smearing in VectorBlur.
• BUG ID 2397 - User Guide: 'Using Practical Grain' is out of date.
• BUG ID 2433 - Configured FrameCycler to write out settings files to Nuke temp directory to
make sessions persistent. For more information, see Known Bugs and Workarounds.
The warning messages about QuickTime libraries not being present should now only appear
• BUG ID 2638 - Read QuickTimes: files recorded with high/low quality only playback low in
• BUG ID 2639 - Paint produces “a coding error in an Op”.
• BUG ID 2738 - Paint: on Windows XP, brush stroke appearance is delayed until mouse
stops moving or goes out of the bounding box.
• BUG ID 2855 - Dual screen saved layout on a single screen system messes up your layout.
• BUG ID 2908 - Reconcile3D and PointsTo3D tooltips show formatting marks.
• BUG ID 3011 - Side input mask pipe disappears when its not selected.
BUG ID 3020 - Console window is not reopened when closing a Nuke script (Windows only).
• BUG ID 3078 - Bezier contextual keyboard shortcuts not working.
• BUG ID 3109 - Rendering to TGAs from a static input produces inconsistent output.
• BUG ID 3161 - Interface resize amount is incorrectly calculated if you're in fullscreen mode
and have the drop down OS X menu down.
• BUG ID 3187 - Ramp: inverted Ramp node resets bounding box.
• BUG ID 3188 - Merge: ‘bbox’ knob breaks bbox expressions.
• BUG ID 3202 - Slower render on Windows with a customer script.
• BUG ID 3283 - When 'tearing' a window panel off to place it elsewhere, there is no overlay
• BUG ID 3351 - A test Tracker script and a Furnace wire removal script cause Nuke to crash.
• BUG ID 3497 - Bezier contextual keyboard shortcuts not working.
• BUG ID 3498 - Python distribution missing modules on different operating systems.
• BUG ID 3507 - Viewer renders frame, then distorts it (only on OS X PPC).
• BUG ID 3521 - Bezier: delete points on spline crashes Nuke.
• BUG ID 3523 - TransformGeo: zooming out causing geometry to be modified/drawn in a
• BUG ID 3525 - Bezier: undo not working correctly.
• BUG ID 3579 - Linux KDE window manager auto hides windows flagged as 'utility' when
Nuke loses focus.
• BUG ID 3680 - The Dilate node deadlocks.
• BUG ID 3709 - Empty values should revert to previous value if focus is moved away rather
than remaining empty.
• BUG ID 3777 - Curve Editor: cannot add a point anymore without first clicking on a point.
• BUG ID 3807 - Crash when disabling Normals node and trying to enable one of the 'show
• BUG ID 3824 - Check boxes do not highight correctly on mouse exit after mouse down.
• BUG ID 3865 - Provide option to scale the normals display in the 3D viewer.
The icon size setting on the Viewers tab in the Preferences can now be used for this.
• BUG ID 4115 - 3D overlays drawn much larger than previously, making them appear clumsy
and difficult to judge exact position.
• BUG ID 4179 - Quit shortcut in a group window exits without saving.
• BUG ID 4226 - The ~ shortcut to show a hidden Curve Editor isn't working.
• BUG ID 4249 - A customer script with a Crop node rendering incorrect result.
• BUG ID 4262 - ‘Segmentation fault’ error on a customer script.
• BUG ID 4321 - Viewer playback is slower when not moving the mouse.
• BUG ID 4359 - JoinViews node: inputs are set by index; however, when pasting into
another script the index to name mapping changes.
• BUG ID 4413 - Frame boundaries/film gate clipped by near plane.
• BUG ID 4416 - Read: a TIF file crashes Linux on Read unless you set threads to zero.
BUG ID 4419 - Improve caching performance.
• BUG ID 4474 - Viewer text occlusion.
• BUG ID 4478 - Ctrl/Cmd + Shift + X on a node in the Node Graph does not disconnect the
node if there is no input.
• BUG ID 4514 - A particular VectorBlur test script crashes Nuke.
• BUG ID 4518 - OFlow hang when rendering from command line.
• BUG ID 4521 - TCL (Python): filename_fix Tcl callback query.
• BUG ID 4524 - Edit > Node > Filename > Version Up/Down used to work (pre 5.0) with
upper case 'V’.
• BUG ID 4526 - Missing the option to turn off auto label and auto colour in the Preferences.
• BUG ID 4545 - Import Discreet LUT is broken.
• BUG ID 4557 - Viewer’s gamma slider: Y indicator ('Toggle gamma between 1.0 and the
previous setting') turns red when offset but is not red when saved script opened.
• BUG ID 4558 - Group tabs disappear when changing layout. They should remain next to the
• BUG ID 4566 - Viewer node does not disappear / get deleted when Viewer is closed and
preference is set appropriately.
• BUG ID 4570 - Frame expression does not work for .mov files.
• BUG ID 4580 - Nuke flagging premult state wrong to OFX plug-ins.
• BUG ID 4617 - Editing user knobs: ‘Start new line’ flag not saved in scripts.
• BUG ID 4656 - Python: knob.addDefault doesn't work on Text.font.
• BUG ID 4657 - Write in proxy mode with no proxy file name should error.
• BUG ID 4661 - Colour sampling stops working after first click.
• BUG ID 4671 - Channel selector: on creating a channel, the new channel is not automatically
assigned in the channel menu.
• BUG ID 4686 - Pressing ‘Auto-Compute’ with no inputs connected to Primatte causes it to
• BUG ID 4687 - Keyer widget doesn't stretch when panel is expanded.
• BUG ID 4710 - File > Open: script filter should default to .nk instead of the name of the
script already open.
• BUG ID 4750 - Erode (fast): crashes when input is a Bezier with opacity set to 0.
• BUG ID 4756 - Importing Ascii into a newly created root LUT causes Nuke to hang.
• BUG ID 4758 - Black x’s and white arrows are hard to read in some Shuffle node boxes
when Silver colour preset is selected in the Preferences.
• BUG ID 4818 - A Group exported as gizmo doesn't heed 'Start new line' set in 'Manage User
• BUG ID 4819 - Bezier: Crash when editing ‘shape’ control’s animation curve in Curve Editor
with Edit > Move.
• BUG ID 4833 - Root name is different in GUI and terminal mode.
• BUG ID 4851 - Can't disable (keyboard 'D') a multiple-node selection in Node Graph when a
Dot node is included.
BUG ID 4866 - Saving preferences to a home directory on a UNC path fails with a 'cant create
.nuke directory' error message.
• BUG ID 4894 - ShuffleCopy edit channel switched to 'none' causes Nuke to crash.
• BUG ID 4896 - Memory allocation failure in a customer script.
• BUG ID 4908 - Return typed to ‘new layer’ dialog ignores changes to text field.
• BUG ID 4929 - Add an option to nuke.show() to force show as a floating panel.
• BUG ID 4944 - User Guide: Oflow parameter 'Shutter Time' references figure not present.
• BUG ID 4947 - Dilate node on a roto shape causes segmentation fault.
• BUG ID 4950 - MotionBlur in several operators: locking up when you try to Write.
• BUG ID 4955 - ‘F' to frame expression only frames between 0 and 1.
• BUG ID 4958 - Can’t use Python “threading” module.
• BUG ID 4973 - Python: nuke.addFormat should return the created format rather than True
• BUG ID 4989 - Floating panels have redundant scroll bar.
• BUG ID 4991 - Adding a favorite directory without type using menu.py and the manual
instructions doesn't work: favorite doesn’t show up in any of the browsers.
• BUG ID 5001 - Hangs in Stabilize2D node.
• BUG ID 5012 - No error from version script up when Nuke script has not already been
• BUG ID 5018 - Progress bars dialog follows the mouse.
• BUG ID 5027 - OFX not returning bounds correctly in some circumstances.
• BUG ID 5035 - Add Python binding for Shuffle knob.
• BUG ID 5039 - A script with Color > Math > Expression node hangs Nuke.
• BUG ID 5041 - User knobs are added at the bottom of the list, rather than after the currently
• BUG ID 5047 - Assigning hotkeys to the Node Graph right-click menu doesn't work, whilst
those assigned in the Application menu do.
• BUG ID 5053 - Undo not working properly in the Curve Editor if multiple curves are
• BUG ID 5054 - TransformGeo: ‘uniform scale’ control affects rate at which mouse drags an
• BUG ID 5064 - Write node: .mov codec selected changed when script reloaded.
• BUG ID 5088 - Tracker: speed is considerably slower in Nuke 5 than in Nuke 4.
• BUG ID 5089 - Nuke.tcl should return the string not a boolean.
• BUG ID 5090 - Make frame in the Curve Editor respect the timeline setting for global/
input/custom when framing expression driven curves.
• BUG ID 5111 - Merge: 'mask' knob reference in existing scripts not auto-fixed as 'mask-
• BUG ID 5112 - Converting a gizmo into a Group and saving it as a Nuke script or gizmo
sets knob values to 0.
• BUG ID 5115 - Colour picker not able to select from current buffer if placed below an 'over'
node with two image inputs.
BUG ID 5123 - Framecycle this script doesn't replace %V with the view name, so Framecycling
a source image node directly can fail in stereo mode.
• BUG ID 5133 - Expression field in Curve Editor jumps to the end of expression when entering
• BUG ID 5145 - Changing ScanlineRender’s ‘filter’ control to ‘Impulse’ crashes Nuke.
• BUG ID 5167 - Copy node: the ‘from->to’ label for multiple channels no longer displayed on
• BUG ID 5168 - Perspective texture not displayed correctly in OpenGL.
• BUG ID 5173 - Menu items added to the Nuke Application menu should not get added in
Node Graph right-click menu.
• BUG ID 5175 - Bezier not showing animation dot on the node in the Node Graph.
• BUG ID 5184 - Make the JoinViews node work on any kind of input, not just image inputs.
• BUG ID 5190 - Avi files not recognised as QuickTime on Mac.
• BUG ID 5198 - Python panels crash if Cancel is hit and if a value is queried.
• BUG ID 5210 - Write node will not render out .exr / .sxr file formats with stereo ouput
ticked, causing a crash.
• BUG ID 5211 - AutoCrop on Write node does not support stereo views.
• BUG ID 5217 - Python node creation: old control panels reappear and float briefly before
new panels go to the Properties Bin.
• BUG ID 5238 - OFX plug-ins: not calling SyncPrivateData before a save/copy.
• BUG ID 5245 - QuickTime fails from command line passing argv 1 to Write node.
• BUG ID 5246 - QuickTime: random missing images when passing argv 0 to Read node.
• BUG ID 5249 - Geometry > Cube: the 'selectable' control disabled still allows mouse picking/
• BUG ID 5293 - Wrong Python object type gets returned for menu item (returns a "Menu"
object instead of the appropriate "Menu", "MenuItem", or "MenuType").
• BUG ID 5351 - Layout > Toggle Hide Floating Viewers does not work if Viewer is in fullscreen
• BUG ID 5355 - Proxy resolution mismatch : Bezier and other Draw nodes scaling incorrectly.
• BUG ID 5373 - Extracting a node that has multiple outputs does not disconnect from all
• BUG ID 5392 - Cloned Read node does not correctly set the on/off state of the postage
• BUG ID 5394 - Certain TCL panel code not drawing properly in Nuke 5.
• BUG ID 5403 - User-coded (TCL, Python) file browsers do not open by default in specified
• BUG ID 5406 - Postage stamp redraw is extremely slow.
• BUG ID 5420 - 3D > Modify > UVProject: spherical and cylindrical projection appear incorrect.
• BUG ID 5424 - Rotating a Bezier shape: the transform handle doesn't move but the points
spin out of control.
BUG ID 5429 - Add compiler version information for each platform to the makefile included
• BUG ID 5445 - Permissions: if menu.py in NUKE_PATH is not accessible, you get seg fault
• BUG ID 5487 - Creating a Dot node via menu or hot key should default to NOT open its
• BUG ID 5520 - Reword 'help' for 'nuke.createNode' to clarify 'inpanel'.
• BUG ID 5646 - Curve Editor’s right-click Loop function (Predefined > Loop) only creates
loops above frame 1.
• BUG ID 5749 - Python: nuke.channels() returns a list of <NULL> items.
• BUG ID 5891 - Write node: QuickTime advanced codec settings don't get saved for Avid
• BUG ID 5900 - Write and Read nodes: DPX edge_code - code put in our Write not then
appearing in our Read of that file.
• BUG ID 6021 - Animation menu: Copy Values, Copy Animation, and Copy Links not working
on multi-part knobs.
• BUG ID 6025 - Simple script crashing when viewing an IDistort node.
• BUG ID 6036 - Extra floating panels appear when loading layouts.
• BUG ID 6040 - Ocula: Write node set to 'all' channels does not write out the correlated
• BUG ID 6042 - TCL documentation missing on Windows.
• BUG ID 6046 - Left/right view mapping for paint strokes lost on script re-load.
See also Bug Fixes Logged During the Beta Period on page 15.
Known Bugs and Workarounds
• On Mac OS X 10.5 (Leopard), when the Viewer is set to the Crystal Eyes stereo display
mode, Nuke may trigger an OS X bug that causes a kernel failure. This is due to a bug in OS
X 10.5 to do with stereo OpenGL support. For this reason, we do not recommend using the
Crystal Eyes stereo viewing mode in Nuke on Leopard at this time. The bug has been registered
with Apple as bug number 5897735.
• We direct FrameCycler to write to the user’s Nuke temp directory (NUKE_TEMP_DIR) for its
user settings files. You can redirect this by modifying the FrameCycler/settings/
Global_Settings.xml file that can be found within your Nuke installation.
• BUG ID 3594 - Sampling colours for Primatte causes a double free or corruption crash.
This is caused by incompatible libstdc++ library on the Nuke running environment in question.
It’s a problem with some Linux distributions, notably Ubuntu 6.06 and CentOS 4.4,
and the libraries shipped with them. As a workaround, we ship the libraries we build Nuke
against, so you can force your operating system to use these. To do so, set the
LD_LIBRARY_PATH environment variable to point at the libraries.
• BUG ID 5063 - ScanlineRender: orthographic projection mode not working. This was fixed
earlier, but the fix caused bug 5978 and so has been removed. The bug will be addressed
more correctly in a subsequent release.
• BUG ID 5690 - Windows run-time libraries were not packaged properly with Nuke.
Nuke will now run correctly from a network install on Windows without specifically installing
the run-time libraries, though we still recommend that you do so as there will still be
some minor problems without them. For details, please see Installation on Windows in the
Installation and Licensing chapter of the user guide.
• BUG ID 5898 - Text on nodes on the Node Graph is fuzzy, hard to read, and loses lines
As a workaround for this, font smoothing is turned off for Nuke during install on Mac OS X.
You can also do this command manually from the terminal:
defaults write uk.co.thefoundry.Nuke5.1v1 AppleFontSmoothing -int 0
To re-enable font smoothing, you can use:
defaults write uk.co.thefoundry.Nuke5.1v1 AppleFontSmoothing -int 1
• BUG ID 5922 - At the moment, cloning does not work properly with all OFX nodes. This
affects, but is not restricted to, any nodes that have an analysis pass.
• BUG ID 5966 - PLE: gizmos exported out of PLE are not read back in through Other > All
Plugins > Update.
• BUG ID 5998 - In full-screen mode, the colour picker window goes behind the main window
when using Linux Gnome window manager.
• BUG ID 6115 - The exr reader needs the Nuke cache directory to exist, otherwise it will fail
with an error message of “exr reader