ID 138535 - The .vf LUT doesn't match when written out and read back into Vectorfield.

Problem summary
The .vf LUT doesn't match when written out and read back into Vectorfield.

Customer reported version
Nuke11.1v1

Customer reported platform
macOS 10.12.1 Sierra

Steps to reproduce:
1. Add a CMSTestPattern node with a small size (e.g. 5) to make the effect obvious;

2. Add a GenerateLUT node and write a null LUT (nothing between CMSTestPattern and GenerateLUT) in .vf format;

3. Add a Vectorfield node with the generated LUT.

4. Toggle the viewer between the original CMS pattern and the one processed through the "null" LUT.

Workaround:
There is no current workaround at this time.

Reproduced by Support in:

Nuke 11.3v1 - Windows 10, CentOS 7, macOS 10.13 High

Nuke 11.2v1 - Windows 10

Nuke 11.1v1 - Windows 10

Nuke 11.0v1 - Windows 10

Nuke 10.5v1 - Windows 10

Nuke 10.0v1 - Windows 10

Nuke 9.0v1 - Windows 10

Nuke 8.0v1 - Windows 10, CentOS 7, macOS 10.13 High Sierra​

Earliest version tested:
Nuke 8.0v1 - This issue appears to be in all versions of the product

Expected behavior:
The Generated LUT should match the original transform.
 

Actual behavior:
All color values are multiplied by n/(n-1) compared to the result of the original transform as n1.