34 Matching Annotations
  1. Mar 2025
    1. Panels

      There's new user prefs for Timeline now

      Frame step size - How many frames to step at a time int he timeline Label mode - How to define labels on the timeline. Either Timecode, Frame number or No Labels

    1. Filter Nodes

      Missing our "Depth of Field" nodes here, which is:

      A real-time depth of field node which requires a colour image and a depth image. This is most suitable for use with a camera override, to add a cinematic depth of field effect.

    1. OCIO Colorspace Converts images from one colorspace to another. OCIO Display Applies a colorspace conversion t to a image sequence. OCIO File Transform Applies a colorspce conversion

      These nodes have been moved to their own OCIO section, and there are two additional nodes -

      OCIO CDL Transform OCIO CDL File Transform

      These nodes are equivalent to the Nuke OCIOCDLTransform node when combined, but are split up here for technical reasons. Reach out to me if you need more info on them

    1. , but can be influenced using the PipelineSortBias property on graphs and cameras, and PipelinePhase on graphs.

      As mentioned elsewhere, these options are now gone, so it's sufficient to say that this isn't editable and is fully automated.

    1. Pipeline sort bias PipelineSortBias 0 Influences the ordering of this pipelineable object within its pipeline phase. Objects are sorted by bias first (lower bias earlier), and then by where they are in the overall list of all objects of their type. Pipeline phase

      Both these settings have been removed

    1. Inputs and Controls

      You can also define the OCIO Display-view transform from here now. Specifically you can:

      Enabled (tick box, default unchecked) Display-view transform (default "sRGB - DIsplay | ACES 1.0 - SDRVideo") Invert (tickbox, default unchecked) Saturation (0-2 value, default 1)

    1. Testing Your Scene

      I realised there was an additional feature that went in a while back that we need to add here (apologies my mistake I must have missed it). It's an app notification panel that appears in the top right of the SM beside the projects list.

      It is essentially just a notification panel which will let the user know critical problems and important feedback. It will have much less info than the log panel, but you can link from the app notifications to the logs to get more detail if needed

    1. .

      Can we add another small line after this (which isn't another step, just more info).

      After the initial node creation, to select those nodes that were created for a USD object, right click in the scene graph and click "Select linked nodes".

    1. The project must currently be playing on the timeline to see the live image in the Image Viewer. If playback is stopped or paused the viewer won't update.

      This can be removed, it's no longer true

    1. It is recommended to use the latest version of Nuke for asset preparation.

      Can we change this to the below: We can keep the mention of Nuke 15.0 after but we want tot set 16.0 as the minimum recommendation.

      "It is recommended to use the latest version of Nuke for asset preparation, and the minimum recommendation is Nuke 16.0."

    1. .

      Another section on visibility would be good here. Something like:

      You can click on the eye icon to toggle visibility for a USD object. If an object is set to be invisible, all object children will inherit that invisibility. To toggle the visibility of the entire scene, click on the eye icon in the graph header.

    1. This is determined automatically based on overrides, but can be influenced using the PipelineSortBias property on graphs and cameras, and PipelinePhase on graphs.

      This feature was improved so pipelinesortbias and pipelinephase no longer exist. We can state something like:

      This is not editable and is determined automatically.

    1. Where are licenses needed?

      I mentioned before that licensing will be changing for Release. However the build we will be giving out after NAB will be using the old system so this is fine, but I wonder if we should mention something like:

      Licensing will be changing to a Render Node based approach upon Release.

    1. .

      Just to be clear, I would change it to the below (or something similar) just in case people think they only need to do it on the control machine.

      During installation, it is also recommended to add the Nuke Stage Listener shortcut to your Windows startup app on all machines used for Nuke Stage.