State:Closed|icon_bug|icon_nuke|database:public|Resolution:Fixed|TargetRelease:11.1v1|BugID:306164|
Problem summary
When using the 'Rolling Kernel' example from the online Blink reference documentation within a BlinkScript node, Nuke will freeze or create incorrect results (depending on OS) when you copy, paste or publishing the BlinkScript node.
https://www.thefoundry.co.uk/products/nuke/developers/100/blinkreference/image_rolling_kernels.html#rolling_kernel_example
Customer reported version
nuke.11.0v1
Customer reported platform
centos7
Steps to reproduce
1) Create a 'BlinkScript' node
2) Go to the blink reference documentation (linked above) and copy the text into your clipboard
3) Open the properties of the 'BlinkScript' node and click 'Clear' below the Kernel file
4) Open the 'Kernel Source' cascade and paste in the code from your clipboard
5) Click on 'Recompile', you will see this change the name of the BlinkScript name to 'RollingBoxKernel::dst' in the node
6) Save the Kernel file, you can do this by going to a directory using the folder icon and making a file called 'KernelTest' and clicking 'Save' (no extensions needed)
7) Copy the 'BlinkScript' node and paste it or 'Publish' it.
Result: Freezes in Windows/Mac, incorrect results in Linux.
Workaround
Unknown
Reproduced by support
This problem has been reproduced on:
Nuke 11.0v1 - CentOS 6.9 - Windows 7 - MacOSX 10.12
Nuke 10.5v5 - CentOS 6.9
Nuke 10.5v1 - CentOS 6.9
Nuke 10.0v6 - CentOS 6.9
Nuke 10.0v1 - CentOS 6.9 - Windows 7 - MacOSX 10.12
Nuke 9.0v9 - CentOS 6.9
Nuke 9.0v1 - CentOS 6.9
Nuke 8.0v7 - CentOS 6.9
Nuke 8.0v1 - CentOS 6.9 - Windows 7 - MacOSX 10.12
Independent OS results:
Windows 7 - Freezes in all releases
MacOSX 10.12 - Freezes in all releases
Centos 6.9 - Freezes pre Nuke 10.0v1 releases and in post Nuke10.0v1 releases it creates a node with no input and the name of '0'
Earliest version tested
Stopped testing at Nuke8.0v1 as BlinkScript did not exist.
Expected behaviour
Rolling Kernel example in the documentation should not cause errors once copied or published
Actual behaviour
Rolling Kernel example in the documentation causes freezing and incorrect results when copied or published
We're sorry to hear that
Please tell us why