Q100199: Slow performance/UI freezes when working with scripts that contain Tracker nodes



Nuke frequently becomes unresponsive for a few seconds and is slow to work with, when scripts contain tracking nodes like Tracker, PlanarTracker or CameraTracker.



This problem is often caused by Nuke’s autosave functionality and the freezes coincide with the autosave frequency.

Tracking nodes generate a lot of data causing the file size of scripts to grow very large.

During autosave, this data has to be processed and written to disk. While this is happening, Nuke can sometimes run slow or become unresponsive.



If you are experiencing a similar behaviour, please try turning off Autosave under Edit > Preferences... > General > Autosave by setting "idle comp autosave after" and "force comp autosave after" to 0 seconds.

If you don't want to turn autosave off completely try a setting that will save less frequently than the default 5 or 30 seconds.


If this doesn’t stop Nuke from becoming unresponsive, the UI freezes might be related to the Tracker node generating keyframe previews, detailed in this article: Q100200: Slow performance when "Reading Keyframe Previews" of Tracker nodes


If you are still seeing any issues after performing the steps outlined in this article, then please open a Support ticket and let us know the issue you are encountering and the troubleshooting steps you have taken so far.

For more information on how to open a Support ticket, please refer to the Using the Support Portal article.

    We're sorry to hear that

    Please tell us why