Create a ticket

Q100172: NUKE viewer performance issues on OSX El Capitan



If you are running Nuke on OSX El Capitan (OSX 10.11) then there is a chance you may encounter some performance issues with NUKE's viewer.

This article covers how you can enable some experimental bug fixes in NUKE 10 to avoid these problems. 



After OSX El Capitan was released we became aware of viewer performance issues when zooming or moving overlay elements (such as roto widgets or transform jacks). The engineers worked to fix these issues ahead of the NUKE 10 release but unfortunately the fixes were non-trivial and it wasn't possibly to safely fix these bugs without causing other issues in time for the NUKE 10 release.

Work is ongoing on these fixes but due to these open issues El Capitan is not a fully certified platform for NUKE. This remains a high priority for the Nuke team and we hope to be able to fix these issues in a future maintenance release. This article will be updated when we have more news to share.

It is currently possible to turn on the work in progress bug fixes for the El Capitan issues by setting a couple of environment variables for NUKE 10. Please note, these environment variables enables are experimental so please take caution if you need to use them in production.

The changes the engineers have made so far can be enabled by setting the following environment variable before running Nuke:


There is also an additional environment variable that can be set to increase the rate at which viewer widgets are redrawn (60 is the maximum it can be set, numbers above this won't show any additional improvement):


How to set the Environment Variables

To test these variables in a single NUKE session you can set the variable in a Terminal and then launch NUKE from the same terminal by doing the following:

1. Open the Terminal application.
2. Type:


3. Press Enter.
4. Launch Nuke from the same terminal by using:


* If you would like to launch Nuke X add --nukex to the end. For Nuke Studio add --studio i.e.

Please follow the same steps to set the second environment variable for testing, before launching NUKE.

Please note this method will only set the variable for any NUKE sessions launched from the same Terminal window.  Once the Terminal window is closed the environment variable will be lost and you'll have to set it again in a new Terminal window.

Please see Q100015: How To Set Environment Variables for instructions on how to set a variable so that it is always picked up.

Keywords: Nuke, El Capitan, OSX 10.11, viewer

Was this article helpful?

We're sorry to hear that

Please tell us why
1 out of 1 found this helpful