ID 225562 - Nuke won't render mov32 codecs to a network drive that has been mapped multiple times

Problem summary
Mov32 codecs won't write to a network drive that has been mapped multiple times. So if you map two different directories on the same network drive to different letters, then only the lowest letter drive can be written to. When writing to a higher letter drive, the temp file is written to the lower letter drive, then Nuke cannot find it.

Customer reported version
nuke.8.0v5

Customer reported platform

Windows

Steps to reproduce

1) On a Windows machine, open My Computer/This PC
2) Disconnect all mapped network drives pointing to {drive}
3) From the top menu, select Map Network Drive

4) In the dialogue, set the Drive to a lower letter, like A or B, and set the Folder to: {drive}\mapTest\LowerDrive, then press Finish.

5) Map a second drive, this time with a higher letter than the first drive, like X or Y, and set the Folder to: {drive}\mapTest\HigherDrive, then press Finish.

6) Open Nuke

7) Create a CheckerBoard node and attach a Write node to it

8) In the file knob of the Write node, set it to the higher mapped drive as a .mov file

9) Set the codec to H264, or any other mov32 codec, and try exporting. It will fail with the message: Write1: Couldn't open file

10) In Windows Explorer, if you navigate to the lower letter mapped drive, you will find a Nuke temp file the Write node couldn't find.

If you try rendering to the lower mapped drive, then it will write correctly.

If you try rendering using the full path, rather than the mapped drive, then it will work correctly.

{drive}/mapTest/LowerDrive/test.mov --- Works

A:/test.mov --- Works

{drive}/mapTest/HigherDrive/test.mov --- Works

Y:/test.mov --- Doesn't work

Workaround

Use UNC paths, so use the full path, and not the mapped drive path

Reproduced by support
The issue had been reproduce on:

Nuke 10.0v3 - Windows 10

Nuke 10.0v1 - Windows 10 

Nuke 9.0v9 - Windows 10 

Nuke 9.0v1 - Windows 10 

Nuke 8.0v6 - Windows 10 

Expected behaviour
For Nuke to be able to write mov32 codec files to network drives which have been mapped multiple times

Actual behaviour
It error-ed saying: Write1: Couldn't open file as the temp file was written to the wrong place