How do i get Nuke Apps to show up inside nuke

Hi, I have recently installed nuke writenode app and the nuke multi-setframerange app on a project, but for some reason, they do not show up inside nuke. The default file manager works fine however.. I have also added the toolkit to the init.py, as sugested in the write node  instructions (but i m not sure if I have done this correctly.

How do I install this correctly?


  • 0
    Manne Öhrström

    Hello Philippe!

    Great question! I think what may be a bit confusing here is our default configuration (something we are working on making more intuitive!). As you have probably discovered, the configuration is split into several environments, each containing a list of engines and apps. The idea with environments is that you should be able to have one suite of apps for the rigging department, one for the shot pipeline, one for lighting etc. It is quite configurable and allows you to fine tune your workflows!

    The default configuration is organized on a per pipeline step level. Pipeline steps are also known as "task types" in Shotgun, so will typically be something like modeling, lighting, layout etc. Often, pipeline steps will match up with the different departments in a studio. For this reason, the default config is broken down per step, so that there is one folder in the file system for each pipeline step, effectively separating out the publish and work areas for different departments. 

    With this structure, it would also be totally possible to set up one environment (which its unique configuration settings and collection of apps) for lighting, one for layout etc. We stopped short of creating one environment for pipeline steps belonging to assets and one for pipeline steps belonging to shots. This is the level where all the work and publish area take exists, and these environments contain the main payload of different apps. These environment files are called asset_step.yml and shot_step.yml.

    In addition to these, there are a number of "transfer" environments, for example project, shot and asset. These environments don't have matching work and publish areas in the default config, but they only contain the "Shotgun File Manager" app. In our default config, these environments exist so enable an artist to reach their actual work environment where all the apps are. This may be a case of going from a shotgun task and launching straight into the pipeline step-level environment, or it may be the case of launching Maya for a Shot or a Project and then using the Shotgun file manager inside of Maya to choose a task and thereby navigating to the asset_step or shot_step environment where the work takes place.

    Please note that this is the default config setup only! - Toolkit is flexible and can be set up in many different ways.

    Now, to answer your question (sorry for the long preamble!) - which environment did you install into? My guess would be that the environment you are starting in Nuke may not be the same environment that you installed the new apps into? You can check your environment info by starting a Shotgun UI (for example the shotgun file manager) and hovering your mouse over the top right corner of the window where it tells you the current project, shot etc. This will show a larger tooltip with environment and context information.

    Hope this helps! Let me know if you want further assistance!


  • 0
    Philippe L

    hey, thx for the answer, I didnt reallise there were diffrent environements since we only use it from a compositing perspective. I ll try this out as soon as I get back from holiday.




  • 0
    Manne Öhrström

    Great! Let us know how it goes! 

Please sign in to leave a comment.