ID 578999 - Using a FrameHold, FrameRange, or TimeOffset node downstream of a 3D node makes the geometry disappear and stop rendering

Follow

Problem summary
Using a FrameHold, FrameRange, or TimeOffset node downstream of a 3D node makes the geometry disappear and stop rendering.
 
This only affects the Classic 3D system, the geometry remains present in the new Beta 3D system 
 
Customer reported version
nuke.14.1v4
 
Customer reported platform
 
Steps to reproduce
 
1) Open Nuke 

2) Create connected CheckerBoard>Card>FrameHold nodes and View it, you can see the Card

3a) Create and connect a Scene node to the FrameHold (or most other 3D nodes) the card disappears
 

 
Alternatively
 
3b) Create and connect a ScanlineRender node to the FrameHold, with a Camera node to point at the Card
 
4) Switch to the 2D Viewer, and view the ScanlineRender node, it renders black:
 

 
Expected behaviour
For the geometry to be visible and renderable
 
Actual behaviour
The geometry disappears or stops being rendered when downstream of a 3D compatible time node
 
Workaround
Unknown.
 
Reproduced by support
This bug has been reproduced in:
Nuke 15.0v4 - Windows 10, macOS Monterey, Rocky 9.2
Nuke 15.0v3 - Windows 10, macOS Monterey, Rocky 9.2 - regression
Nuke 14.1v4 - Windows 10
Nuke 14.1v3 - Windows 10 - regression
 
Unable to reproduce bug in:
Nuke 15.0v2 - Windows 10, macOS Monterey, Rocky 9.2
Nuke 14.1v2 - Windows 10
 
 
Earliest version tested
Nuke 14.1v2 - This issue doesn't appear in this version and has regressed
 

    We're sorry to hear that

    Please tell us why