Problem summary When Versioning up/down Footage within Read nodes, if the footage does not have any Padding, Nuke will fail to read the footage when versioning down on multiples of 0.
For example, if you version down from _v10 to _v9 Nuke will look for _v09 and fail.
This also occurs at higher padding e.g _v100 and _v99.
This issue does not occur within NukeStudio/Hiero timelines.
Customer reported version nuke.11.3v2
Customer reported platform centos7
Steps to reproduce
1) Create and Write out a Checkerboard in Nuke named /TestVersion_v9.png
2) Write out two more Checkerboards named ./TestVersion_v10.pngand ./TestVersion_v11.png
3) Read in ./TestVersion_v9.png as a Read node
4) Hover over the Read node and Version up with Alt+Up twice Nuke will version the image up to ./TestVersion_v11.png
5) Version down the Read twice with Alt+Down twice
Result: Nuke will attempt to version down to ./TestVersion_v09.png which does not exist. Nuke will throw an Error in the Viewer to display this behaviour:
Expected behaviour If Nuke does not find footage with the Padding, it should check without padding.
Actual behaviour Nuke attempts to check for footage with padding returns errors.
Workaround It is recommended to add padding to Version and Frame numbers in Footage naming templates.
This allows Nuke to Version up and down without issues. The most common padding for Versions is v### and for frames #### .
Reproduced by support
This bug has been reproduced in: Nuke11.3v1- Windows 7 - Mac10.14 - CentOS7 Nuke11.3v1- Windows 7 - Mac10.14 - CentOS7 Nuke11.2v1 - Windows 7 Nuke11.1v1 - Windows 7 Nuke11.0v1 - Windows 7 Nuke10.5v1 - Windows 7 Nuke10.0v1 - Windows 7 Nuke9.0v1 - Windows 7 Nuke8.0v1 - Windows 7 - Mac10.14 - CentOS7
Earliest version tested - This issue appears to be in all versions of the product
