ID 372224 - The NUKE_EXR_TEMP_NAME environment variable does not match the naming convention of .exr temporary files to the naming convention of .dpx temporary files

Problem summary
The NUKE_EXR_TEMP_NAME environment variable does not match the naming convention of .exr temporary files to the naming convention of .dpx temporary files.

Currently, .dpx sequences are written out like so:

Whereas, with the NUKE_EXR_TEMP_NAME environment variable set, .exr sequences will be written out like the following:

Customer reported version
Nuke 11.2v4

Customer reported platform

Windows

Steps to reproduce

1) Set the following environment variable on your system NUKE_EXR_TEMP_NAME=1, then open Nuke.

2) Create a Checkerboard node and attach it to a Write node.

3) Render out an .exr sequence and observe the naming convention used for the temporary files. It should look something like the following:

filename.[FrameNumber].exr.tmp

If you then render a .dpx sequence and look at the names used for the temporary files, you will notice that the naming convention is different. ie:

filename.[FrameNumber].dpx.[NukeExecutableProcessID].tmp

Reproduced by support

This bug has been reproduced in:
Nuke 11.2v4 - Windows 10

Earliest version tested
Nuke 11.2v4
- The NUKE_EXR_TEMP_NAME environment variable did not exist before this version.

Expected behaviour
The naming convention of .exr temporary files should be the same as the naming convention of .dpx temporary files. For example:

filename_[FrameNumber].exr.[NukeExecutableProcessID].tmp

Actual behaviour
The naming convention of .exr temporary files does not match the naming convention of .dpx temporary files. For example:

filename.[FrameNumber].exr.tmp