ID 383268 - LensDistortion2 Filters replaced with LensDistortion1 filters

Follow

Problem summary
In Nuke 11.3, the LensDistortion2 node restored the filters to be the same as the original LensDistortion1 node, from Nuke 10.5.

The LensDistortion2 node was added in Nuke 11.0, but with a different set of filters. 
The filters were changed to match LensDistortion1, however, it should not have broken backwards compatibility.

The filters should have been added to the LensDistortion2 filter list, and not remove the ones which were already there.

Below is a comparison of the Filters per version:

Nuke10.5v7



Nuke11.2v5 ( Regression )


Nuke11.3v2 


Customer reported version
nuke.11.3v2

Customer reported platform
n_a_linux

Steps to reproduce

1) Open Nuke11.2v5

2) Within Nuke11.2v5, create a LensDistortion node and set the filter to 'Bilinear'

3) Save and exit Nuke.

4) Open Nuke11.3v1 or later.

Result: This issue will display an exception Window if a Nuke11.2v5 saved script includes a LensDistortion node with Bilinear filter settings


Workaround
Unknown

Reproduced by support

This bug has been reproduced in:
Nuke11.3v2 - Windows 7 - Mac10.13 - CentOS7
Nuke11.3v1 - Windows 7 - Mac10.13 - CentOS7 - regression

Unable to reproduce bug in:
Nuke11.2v5 - Windows 7 - Mac10.13 - CentOS7

Earliest version tested
- This issue no longer appears in this version and has regressed

Expected behaviour
LensDistortion2 node should contain filters from both nodes to provide backwards compatibility.

Actual behaviour
The LensDistortion2 filters have been replaced with the LensDistortion1 filters.

    We're sorry to hear that

    Please tell us why