Problem summary
When a Read node is recalling from a localised location, it is possible to also cache another Read node in the script by playing it in the Viewer.
When this occurs, the localization process on the original Read node is paused and the Viewer caches the second Read node.
Although, when the caching process is stopped or paused, the Viewer's cache will be removed and the built cache will be lost in the second Read node.
Customer reported version
nuke.12.1v2
Customer reported platform
windows10
Steps to reproduce
1) Open a new Nuke session
2) Create two Read nodes, preferably large in file size and duration.
3) Turn the localisation policy to 'on' within the first Read node
4) While the first Read node is localizing, view the second Read node, and cache a few frames in the Viewer.
5) Stop the caching by stopping the playback in the Viewer Result: Localization will resume, but the cache related to the second Read node will be removed.
Expected behaviour
When a Read node is cached in the Viewer, the cache should remain
Actual behaviour
When a Read node is cached in the Viewer, the existing cache is removed when the localization process is continued from being paused.
Workaround
unknown.
Reproduced by support
This bug has been reproduced in:
Nuke 12.1v4 - Windows 10
Nuke 12.1v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.3v1 - Windows 10
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
Unable to reproduce bug in:
Nuke 9.0v1 - Windows 10
Earliest version tested
Nuke 9.0v1
- Localisation cache was not implemented into the Read node till Nuke 10.0v1