ID 589429 - WriteGeo ignores upstream TimeOffset nodes when exporting Cameras/Axis'

Problem summary
WriteGeo ignores upstream TimeOffset nodes when exporting Cameras/Axis'
 
The beta GeoExport node doesn't seem to export any animated Cameras
 
This happens with alembic (ABC) and fbx files, obj does not support exporting animated cameras
 
Customer reported version
nuke.15.1v1
 
Customer reported platform
 
Steps to reproduce
 
1) Open Nuke

2) Create a Camera node, and give it a simple animation with keyframes at 1 and 10

3) Create and connect a TimeOffset node, and set the time offset to 10, the animation in the Viewer will now be offset
 
4) Create and connect a Scene node, then a WriteGeo node
 
5) Set the WriteGeo node to a path to export alembic files, and Execute the export, setting the frame range to the global range 1-100
 
6) Create a Camera node, enable read from file and read in the recently exported alembic file, the animation is no longer offset
 
Expected behaviour
For the export Camera/Axis animation to be time offset correctly
 
Actual behaviour
No time offset was applied
 
Workaround
Rather than using a TimeOffset, change the animation inthe node. This could be done Pythonically using the following:

c = nuke.selectedNode()for k in c.allKnobs():    if k.isAnimated():        try:             firstFrame = int(k.animation(0).keys()[0].x)            k.fromScript(k.toScript().replace("x" + str(firstFrame), "x1001")) ### x1001 is the frame the animation will now start on        except: pass

 
Reproduced by support
This bug has been reproduced in:
Nuke 15.1v4 - Windows 10, macOS Sonoma, Rocky 9.3
Nuke 12.0v1 - Windows 10, macOS Sonoma
 
Earliest version tested
Nuke 12.0v1 - This issue appears to be in all tested versions of the product