nuke 8.0v1 releasenotes

Release Notes for Nuke 8.0v1

Release Date05 December 2013

Qualified Operating Systems Mac OS X 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks)

NOTE: Nuke is expected to function correctly underMac OS X Mavericks (10.9), but we are seeing UIperformance degradation compared to previous OS X versions. We areworking on resolving these issues.

Windows 7 64-bit andWindows 8 64-bit

CentOS/RHEL 5 and CentOS/RHEL 6

Other operating systemsmay work with Nuke, but have not been fully tested. If you have any problemswith aparticular operating system, please contact [email protected].

Requirements for GPU AccelerationTo take advantage of GPU acceleration, youmust have:

an NVIDIA GPU with compute capability 2.0 (Fermi) or above. A list of the compute capabilities of NVIDIA GPUs isavailable at www.nvidia.co.uk/object/cuda_gpus_uk.html

NOTE: The compute capability is a property of the GPU hardware and can't be altered by a softwareupdate.

graphics drivers capable of running CUDA 4.2 or above.

OnWindows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU.Drivers fromApril 2012 onward support CUDA 4.2.

Go to http://www.nvidia.com/Download/Find.aspx?lang=en-us formore information.

2 OnMac, the CUDA driver is separate from theNVIDIA graphics driver andmust be installed, if you don't have italready. Theminimum requirement for CUDA 4.2 is driver version 4.2.5 which can be downloaded fromwww.nvidia.com/drivers.

NOTE: We recommend using the latest graphics drivers, where possible, regardless of operating system.

New Features

ApplyMaterial

A new filter control has been added to the ApplyMaterial node, allowing you to use a named filter when applying amaterial.

ApplyMaterial can be found in the 3D > Shader menu. Click here to launch the online help page.

BlinkScript

A newBlinkScript node has been added. This utilizes our Blink framework to compile and run C++-like imageprocessing kernels on the CPU (with optional SIMD acceleration) or GPU. It streamlines plug-in developmentworkflow significantly, as you no longer have to exit Nuke to compile your code.

The Publish button, on theKernel Parameters tab, can be used to share your BlinkScript tools with others,without exposing the development environment. This button creates a group containing a copy of the current node,which can then be saved as a gizmo if desired. Only the kernel parameters and GPU controls are exposed by defaultin the published version of the node.

You can also enable Protect kernel, next to the Publish button, before publishing. When enabled, the kernelsource is encoded inside the published version of the node, and is not readablewhen the published node is saved toa script.

Click here to launch the online help page.

Breakpad Crash Reporting

Breakpad crash reporting has been integrated into Nuke. This allows you to submit crash dumps to The Foundry inthe unlikely event of a crash.

Crash reporting is enabled in GUI mode and disabled in terminalmode by default. You can toggle reporting on andoff using the --crashhandling 1 or 0 option on the command line or by setting the environment variable NUKE_CRASH_HANDLING to 1 or 0.

|RELEASE NOTES FOR NUKE 8.0V1

3When crash handling is enabled in GUI mode, you can control whether reports are automatically submitted or notusing the --nocrashprompt command line option or by setting the environment variable NUKE_NO_CRASH_PROMPT to 0.

Crashes in terminalmode are automatically submitted when crash handling is enabled.

CameraTracker

Nukes CameraTracker has been overhauled and now includes tracking stills to create an animated 3D camera andadding User Tracks to augment a solve or process and entirely manual track and solve.

You can automatically track features, add User Tracks or tracks from a Tracker node, mask out moving objects usinga Bezier or B-spline shape, and edit your tracksmanually. CameraTracker can solve the position of several types ofcameras as well as solve stereo sequences.

The new CameraTracker has threemain workflows:

Sequence - designed to track a contiguous frame sequencewithminimal intervention from you.

User Tracks - allows you to manually place trackingmarkers to augment, or even totally replace, sequencetracking. You also assign User Tracks as 3D Survey Points to improve solve accuracy or link solves to the sameworld coordinates.

NOTE: 3D Survey Points have replaced the ProjectionSolver workflow, but you can still addProjectionSolver nodes by pressing X in theNodeGraph and entering ProjectionSolver as a TCLcommand.

Stills - creates a camera track from reference frame stills taken on site. These represent theminimumnumber offrames required to cover your subject with sufficient overlap.


Context-Sensitive Online Help

Nuke now features an online help system linked to individual nodes. The in-context help is designed to replace thenode specific tooltips in-application.

Previously, when you clicked the ? in the properties panel in Nuke a brief tooltip displayed with a short description ofthe node and, in some cases, a little bit of control usage info. The new system cuts away to the default browser anddisplays the relevant content from the new online HTML help, including video tutorials and example scripts.

NOTE: You can still display the tooltip by hovering over the ? in the properties panel.


4There are also some new Preferences, on theControl Panel tab under Documentation, which will allow you tochoose to display the local copy of the online help, The Foundry version fromourwebsite, or your own customURLs.

Click here to launch the online help.

Dope Sheet

TheDope Sheets functionality, layout, and visibility have been improved:

Keyframe positions can be remapped in theDope Sheet using AppendClip, Retime, TimeClip, TimeOffset, andTimeWarp nodes. The keyframes are displayed in context, allowing you to shift keysmore easily within theDopeSheet from their remapped positions.

Nodes that affect frame ranges are now displayed within a layer in theDope Sheet for easier visualization.


EditGeo

Nuke now includes an EditGeo node allowing you to select and edit geometry or point cloud vertices and faces in the3D Viewer.

EditGeo can be found in the 3D > Modify menu. Click here to launch the online help page.

Import Nuke

A new import nuke function has been added to allow you to useNuke as amodule in any Python interpreter. Werecommend running the Python interpreter bundled in theNuke install directory.

You can import Nuke as amodule into a third-party Python 2.7.3 interpreter by adding the file path to Nuke's site-packages directory to the usrlocal.pth file in your Python 2.7 install.

NOTE: The Foundry cannot provide customer support for third-party Python interpreters.

Whichever interpreter you choose, use the import nuke declaration to makeNukes Script Editor functions andcommands (such as nuke.nodes.Blur() to add a Blur node) available in the interpreter.

Formore information, select Help > Documentation fromNuke'smenu bar and navigate to Python DevelopersGuide > Running Nuke as a Python Module.


5MatchGrade

MatchGrade for NukeX allows you to match grades fromunrelated frames as well as the original graded sourcematching function. Additionally, you can now export LUTs from the analysis to an OCIOTransform node to useelsewhere in the node tree:

Match Graded Source - extract a baked-in grade by matching the source footagewith a graded version of thesource.

Use this to create and export the grade to usewith the original source footage. The same frames are expected onthe source and target inputs.

Match Different Clip - match the grade in a different clip where the source and target frames are different.

Use this to create a grade to reproduce the look of the target in the source footage. You can, for example, createthe grade to match an element between different shots by using themask input to match the colors on theelement only in the different clips.

Analyze Reference Frames - analyze a set of reference frames. First set thematching task then key referenceframes that pick out the characteristic colors in each sequence.

Then click Analyze Reference Frames to calculate the grade.

Auto-analyze Per Frame - calculate the best grade to use on a frame-by-frame basis when extracting a baked ingrade.

Select Auto-analyze per frame when the task is set to Match Graded Source to enable this.

Export - export the calculated grade in .csp format for usewith theOCIO FileTransform node.

A CDL transform can also be calculated and exported to OCIO CDLTransform. There is the option to manually setCDL parameters and recalculate the best fit transform.

MatchGrade can be found in theColor menu. Click here to launch the online help page.

ModelBuilder

ModelBuilder for NukeX now supports the unpacking of geometry as UVs using seams marked by hand in theViewer. The seams control the unwrapping, tellingModelBuilder where it's allowed to cut themodel in order to beable to lie themodel flat without any faces overlapping.

Unwrapping generates UV values for each of the vertices. You can do it asmany times as you like; each iterationreplaces whatever UVs you had previously.

ModelBuilder can be found in the 3D > Geometry menu. Click here to launch the online help page.

Multi-part EXRs

Nuke now supportsmulti-part EXR files using ILMs OpenEXR2.0 library. Multi-part EXRs allow you to read individualchannels, layers, and viewswithin an EXR file without unpacking all the parts contained within it.


6Additionally, you can writemulti-part EXRs out using theWrite nodes interleave dropdownwhich determines theparts that arewritten to file:

channels, layers, and views - creates a single part imagewhich is compatible with earlier versions of Nuke andother applications using an old OpenEXR library.

channels and layers - separates views into the layers and channels contained within the view.

channels - separates layers into their component channels.

ParticleCache

The ParticleCache node allows you to write particle systems to file and read themback in to alleviate the constant re-evaluation of pre-frames in the simulation.

If you have downstreamnodes requesting extra frames outside the normal range, such asmotion blur orScanlineRender shutter length, use thepadding control to set the number of frames to extend the sequence by, atboth start and end.

NOTE: ParticleCache nodesmust be placed at the base of a single particle systemormultiplemergedparticle systems, they can not be placed beneath a Scene node connected to two separate streams or inthemiddle of a string of particle nodes.

ParticleCache can be found in the Particles menu. Click here to launch the online help page.

Pixel Analyzer and Scopes

A Pixel Analyzer panel has been added to the contentsmenu, allowing you to collect color information frompixels inthe Viewer. The analyzer has threemodes:

Ctrl/Cmd + click - samples a single pixel wherever you click in the Viewer.

Ctrl/Cmd + click and drag - samples single pixels as you drag around the Viewer, producing current, max/min,average, andmedian pixel values.

Ctrl/Cmd + Shift + click and drag - draws amarquee aroundmultiple pixels, producingmax/min, average, andmedian pixel values. You can drag themarquee around to sample different areas and adjust its size using thehandles in the Viewer.

Nuke has adopted Hieros Histogram,Waveform, and Vectorscope panels, accessed from the content menu. Thereare also new scope controls in the Preferences > Scopes tab.

Click here to launch the online help page for the Pixel Analyzer or here for the Scopes help.


7QuickTime Processing

Theway that Nuke and Hiero handleQuickTime clips has been overhauled, allowing you to change various read andwrite options.

Nukes Read node attempts to select the best fit combination by reading an extended list of metadata key/valuepairs from theQuickTime header, including nclc atom, gama atom, and ProRes codec headers.

Nuke also writes out usermetadata depending on the specific settings used (outside of the nclc and gama atomsand ProRes header) and Hiero has been set to use these if it finds them in the .mov files written, instead of theatomsmentioned above. If Hiero doesn't find this usermetadata, it falls back to using the atoms/header data.

You canmanually override the following mov Options in the Read node properties panel:

ycbcr matrix - sets theway YCbCr is converted to RGB. You can choose to use the new Rec 601 and Rec 709 orthe Legacy encodingmethods, which are themethods used previously in Nuke.

codec - sets the codec used to read theQuickTime file. The codec dropdown defaults to a codec appropriate for theQuickTime in question, where available, and only lists those that declare themselves able to read the file.

pixel format - sets the read and write pixel format, which includes bit-depth, colorspace, pixel packing, and ranges.This setting defaults to the best format accepted by the codec, allowing Nuke to perform the conversion to RGBwithout the use of an unknownQuickTime transform, where possible. RGB pixel types rely on QuickTime to do theconversion from YCbCr when dealing with a non-RGB codec.

Setting theWrite node properties file type to mov allows you to override the sameQuickTime controls as the Readnode, except that thepixel format dropdown is populated depending on the codec chosen.

ScanlineRender

Nukes ScanlineRender node now supports Deep output allowing to connect Deep nodes directly downstreamofScanlineRender nodes.

Additionally, the render dropdown for 3D objects now contains all display types, allowing you to renderwireframe, solid+wireframe, and textured+wireframe.

Text

Nukes Text node has been reworked to includemore text options and attributes for individual characters:

Make group and individual character selections in either the Viewer or properties panel.

Adjust single characters in a text string including individual or group character transforms.

NOTE: The font dropdown includes system fonts by default. If you don't want access to the local systemfonts, go to the Project Settings > Font tab and disable include system fonts.


8Text can be found in theDrawmenu. Click here to launch the online help page.

Miscellaneous New virtual sliders have been added to all numeric controls. Hover over a control, click themiddlemouse button,then drag the field to adjust the associated control. Hold Shift to increase slider sensitivity.

Three new filters have been added to all filter menus. The new filters are especially useful for down-scaling imageswithout excessive softening:

Lanczos4 - good for scaling downwithminor sharpening.

Lanczos6 - good for scaling downwith some sharpening.

Sinc4 - a box windowed Sinc filter, good for scaling downwith a lot of sharpening.

The filter numbers at the end of the filter name denote thewidth of the filter, similar to the naming scheme usedby PRMan (http://www.renderman.org/RMR/st/PRMan_Filtering/Filtering_In_PRMan.html).

NOTE: All three filters have negative lobes and can produce values outside the range of the input pixels.They exhibit increased ringing as the filters become sharper.

In-panel color picker dropdowns have been added to nodes that feature the regular floating color picker panel.

A new luminance mix slider has been added to the ColorCorrect and HueCorrect nodes, allowing you to dissolvebetween the cooked/output luminance at 0 and the original/raw luminance at 1.

A new Capture this Viewer button has been added to write the contents of the current Viewer to a .jpg file.

Capture this Viewer is located in the Viewer pane, adjacent to the Flipbook this Viewer button.

The Viewer now has a full frame processingmode. When enabled, Nuke does not skip scanlines when rendering inthe Viewer.

AWireframe shader has been added, which overlays an adjustable wireframe on any geometry at render time.

Wireframe can be found in the 3D > Shader menu.

BUG ID 13458 - ScanlineRender: The render dropdown for 3D objects now contains all display types, allowing youto renderwireframe, solid+wireframe, and textured+wireframe.

BUG ID 32324 - Monitor Output: Nuke has adopted Hierosmonitor out functionality, adding support for SDI outon Linux.

NOTE: AJAmonitor out cards are not currently supported on Linux.

BUG ID 36378 - MergeMat: A new also merge dropdown has been added to the properties panel allowing you tomerge additional channel sets.

BUG ID 38750 - Nuke now ships with Courier and Charter, Courier, and Utopia default fonts. Copyrights belongs toBitstream Inc., IBM Corp., and Adobe Systems Inc., respectively.

BUG ID 38765 - Alembic: Ogawa support has been added read and write operations.


9Feature Enhancements GPU acceleration for certain nodes is now available with a standard Nuke license. See Requirements for GPUAcceleration on page 1 formore information.

BUG ID 18040 - CameraTracker now includes a selection of common film back options.

BUG ID 24080 - The Sony S-Gamut (S-Log) colorspace primaries have been added to the Colorspace node.

BUG ID 29804 - VectorGenerator, Kronos, andMotionBlur now fall back to the CPU if a GPU render fails due tolack of memory.

BUG ID 32179 - ModelBuilder: The Viewer now has a visual referencewhen operations are in progress, such asextrude and bevel.

BUG ID 32248 - ZDefocus now includes the option to use a flat depth channel.

BUG ID 32899 - DeepMerge: A new drop zero threshold control has been added to DeepMerge, allowing you todiscard holdout samples below a certain threshold.

This control can help filter out samples with low alpha values caused by floating point inaccuracy.

BUG ID 34656 - DeepRead: You can now use custom file extensions for Deep .exr files in the sameway asstandard files.

For example, adding an odzReader.tcl file to your .nuke directory containing the lines:load exrReader.so

add_file_extension_alias odz exr

Allows Nuke to read .odz files using the .exr reader.

BUG ID 35330 - The default 3D Viewer camera position is now x=3.5, y=3.5, z=3.5 and is rotated so that thecamera is oriented towards the Viewer origin.

BUG ID 35522 - Nukes Read node now disregards Deep data fromOpenEXR 2.0 files, allowing clips to be openednormally without the use of DeepRead.

BUG ID 35563 - Added ACES primaries to the Colorspace node.

BUG ID 36248 - Added a note about pre-rendering from IBKColor to the ReferenceGuide.

BUG ID 37016 - Kronos, MotionBlur, and VectorGenerator now produce identical output from the same imagewhen processed on both the CPU and GPU.

BUG ID 37108 - Keyframes on the timeline now updatewhen temporal nodes, such as TimeOffset, aremanipulated in theDope Sheet.

BUG ID 37391 - Text: The Viewer toolbar now includes keyframe +/- and edit text mode controls.

BUG ID 37749 - EXPTool has been renamed to Exposure.

BUG ID 37908 - ModelBuilder: You can now flip object or face normals in object and face selectionmode by right-clicking in the Viewer and selecting flip face normals.

BUG ID 38388 - CameraTracker: A new Update Track button has been added, allowing you to retrack a range offrameswithin an existing set, instead of retracking the entire sequence.


10

BUG ID 38390 - CameraTracker: A new Update Solve button has been added, allowing you to resolve a range offrameswithin an existing solve, instead of recalculating the entire sequence.

BUG ID 38455 - MatchGrade: A new Output dropdown has been added to the properties panel allowing you toselect what is displayed in the Viewer: Source, Target, orMatched.

BUG ID 38708 - A new channels control in the Copy node (and various others) allows you to create channels intobuilt-in layers.

BUG ID 38928 - Tracker: The default add tracking anchor hotkey, Shift, has been changed to Ctrl/Cmd+Alt in-linewith CameraTracker.

Bug Fixes BUG ID 3326 - Increasing the Viewer downrez caused Flare and Sparkles to appearmagnified.

BUG ID 6429 - The file browser did not collapse sequential files when they did not have a file extension, such asimage.001, image.002, image.003, and so on.

BUG ID 10884 - Text: Closing the properties panel did not hide the transform jack overlay in the Viewer.

BUG ID 15561 - Channel adds were generated during saves even when the channels were not referenced in thescript.

BUG ID 16404 - The 3D Viewer did not use Camerawin_translate orwin_scale controls.

BUG ID 16484 - QuickTime: Valid rgba alpha channels were not included in alpha-supporting Quicktime codecs,such as Prores 4444 and Animation.

BUG ID 16855 - Metadata was not updated duinrg rendering.

BUG ID 18206 - SplineWarp: Persistent preview always showed rgbwhen applied to other channel sets.

BUG ID 19819 - PrmanRender: Particle systems could not be rendered.

BUG ID 21314 - Roto: Selecting no animation on all knobs added a keyframe on the current frame.

BUG ID 21370 - Nuke crashed in terminalmodewhen calling the Preferences file.

BUG ID 21839 - Denoise: White alpha channels were created from rgb only inputs.

BUG ID 22179 - Denoise: Moving the analysis region updated before you finishedmoving it.

BUG ID 22335 - TheV view indicator didnt disappear after unsplitting controls.

BUG ID 23213 - ReadGeo: Enabling all objects in the properties panel showed objects in the Viewer with either atranslate or rotate offset.

BUG ID 24138 - ReadGeo: Changing the file type from a static .fbx to an .obj sequence caused unexpectedbehavior.

BUG ID 26089 - Expression link arrowswere only drawn halfway between nodes in theNodeGraph.

BUG ID 26129 - Vectorfield: Selecting file type > cms when the actual LUT file typewas different caused Nuke tocrash.

BUG ID 26142 - The AlexaV3LogC LUT in root LUTs was an older version than the one in the Colorspace node.

BUG ID 26234 - Setting the ContactSheet nodes row control to negative values caused Nuke to crash.

BUG ID 27622 - ModelBuilder: The F hotkey did not center on the selected object in the 3D Viewer.


11

BUG ID 27800 - The Text nodewas usingmorememory than expected.

BUG ID 28887 - ModelBuilder: Selecting an object in the Viewer did not select the corresponding entry in the in theScene list and vice versa.

BUG ID 29048 - OCIO: Using the ocionuke library in terminalmode resulted in an error.

BUG ID 29279 - ModelBuilder: Selecting the current shape from the shapemenu didnt initialize the shape addingtool.

BUG ID 29564 - ModelBuilder: Snapping transformhandles to the object surface automatically caused problemswith the scaling behavior.

BUG ID 29952 - RotoPaint: Keyframes specific to individual views appeared in all views.

BUG ID 29966 - RotoPaint: Keyframes on the stereo offset control were not displayed in the VIewer timeline.

BUG ID 30659 - Polygon clipping was incorrect in theDisplacement node.

BUG ID 31718 - CameraTracker: Camera sensor presets were not scriptable.

BUG ID 32143 - Playback did not reach 24 fps for geometry attached to a TimeOffset with reverse input enabled.

BUG ID 32328 - Dope Sheet: The unkeyable Read file control was exposed incorrectly.

BUG ID 32334 - RotoPaint: Drawing a spline in proxy mode resulted in unexpected behavior.

BUG ID 32364 - Tracker: RotoPaint toolbars and overlays disappeared when a Tracker node's properties panel wasopen andthe Viewer was displaying and error.

BUG ID 32369 - QuickTime: Converting from 16-bit scaled incorrectly.

BUG ID 32457 - RotoPaint: In multi-view scripts, cutting and pasting a split shape did not work as expected.

BUG ID 32472 - RotoPaint: Undoing the transform on a shapewithmodified points locked Nuke.

BUG ID 32475 - RotoPaint: Moving a shape's transformhandle occasionally moved only a single point on theshape.

BUG ID 32520 - ModelBuilder: The source image appeared until a refresh was forced with unlocked cameras.

BUG ID 32552 - Mac OS X only: Movingmultiple RotoPaint points and shapes while changing frame occasionallycaused Nuke to crash.

BUG ID 32569 - Textured objects occasionally disappeared during playback when using DisplaceGeo andPositionToPoints nodes.

BUG ID 32592 - ModelBuilder: When Preferences > Control Panel > expand/collapse panels in Propertiesbin to match selection was enabled, baking geometry created empty ModelBuilderGeo nodes.

BUG ID 32752 - Dragging a roto point, 3D object, or the Viewer playhead behind a floating window displaced theobject randomly.

BUG ID 32832 - ParticleEmitter: Emitting from faces with emit order set to uniformly or in order caused colorfrom texture to be ignored.

BUG ID 32851 - ParticleEmitter: Enabling color from texture did not apply the color properly when the incomingbbox did not match the format.

BUG ID 32992 - RotoPaint: toolbar_paint_source reverted to default when switching tools.

BUG ID 32996 - ModelBuilder: Therewas no visible indication of which shapewas selected in the scene tree.


12

BUG ID 33536 - Entering an empty string in aMerge nodes label field caused an error if the red, green, or bluechannels for that nodewere disabled.

BUG ID 33623 - Opening a certain script generated for a Hiero transcode caused Nuke to crash.

BUG ID 33663 - RotoPaint: Handles were offset while transforming Roto shapes when in down-rezmode.

BUG ID 33696 - Kronos/MotionBlur/VectorGenerator: Results differed depending on the number of cores used forrendering.

BUG ID 33796 - Mac OS X only: Switching the Viewer right-click Stereo Modes control away fromOpenGL stereomode and back again caused Nuke to crash onMacBook Pros with Retina displays.

BUG ID 33952 - The Relight example in theNukeUser Guide showed amisleading image.

BUG ID 34281 - A customer script displayed 'Shuffle.in: Can't select rgba.alpha; it conflicts with other selectedchannels' during rendering.

BUG ID 34332 - r3dReader: It was not possible to undo the changesmade by clicking Metadata.

BUG ID 34334 - r3dReader: Clicking Metadata did not update the label correctly.

BUG ID 34357 - Tracker: Lock-ups when adjusting translate or rotate values in a Transformupstreamof aTracker.

BUG ID 34495 - Dope Sheet: Attempting to scale three ormore keyframes at once caused the scale handles to getstuck when dragging.

BUG ID 34508 - GridWarp: Maintaining selection when switching between source and destination grids wasinconsistent.

BUG ID 34525 - Suppress bad channels was not working properly.

BUG ID 34617 - Deep: Crash opening a script with two HoldOuts and viewing the deep channel.

BUG ID 34664 - Deep nodes provided incorrect resolution information in expressions.

BUG ID 34725 - Assist: Splinewarp handles were not visible.

BUG ID 34770 - ModelBuilder: Connecting PoissonMesh node caused Nuke to crash.

BUG ID 34948 - Therewas no information on GeoReaderFormat in theNuke developer documentation.

BUG ID 35647 - BlendMat: Theblend control was always set to over when converting Deep data.

BUG ID 36110 - ReadGeo: Invalid vertex, uv, or normal indices in an .obj file caused Nuke to crash.

BUG ID 36133 - DeepRead: Leaving the _formatHint variable null caused theDeepRead plug-in to crash.

BUG ID 36249 - ColorLookup: Entering an x expression then viewing it caused Nuke to crash.

BUG ID 36523 - ZDefocus: Height did nothing in the size control.

BUG ID 36571 - Sony S-Log LUT in root LUTs and the Colorspace node did not take the black point offset intoaccount.

BUG ID 36673 - Kronos/MotionBlur/VectorGenerator: Results differed depending on the operating systemused.

BUG ID 36827 - Stereo: The Viewer didnt update correctly when switching between Single/Interlacedmodes.

BUG ID 37137 - RenderingmultipleWrite nodes simultaneously occasionally displayed a 'Reader did not setbounding box' error due to toomany open files.

BUG ID 37197 - Denoise: The Smoothness control was not scaled correctly.


13

BUG ID 37457 - ZDefocus: A customer script crashed when scrubbing in the Viewer at x1 zoom level when theZDefocus nodewas set to use CPU.

BUG ID 37981 - The crwReader leaked file handles, resulting in errors opening .cr2 files.

BUG ID 37996 - ModelBuilder: Right-click actions were applied to hidden objects.

BUG ID 38035 - DeepRead: Thediscrete and premultiply controls werewired up thewrong way around.

BUG ID 38440 - Alembic: Camera horizontal and vertical film back offsets were not measured in cm.

BUG ID 38549 - The right-click Set key on all knobs option caused buttons to execute.

BUG ID 38682 - Mac OS X Mavericks only: Creating a B-Spline in a Roto node caused Nuke to crash.

BUG ID 38705 - TimeOffSet didnt work with Deep data.

BUG ID 38725 - Alembic: Exports used Acyclic time sampling.

BUG ID 38751 - Alembic: Including custom information in .abc files caused Nuke to crash when reading the file.

BUG ID 38791 - Particles: The progress bar showed thewrong amount of progress with a ParticleSettings node inthe tree.

BUG ID 38806 - ZDefocus: The filter aspect ratio slider did not range from 0.5 to 2.

BUG ID 38873 - TheMatrix node's ? tooltip wasmisleading.

BUG ID 38914 - Alembic: Results from alembic cameras looked different in Nuke andMaya, unless you set anexpression on thewindow_translate.u control.

BUG ID 39001 - Alembic: Changing frame on exported particles caused Nuke to crash.

BUG ID 39209 - Mac OS X 10.9 only: The RotoPaint tools were slowwithmultiple strokes in the Viewer.

BUGID 39648 - ModelBuilder: Changing the separation value using the virtual slider caused Nuke to crash.

Known Issues and WorkaroundsThis section covers known issues and gives workarounds for them, where appropriate.

Known Issues Specific to 8.0

BlinkScript BUGID 39592 - Kernel parameters with spaces in their names do not work when the kernel is reloaded.

As aworkaround, remove any spaces in the parameter names. For example, change this line in the kernel:defineParam(showDetail, "Show Detail", false);

to thisdefineParam(showDetail, "ShowDetail", false);

BUGID 39485 - TheKernel Source text entry field currently loses focus when the cursormoves to another pane.


14

CameraTracker BUGID 39606 - Stereo: After placing User Tracks, clicking Autotrack does not track on the first frame.

BUG ID 39604 - The zoomwindow doesn't always update correctly whenmoving between frames.

BUG ID 39511 - CameraTracker cannot currently solve lens distortion on single frame.

As aworkaround, use the ProjectionSolver by pressing X in theNodeGraph and entering ProjectionSolver as aTCL command.

BUG ID 39509 - On theAutoTracks tab, clicking Delete Rejected does not remove all rejected tracks.

As aworkaround, you can remove the rejected tracksmanually by right-clicking them in the Viewer and selectingtracks > delete selected.

BUG ID 39507 - The enabled/disabled state of tracks in theUser Tracks table is inconsistent.

BUG ID 39506 - After solving the camera, theAlt+ previous/next keyframe hotkeys do not workfor User Tracks.

BUG ID 39505 -When a track is selected in the Viewer, no hover-over track info is available.

BUG ID 39501 - Increasing AutoTrack threshold controls do not currently allow rejected tracks to be included.

BUG ID 39215 - It is not possible to copy XYZ position values from theUser Tracks table unless the track ismarkedas a survey point.

BUG ID 39201 - Holding Shift and clicking User Tracks in the Viewer doesn't add to the current selection.

BUG ID 38381 - Drag selecting andmovingmultiple User Tracks is not currently possible.

BUG ID 38361 - In Source > Stills mode, tracking ignores theGlobal frame range specified.

BUG ID 37411 - Sequences containing an alpha channels display the alpha premultiplied by the image in referencethumbnails, rather than just the RGB values.

In-panel color picker BUGID 39373 - Modifying the value of the red channel affects green, blue, and alpha as well when the controls areexpression linked.

Dope Sheet BUGID 39426 - Undoing individually animated text characters removes their keys completely from theDopeSheet.

BUGID 39338 - Clicking theMove button for a selection and then undoing themove does not work as expected.

BUGID 39156 - Keys remapped with descending TimeWarp lookup curves don't snap to frameswhen frame snapis enabled.

BUGID 38910 - Keys fromViewer buffers not currently being viewed are still visible.

BUGID 38630 - Read and TimeClip representations disappear in theDope Sheet if they are set to have a non-empty frame expression.

BUGID 37869 - TheDope Sheet is not updated correctly when a Retime's speed control is animated.


15

BUGID 37815 - Multiple instances of the same clip within one AppendClip are only represented once in theDopeSheet.

EditGeo BUGID 38954 - The transformhandle of selections in the Viewer is not updated between frames on geometry withanimation baked into its vertices.

To update the transformhandle, toggle the axis alignment control between object and average normal.

BUGID 38699 - Changing the visibility of objects within an Alembic SceneGraph causes geometry to ignore theEditGeo node.

BUGID 38670 - Setting a keyframe can be slow to update the Viewer with the appropriate keyframemarker.

BUGID 36094 - Setting axis alignment to average normal displays the axis incorrectly on edge and cornervertices.

Import Nuke BUGID 38963 - Calling import nuke terminates the Python session if no applicable license is available.

Linux only BUGID 39537 - Using a Blackmagic Decklink Extreme 2 card causes Nuke to becomeunresponsive.

Mac OS X only BUGID 39429 - Crash Reporting: The 'save to' dialog is hidden behind the crash report dialog when you click Save

Report.

BUG ID 39350 - Mavericks only: Imported User Tracks are not currently added to the Viewer correctly.

Monitor out BUGID 37707 - Viewing 4k footage through a Blackmagic Design DeckLink 4k Extreme causes Nuke to crash.

BUGID 37700 - AJA Kona LHe+ 2K formats are not displayed correctly.

ParticleCache BUGID 39210 - Errormessages displayed when read from file is toggled on and off are not reliably cleared whenrendering through ScanlineRender.

Pixel Analyzer and Scopes BUGID 39479 - PixelAnalyser: Switching mode to full frame disables color picking for all color controls in Nuke.

As aworkaround, select mode > pixel selection before using the color picker.


16

BUGID 39180 - Scopes: Switching to a layout with a scopewindow, whilst rendering, forces the Viewer boundingbox to 1x1 for that frame.

BUGID 36508 - Scopes do not currently updatewhen zooming into the Viewer.

BUGID 36491 - Scopes clip color values between 0 and 1 when Preferences > Scopes > Include viewer colortransforms is enabled.

Python BUGID 39672 - Calling nuke.Layer() currently returns an empty list for built-in channels.

BUGID 39308 - Accessing a node's x and y positions using the xpos and ypos controls reports incorrect values.

As aworkaround, either call nuke.Node.xpos() ornuke.Node.ypos() first, or ensure no nodes are currentlyselected in theNodeGraph.

BUGID 38994 - nuke.Node.screenWidth() and screenHeight() are incorrect when a node is first created if ithas an autolabel.

BUGID 38591 - The update to Python 2.7 was not compiled with SSL support enabled.

QuickTime improvements BUGID 39405 - The ProRes422(HQ) codec with pixel format set to RGBA_16-bit (b64a) is currently reading inGamma2.2, rather than theGamma1.8 colorspace.

BUGID 38908 - Using the ProRes4444 codec with a pixel format of either YCbCrA 8-bit 444 Biased (r408) orYCbCrA 32-bit 444 Float (r4fl) does not produce the alpha channel correctly.

As aworkaround you can use either the RGBA 8-bit or RGBA 16-bit (b64a) pixel format.

ScanlineRender BUG ID 38329 - Deep renders from ScanlineRender currently ignore the ScanlineRender's bg input.

BUGID 38205 - Deep: Depth, motion, position, and normals information is occasionally incorrect in semitransparent areas.

BUGID 37967 - Deep: Geometry with alpha 0 renders black when the deep output is converted to an image.

Text BUGID 39556 - In text edit mode, it is not currently possible to edit text attributes when the Viewer overlay isdisabled.

BUGID 39552 - Transforming animation groups using an expression-linked Transformnode does not work asexpected.

As aworkaround, expression link the translate x and y controls separately.

BUGID 39483 - Highlighting text in themessage field and Viewer is not always synchronized correctly.

As aworkaround, scrub the playhead to a different frame to update the highlighted text.

BUGID 39414 - Text entry in themessage field occasionally requiresmultiple undo operations to remove text.


17

BUGID 39291 - Splitting the transform control on theGroup tab splits all controls.

BUGID 39271 - Japanese characters cannot be entered directly in the Viewer.

As aworkaround, enter characters using themessage field.

BUGID 39239 - Transforming a character generated from an expression, and then going to a framewhere thecharacter no longer exists, results in the transformation being lost.

BUGID 39130 - Splitting themessage field does not work as expected.

BUGID 38789 - Viewer toolbar controls steal cursor focus.

BUGID 38425 - The undo history becomes unreliable when the panel focus changes.

BUGID 37119 - Typing text in the properties panel message field always uses the default font settings.

BUGID 36372 - Selecting a TCL expression in themessage field doesn't always select the result in the Viewer.

Tracker BUGID 39200 - Holding Shift and clicking tracks in the Viewer doesn't add to the current selection.

BUGID 38356 - The zoomwindow occasionally doesn't update correctly when scrubbing between frames.

Windows only BUG ID 39394 - CameraTracker: Importing a User Track created on another operating system causes Nuke tobecomeunresponsive.

Exporting fromWindows to other operating systemsworks as expected.

BUGID 35800 - Scopes: The alpha channel doesn't update correctly whenmodified through a node, such asPrimatte or Shuffle, even after the node is removed from theNodeGraph.

Miscellaneous known issues BUGID 39651 - AddingMotionBlur after a Convolvewith no filter causes Nuke to crash.

BUGID 39637 - Adding a Transformnode downstreamof certain .exr Read nodes and enabling auto alpha orraw data in the Read properties causes Nuke to crash, if the the Transform is scaled on both the x and y axis.

BUGID 39557 -Writing .exrs with 200+ layers, when interleave is set to channels, can be sluggish.

BUGID 39459 - Virtual Sliders: Clicking the left mouse button, while holding down themiddlemouse button,pastes values into the control.

BUG ID 39407 - Project3D: The node class name has changed to Project3D2. As a result, theNukeMari bridgewon't work unless all instances of Project3D are renamed appropriately in themari_bridge.py file.

BUGID 39287 - Plug-ins: Loading scripts with plug-ins compiled against older versions removes the nodes fromNodeGraph.

BUGID 39165 - ReadGeo: When reading in .fbx files, the transform/scale state can become incorrect whilsttoggling the read transform from file in combination with all objects and/or read on each frame.

BUG ID 39122 - Switching the Viewer to wipe mode and wiping between inputs with different format sizes causescorruption and constant refreshing in the Viewer.


18

BUGID 38929 - File Browser: Items in the favorites/file list get highlighted incorrectly onmouse over.

BUGID 38713 - Capture: Roto opacity and feather settings are not included in captured images.

BUGID 35661 - Capture: Capturing the Viewer with a custom file path saves the file path in the script, resulting inerror when the path doesn't exist:Flipbook render failed: viewerCaptureOp: Cannot write to specified path

BUGID 35659 - Capture: Capturing a 3D scene containing lights produces Viewer flashes in the captured images.

BUGID 35614 - For EXR 2.0 files to be backwards compatible with earlier readers, the layer namesmust not exceed32 characters in length.

As aworkaround, open the .exr in Nuke 8.0 andmanually (or Pythonically) truncate the names to allow for legalbackwards compatibility.

BUGID 35611 -Writing .exrs with theWrite node's interleave control set to channels adds a superfluous mainview.

Other Known Issues

AudioRead BUG ID 18924 - Changes to the rate control value are not honored when ratesource is toggled between file and

custom.

BUG ID 18666 - Changing the sample rate has no effect on playback in a Flipbook.

BUG ID 18465 - The time range control doesnt limit the rangewhen an endtime is specified.

BUG ID 18451 - Flipbooking doesn't honor the time range knob.

BUG ID 18217 - Redo keyframe generation doesn't replace the keys.

BUG ID 18213 - Changing Draw Style in the Curve Editor or Dope Sheet doesn't redraw the curves correctly.

FrameCycler BUG ID 17199 - There aren't appropriate LUTs in 6.2v3 for flipbooking some colorspaces including rec709, Gamma1.8, Gamma 2.2, Panalog, REDLog, ViperLog and REDSpace. As aworkaround, you need to select Burn in the LUTin FrameCycler for an authentic color reproduction.

BUG ID 15204 - There are currently some graphical glitches occurring when flipbooking certain images. Theworkaround is to change the cache precision in FrameCycler. To do this, bring up the settingsmenu in FrameCycler(press S), go to Options > Cache and change theCache precision option to either 16 bit float or 8 bit int + 16bit float.

BUG ID 15046 - Flipbooking to FrameCycler with images greater than 4K in width, and with a non-1 pixel aspectratio, skews the images (in FrameCycler). This is an issuewith FrameCycler 2009, and we are awaiting a fix.

We direct FrameCycler to write to the users Nuke temp directory (NUKE_TEMP_DIR) for its user settings files. Youcan redirect this by modifying the FrameCycler/settings/Global_Settings.xml file that can be found within yourNuke installation.


19

Flipbooking with FrameCycler 2009 may not work on some older Intel and AMD processors with certain graphicscard configurations. You can set the FC_PATH environment variable to point to a previous version of FrameCycler(that is FrameCycler 2008 found in Nuke 6.0v7). For information on setting environment variables, please refer tothe Configuring Nuke chapter in theNukeUser Guide.

For example, you can point FC_PATH to the following locations (check the correct path to the installation on yourmachine):

Mac:

/Applications/Nuke6.0v7-32/Nuke6.0v7.app/Contents/MacOS/FrameCyclerOSX/bin/FrameCycler

Windows:

Program Files\Nuke6.0v7\FrameCycler\Windows\bin\FrameCycler.exe

Linux:

/usr/local/Nuke6.0v7-32/FrameCyclerCentOS4.4/bin/framecycler

NOTE: Please contact [email protected] if you need older versions of The Foundry software.

Linux only BUG ID 31431 - Linux only: The current version of the FFmpeg library used by Nuke reads the height of HD .movfiles at 1088, rather than 1080.

As aworkaround, use a Reformat node to force the input to the correct format.

Mac OS X only BUG ID 39288 - QuickTime: Limiting the number of helper processes, using the Preferences > QuickTime >

reader subprocess limit dropdown, can cause read errors.

BUG ID 38686 - Enabling UseGPU if available on supported nodes, such as Kronos, in more than one instance ofNuke at the same time, can cause display corruption and/or entire system freezes. This seems particularly likely tooccur on GPUswith low amounts of RAM, such as theGeForce GT 650M.

As aworkaround, only enable GPU acceleration in one instance of Nuke at a time.

BUGID 35123 - PrmanRender: If you're usingMacOS X 10.8 (Mountain Lion) or above, make sure X11 is installedon your system. Unlike previous versions of OS X, 10.8 and above do not have X11 installed by default.

Formore information, see http://support.apple.com/kb/HT5293.

BUGID 34697 - Launching Nuke from a network shared drive causes Nuke to crash on launch.

As aworkaround, either:

tarball the installation fromMacOS X and unzip it on the alternate file system (using NFS or Samba, dependingon source), or

using the command line, copy the installation fromMacOS X to the network location using the same filesystem as the destination.

BUGID 33970 - Using a node, such as Grade, as a custom viewer process outputs a blank Viewer.


20

As aworkaround, adjust the Viewer gain control to refresh the Viewer.

BUG ID 22062 - Nuke doesn't currently give the option to restore the autosave of an unsaved script, except whenNuke is run from the command line.

BUG ID 13638 - The following graphics cards are not currently supported forMac:

ATI Radeon X1600

ATI Radeon X1900

Users with these cards will be able to render from the command line, but in GUI sessions, theNodeGraph willrender incorrectly due to a requirement of OpenGL 2 drivers.

BUG ID 12048 - Nuke crashes if you activate screen sharing when there is no screen plugged in.

BUG ID 11776 - Node text appears aliased, unclear, or garbled at certain zoom levels.

ModelBuilder BUG ID 33053 - Using the Face Selection tool in the 3D Viewer disables the Scale handles (Ctrl/Cmd+Shift).

As a workaround, press F to fit the contents to the Viewer and thenmove the Viewer to a different angle beforeactivating the Scale handles.

Particles BUG ID 18268 - Enabling color from texture always renders a solid white alpha for the texture.

BUG ID 17520 - Geometry representation textures are displayed even when display is set to off.

BUG ID 17243 - Using sprites instead of geometry representations causes particles to render behind the 3D gridlines.

PlanarTracker BUG ID 33254 - PlanarTrackers Roto node defaults to the Select all tool rather than Bezier. If you click on theViewer, then change the tool and draw a shape, your shape is added to the root layer instead ofPlanarTrackerLayer1. Thismeans its not considered for tracking, and tracking fails.

Theworkaround is to:

make sure PlanarTrackerLayer1 is selected in the Roto properties,

change to one of the shape tools before attempting to draw in Viewer, and

in the Roto properties, make sure a purple rectangle appears in the PT column to indicate that the shape isconsidered for tracking.

BUG ID 19683 - After adjusting the planar surface using theCorrect Plane Viewer button, you have to undo twicefor the planar surface to return to its original position.

BUG ID 19563 - Detected or tracked features are not offset by the origin of the input image's bounding box.

To avoid this, you can add a Crop node before PlanarTrackers associated Roto node.

BUG ID 19240 -When Viewer downrez is greater than 1, the clearTrackDataForward button currently offsetsbezier shapes to fit the root format.


21

To return the shape to its original size and position, advance the sequence one frame.

PrmanRender BUG ID 27648 - After a security update forMac OS X, Nuke is unable to load the PrmanRender plug-in when in GUImode.

See http://support.apple.com/kb/HT5281 formore information.

As aworkaround, set the following environment variables:export RMANTREE=/Applications/Pixar/RenderMan.app/Versions/RenderManProServer-15.1

export DYLD_LIBRARY_PATH=$RMANTREE/lib

Then launch Nuke from the command line.

In theNuke camera, thewindow roll control is not yet mapped to RenderMan.

Python BUG ID 8063 - Creatingmany new nodes with nuke.createNode() and the in-panel argument at default (True)may crash when toomany node control panels are created too quickly. Theworkaround is to pass the in-panelargument as False or else usenuke.nodes.NodeClass() (whereNodeClass is the type of node to create) to createthe node and then connect it to the currently selected nodemanually.

BUG ID 6455 - You should not call the Python command nuke.restoreWindowLayout() from the Script Editor asthat can causeNuke to crash. Instead, you can use the same command from yourmenu.py, restore layouts byselecting Layout > Restore Layout, or use a custommenu or toolbar item.

Nuke sometimes reports errors in Groups and Gizmos, appearing similar to the following:

groupName.NodeName.knobname: unexpected 'k' in '0.knobname'

The problem ismost likely that there is an expression that is using the input TCL command and doesn't validatethat there is an input connected. An example expression:

[input parent 0].translate.x

The input command returns 0 when it can't find the requested input, which generates an expression of'0.knobname' that doesn't refer to anything. The fix is to restructure the expression to use the value TCLcommand and specify a default value to return in the case that the expression is invalid. It takes the form:

[value [input parent inputnumber].knob defaultValue]

Here is themodified example:

[value [input parent 0].translate.x 0]

Themodified example returns 0 in the event that there is no input 0, and no longer result in an errormessage.

There is a Python syntax conflict when assigning knob names on the fly with nuke.nodes.() if the knob iscalled 'in'.

For example, this gives a syntax error:

nuke.nodes.Shuffle(in = 'depth')

while this works because 'in' is a string here and not a keyword:

sh = nuke.nodes.Shuffle()


22

sh['in'].setValue('depth')

QuickTime ProRes 4444 BUG ID 17360 - Some customers have experienced unexpected shifts in chroma values when using the ProRes4444 .mov codec.

A possible workaround is to modify theGlobalSettings.csv found in the following locations:

NOTE: Please be aware that this workaround is not reliable in every case.

Mac OS X

/Applications/Nuke7.0v6/Nuke7.0v6.app/Contents/Resources/

Windows

C:\Program Files\Nuke7.0v6\

Add the following lines to the bottomof the .csv file:# Apple ProRes 4444

encode,ap4h,appl,any,any,512

decode,ap4h,appl,any,any,512

Render codecs

There have been issues where rendering with certain codecsmakes Nuke crash. Due to this, we recommend thefollowing:

If you're using the Sorensen Video codec, it's recommended you use the Sorensen Video 3 codec instead. If you'reunable to switch to Sorensen Video 3, try using a format smaller than 2K for better performance.

If you're experiencing crashes with CineformHD, try updating your Cineform codec to version 5 or above. Youmayneed to download theNeoplayer at http://estore.cineform.com/neoplayer.aspx.

If you're using Avid Meridien, you should only write out in NTSC and PAL.

Roto/RotoPaint BUGID 32459 - RotoPaint: Undoing a point move that created a keyframe doesn't currently undo the keyframecreation.

BUGID 32450 - RotoPaint Stereo: Attempting to undomulitple split-control transforms on the same shape revertsthe shape to its original position.

BUGID 31552 - Point handles for paint strokes, whose lifetime doesnt extend to the current frame, disappearwhen drag-selected.

As aworkaround, select the shape in the curves list to re-display the points.

BUGID 30920 - Expression linking extramatrices in the Transform tab doesnt work as expected.


23

NOTE: This also applies to SplineWarpmatrices.

BUGID 30551 - Several levels of smoothing applied to one shape are carried over to subsequent shapes for asingle smooth operation.

BUGID 29170 - The cut, copy, and paste keyboard shortcuts don't work for entries in the curves list.

BUGID 28838 - Gizmos fromNuke 6 containing Roto/RotoPaint nodes should be recreated in Nuke 8, but bear inmind that they wont be backwards compatible with Nuke 6 once converted, unless you follow the instructionsbelow:

Nuke 6 scripts containing Roto display a conversion prompt when you open them in Nuke 8:

Click Save As to convert the script to theNuke 8 Roto format, or

Click Ignore to load theNuke 6 format into Nuke 8. Youmight select this option if:

- You don't intend to make any changes, or

- You want to overwrite the file with a Nuke 7 and 8 only Roto format when saving.

If you want Nuke 8 scripts to load in Nuke 6, use the convertToNuke6 or convertDirectoryToNuke6 Pythonfunctions when running Nuke 8 in terminal only mode:

NOTE: The conversion functions cannot convert stereo-split curves as they are not supported by Nuke 6.

To convert individual .nk scripts:convertToNuke6(fromScript, toScript, overwrite = False)

To convert all .nk scripts in a given directory:convertDirectoryToNuke6(fromDir, toDir, matchPattern =.*\.nk, overwrite = False)

NOTE: The pattern is a regular expression.

An example single script conversion and rename to the same directory, from the command line (terminal):$ /Nuke8.0v1 -t

>>> import nuke.rotopaint

>>> nuke.rotopaint.convertToNuke6(/tmp/myRoto8.nk, /tmp/myRoto6.nk)

BUG ID 26855 - Theundo and redo buttons in the properties panel didnt work as expected and have beendisabled.

Theworkaround is to use the undo (Ctrl/Cmd+Z) and redo (Ctrl/Cmd+Y) hotkeys or the Edit menu instead.

BUG ID 11524 - Adding strokes/shapes in RotoPaint is slowwhen there is another RotoPaint after it.

BUG ID 9238 - Painting onMacOS X and Linux is slower when the paint cursor is near the edges of the screen.

The foreground onion skin overlay updates as you paint. This will change so the overlay only updates with the newstroke on pen up.

It is not currently possible to clone RotoPaint nodes.

Interactivity of laying down strokes/shapes in the Viewermay be faster whenmotion blur is disabled on the layeryou areworking in.


24

Tracker BUG ID 39225 - Moving tracking anchors is occasionally unresponsive and jerky.

BUGID 32353/32359 - Right-clicking on a point in the Viewer doesnt always update the available Link to >Tracker linking dialog or Tracker options.

As aworkaround, close and re-open the Roto/RotoPaint Properties panel to update the Link to menu.

BUGID 30116 - Adding tracking anchors with an OFlow node upstreamof the Tracker causes Nuke to becomeunresponsive.

BUGID 29382 - Tracking keyframeswith different sized patterns doesnt work as expected.

As aworkaround, keyframe patterns should, where possible, be of comparable sizes.

Warpers BUGID 32340 - SplineWarp: Ctrl/Cmd drag-creating rectangles and ellipses doesn't display an overlay until pen-up.

BUGID 32083 - SplineWarp: Deleting all but one point on a curve resets its correspondence points to 0,0, whichcannot be undone.

BUGID 32082 - SplineWarp: Correspondence points are too sensitive to when control points are removed.

BUGID 32079 - SplineWarp: Moving correspondence points on curves with no keyframes cannot currently beundone.

BUGID 30429 - SplineWarp: Transform links are not maintained when the source curve ismoved to a new layer.

BUGID 31322 - SplineWarp/GridWarp: Preview doesn't handle upstream transforms correctly.

BUGID 20000 - GridWarp: When using cropped input, moving control points causes the Viewer to display thecropped image and the black area between the crop box and the format whenmerged over a background.

BUGID 19995 - GridWarp: Locked source and destination grids still allow adding and removing grid lines.

BUGID 19835 - SplineWarp/GridWarp: The Viewer LUT is incorrect in morph mode, when mix is set at anintermediate value.

BUGID 19755 - SplineWarp: Placing correspondence points at each end of an open spline causes renderingproblems.

BUGID 19565 - GridWarp: The Viewer does not show the correct mix amount when in morph modewith mix setat an intermediate value.

BUGID 19386 - GridWarp: All keyframes are removed from theDope Sheet after undoing, rather than just thelatest, and the keyframes remain on the timeline and in the Properties pane.

BUGID 19148 - SplineWarp: Rendering fails if a curve is reduced to a single point.

BUGID 19079 - SplineWarp: TheC hotkey does not currently select theAdd Correspondence Point tool.

BUGID 18712 - GridWarp: The timeline currently shows both source and destination keyframes, even if a grid isnot visible in the Viewer.

BUGID 18709 - GridWarp: Rotating the transform jack with both grids selected, but in different positions, does notundo as expected.

BUGID 18342 - SplineWarp: The spline keyframe + button does not add keys to the Curve Editor or Dope Sheet.


25

BUGID 18304 - GridWarp: Existing control point keyframes are not cleared when you draw a new grid using theDraw Boundary Viewer button.

BUGID 18019 - GridWarp: You cannot select all grid points in the Curve Editor using Ctrl/Cmd+A shortcut.

BUGID 18012 - GridWarp: The grid can flicker between white and grey when zooming in and out of the Viewer,particularly when the grid is subdivided.

BUGID 17697 - GridWarp: In stereomode, the right view is labelled as default when you split controls intoseparate views.

Windows only BUGID 35284 - Exiting Nuke can be unacceptably slow, causing issues for render farms.

Set the environment variable NUKE_USE_FAST_ALLOCATOR to 1 to workaround this issue.

BUGID 30903 - Some scripts render significantly slower onWindows than on Linux.

Set the environment variable NUKE_USE_FAST_ALLOCATOR to 1 to workaround this issue.

BUGID 28921 - Changing the 3D selectionmode does not update until you click in the Viewer.

Miscellaneous known issues BUG ID 39365 - The Viewer properties headlamp control can not currently bemanaged using expression links.

BUG ID 39260 - Custom knobs on Groups and NoOp nodes cannot be retimed.

BUGID 35976 - SomeCUDA code runs in rendermode, even when the --gpu argument is omitted.

You can disable all CUDA code by setting the FN_NUKE_DISABLE_CUDA environment variable to 1.

BUGID 33863 - FBX geometry: Faces on geometry read in from .fbx files are not connected to neighboring faces,leaving gaps in certain circumstances.

This issue is particularly visible when using the EditGeo node, which should not allow you to remove faces from thegeometry.

BUGID 32856 - PositionToPoints: Textures occasionally disappear during playback or whenmousing over theViewer.

BUGID 32666 - FrameHold nodes have no effect on Deep nodes.

BUGID 32628 - DeepToPoints: Command line rendering appears to calculate renders even when render is set tooff.

BUGID 32497 - The R3D parameter labels in Nuke arent entirely consistent with REDCINE-X and Hiero.

BUGID 32219 - DepthToPosition: Reading depth information from the same layer as the output layer producescorrupt output.

As aworkaround, shuffle the depth information to an alternate layer.

BUGID 32118 - Card3D: When motionblur is enabled in the properties panel, FrameHold and TimeOffset nodesare ignored when connected to the cam or axis inputs.

BUGID 31803 - Using Shift+drag on a controls animation icon only copies the value for the current frame, not theentire expression.


26

BUGID 31714 - In the Viewer settings, enabling 3D > show_prim_bbox does not display individual boundingboxes for polymesh primitives.

BUGID 31310 - TimeOffset: Checking reverse input doesnt affect cameras, lights, or axes.

BUGID 31238 - RAM cache: Any action that changes a frames hash value, its unique identifier, causes the cache torelease. Actions such as adjusting the ViewerGamma, Gain, or channels dropdown affect the frame hash.

BUGID 30502 - Copying and pasting spline keys does not work as expected in theDope Sheet.

NOTE: This known issue only applies to Roto and SplineWarp keys.

BUGID 30256 - Script Editor: Flagging a control as invisible using setFlag() is not honored when the node iscopy/pasted in theNodeGraph.

BUGID 30173 - Manipulating 3D handles in the 2D Viewer is unreliable.

BUGID 29677 - Connecting a FrameHold node to an animated Camera and connecting both to a Scene node onlydisplays the animated Camera in the Viewer. There should be two cameras: one static and one animated.

BUGID 29083 - Using Create Camera in the 3D Viewer only sets position and rotation. The focal length of thenew camera does not match that of the Viewer camera.

BUGID 29048 - OCIO: Using the ocionuke library in terminalmode results in an error.

BUGID 28291 - Nuke crashes on startup if thedisk cache location set in the Preferences is no longer available.

BUGID 27211 - Alembic: The state of the Viewer Lock Frame control is not always honored for .abc files.

As aworkaround, ensure that ReadGeo > read on each frame is enabled.

BUGID 21663 - Read: After reading in a stereo/multiview .exr file and choosing not to add new views to theproject, subsequent reads of any stereo/multiview .exr files wont give the option to add new views.

BUGID 20431 - CameraTracker: Its not possible to pick colors in the Viewer with the control panel open.

BUGID 20204 - Multitexturing: When Preferences > Viewers > Multiframe is enabled, increasing downrez inthe Viewer toolbar can cause textures to flicker in the 3D Viewer.

You can switch back to Classic mode or avoid using proxy in 3D to workaround this issue.

BUGID 19933 - ReadGeo: Geometry occasionally doesn't display as a solid until you click in the Viewer.

BUGID 19185 - Attaching an FBX ReadGeo to the Viewer occasionally causes a slight graphical glitch in theProperties pane.

BUGID 18649 - The transform jack is currently scaling incorrectly from the corner pivot point.

BUGID 12505 - Motion Vector output has been improved, but still doesn't work properly because some largepolygons are clipped by the front camera plane.

You canminimize this effect by increasing the geometry tessellation max parameter.

BUGID 12424 - Ultimatte: Overlays are not updating correctly or reverting when panning or zooming.

BUGID 11620 - In the 3D Viewer, there is currently a conflict between 3D geometry selection and points drawnwith RotoPaint. This only occurs if you have two Viewers open, one in 2D mode and the other in 3D mode, and youhave the panel for the RotoPaint visible.

BUG ID 9521 - Currently, theNuke Viewer cannot cache very large plate sequences in float. The limit per frame is50MB. If your frames are larger than this, youmay need to switch to proxy mode for the caching to work.


27

BUG ID 5922 - At themoment, cloning does not work properly with all OFX nodes. This affects, but is not restrictedto, any nodes that have an analysis pass.

BUG ID 5690 -Windows run-time libraries are not packaged properly with Nuke.

Nuke runs correctly from a network install onWindowswithout specifically installing the run-time libraries, thoughwe still recommend that you do so as therewill still be someminor problemswithout them. For details, please seeInstallation on Windows in the Installation and Licensing chapter of theNukeUser Guide.

BUG ID 5083 - Flipbooking the output of the Anaglyph node asks which view you want to render. This question isunnecessary as the result is an anaglyph image. Irrespective of what view you choose, the flipbook output is thesame.

File types inWindows andMacOS X are associated with the standard version of Nuke by default, so if you save ascript on NukeX using features that are only included in NukeX (such as CameraTracker or FurnaceCore) and thendouble-click on the script icon to open it, it will open in standard Nuke instead of NukeX.

If you have troublewith FBX files, it may be because they werewritten with an older version of FBX. If they loadvery slowly, it is also possible that they are ASCII rather than binary. To get around these problems, you can use theFBX converter on the Autodesk web site. It converts between various different formats, including older FBXversions, ASCII, and binary, and is available onWindows, Mac OS X, and Linux.

To download the FBX converter:

1. Go to http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855.

2. Scroll down to FBX Converter and click on one of the links to start the download.

CameraTracker: Canceling lens distortion initialization results in corrupt tracks.

3D Camera: If you want to navigate through the 3D point cloud created by the CameraTracker nodewhen usingCreate Scene:

Select the Camera that was created in the 3D viewwhen using theCreate Scene button.

Press F to focus on the selected Camera. You can now navigate around the cloud. Do not try to focus (using F) onthe point cloud. The resulting tumble cameramovement is likely to be jumpy.

Plug-ins installed using theNuke Plug-in Installermay not work correctly as they were complied against an earlierversion of Nuke.

Developer NotesHere are the changes relevant to developers.

NOTE: SeeHelp > Documentation from theNukemenu bar formore information.

New Features Nuke now includes the Blink API enabling you to use the Blink framework inside an NDK plug-in. Formoreinformation, see the following resources:


28

The Blink API: Available from aNuke install in /Documentation/Blink/index.html

Blink Kernels: http://docs.thefoundry.co.uk/nuke/80/BlinkKernels/

Feature Enhancements BUG ID 39309 - You can now access private variables to subclasses of NukeWrapper.

Bug Fixes BUG ID 15737 - nuke.Node.screenWidth() and screenHeight() were zero when aNoOp nodewas first created.

BUG ID 21471 - Calling nuke.cancel() in aWrite nodes beforeFrameRender field produced corrupt output whenwriting .exr files.

BUG ID 26136 - Calling nukescripts.create_read() didnt detect deep sequences as deepRead.

BUG ID 28510 - Calling nuke.menu('Nodes').shortcut() caused Nuke to crash.

BUG ID 29712 - RotoPaint: Calling _curveknob.Layer.insert() inserted in thewrong location.

BUG ID 32947 - Setting viewswith Python returned no result when deleting all of the views, then add a single view.

BUG ID 33310 - Calling nuke.cancel() in aWrite node did not cancel the current render operation when writing.exr files.

BUG ID 33872 -Windows only: ZDefocus and Convolve FFTs were single-threaded.

BUG ID 34003 - Calling nuke.localiseFiles caused Nuke to crash.

BUG ID 34337 - Calling File_Knob.evaluate caused a segmentation fault with view=None.

BUG ID 36273 - Calling nuke.root().setName( name ) crashed Nukewhen a script didnt have a name.


Release Notes for Nuke 8.0v1Release DateQualified Operating SystemsRequirements for GPU Acceleration

New FeaturesFeature EnhancementsBug FixesKnown Issues and WorkaroundsKnown Issues Specific to 8.0Other Known Issues

Developer NotesNew FeaturesFeature EnhancementsBug Fixes

nuke 8.0v1 releasenotes

Documents