ID 335929 - Altering the Localization custom directory in Nuke 11.1v2, localizes the media to the default Nuke temp directory location and not the specified custom location.

Follow

Problem summary
It is possible to create a custom localization directory within Nuke. This can be achieved by adding the new directory to the 'localize to' field in 'Preferences > Performance > Localization'. By default this is set to your nuke temp directory in a folder called 'localize'.

Within Nuke 11.1v2 releases, if this directory is changed it will still localize to the default nuke temp directory.

This issue only occurs in Nuke 11.1v2 releases and is present in all three major operating systems and works correctly in Nuke 11.1v1 and earlier releases.

Customer reported version
nuke.11.1v2

Customer reported platform
MacOS 10.12

Steps to reproduce

1) Create a new Nuke script in Nuke 11.1v2

2) Navigate to Edit > Preferences > Performance > Localization location and change the 'localize to' directory to a custom location of your choice. Before clicking 'Ok' ensure that 'mode' is set to 'on' under System area.

3) Read in a single frame of footage

4) In the Read node properties bin, select the 'localization policy' and set to 'on'
This will create a green bar on the Read node, which indicates that this is localised

5) Navigate through the file explorer to the localised location you set 
Result: Localized file does not exist

6) Repeat steps 1-5 in Nuke 11.1v1
Result: File correctly localized in directory

Workaround
Unknown.

Reproduced by support

This bug has been reproduced in:
Nuke 11.1v2 - Windows 7 - MacOSX 10.13 - CentOS 6.9 - regression

Unable to reproduce bug in:
Nuke 11.1v1 - Windows 7 - MacOSX 10.13 - CentOS 6.9

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

Expected behaviour
When changing the directory for the localization, the file set to be localized should be written to the custom directory

Actual behaviour
When changing the directory for the localization, the localization is still set to go to default nuke temp directory location

    We're sorry to hear that

    Please tell us why