Limitations and Known Issues

GPU

Complicated kernels can cause driver timeouts on the GPU if they take too long to execute. The lower the specification of your GPU, the more likely this is to happen.

Note:  For more information on GPU support, see the Release Notes for your version of Nuke.

Vectorization

Vectorization will attempt to optimize Blink kernels on the CPU with SIMD instructions. This may result in noticeably longer compile times for very large kernels, and there is no guarantee that your code will be vectorizable.

Crashing and Infinite Loops

Since the BlinkScript node allows arbitrary code to be written and run, it is possible to either crash or lock up Nuke. The BlinkScript node does not check your code to make sure it is sensible before running it, so we advise you to use caution!

To prevent crashes caused by out-of-bound memory accesses, turn on the Safety Rails option in the Kernel Parameters. When this option is enabled, additional code is generated to check for, catch and safely handle these out-of-bounds accesses, which are a common cause of BlinkScript crashes.

When you recompile the BlinkScript Kernel, full error messaging is logged in the Nuke terminal and the BlinkScript Editor Error Accordion to assist with debugging. See Editing Kernels for more information.

Tip:  Tip: It is recommended to enable Safety Rails during development and to disable once complete.