ID 399421 - ParticleEmitter node is not relaying transform information, when passed through a TimeOffset node in Nuke 11.3 releases

Follow

Problem summary
When animating a texture into a ParticleEmitter node using a Transform node, if there is a TimeOffset before the ParticleEmitter node, the animation will not carry through to the result.

This only occurs in Nuke 11.3 releases, and not in releases 11.2 and earlier.

Customer reported version
nuke.11.3v4

Customer reported platform
ubuntu

Steps to reproduce

Open the attached script in a Nuke 11.2 release, enable/disable the TimeOffset node, and compare the results to a Nuke 11.3 release.

or

1) Create a new NukeX session (in a Nuke 11.2 release), setting the frame range of the script to 1 - 2000

2) Create a ColorBars node

3) Create a Transform node downstream of the ColorBars node

4) Within the Transform node, key the rotate knob at 0 on 'frame 1', and 20000 on 'frame 2000' and then set the scale value to 0.1

5) Create a TimeOffset node downstream of the Transform node and set the TimeOffset value to 1000

6) Create a ParticleEmitter node downstream of the TimeOffset node

7) Within the ParticleEmitter node, set the 'start at' knob to 1001, the 'velocity knob' to 0.02

8) Cache particle sim and view frame 1007.

9) Enable/Disable the TimeOffset node.
Result: The animated texture works as expected.

9) a) Save and open the script in a NukeX 11.3 release
or
b) Recreate steps 1-8 within a Nuke 11.3 release

10) View results of ParticleEmitter node

11) Enable/Disable the TimeOffset node
Result: When the TimeOffset node is active, the texture does not carry through to the particle result.

Expected behaviour
The texture should be carrying through the TimeOffset node to the ParticleEmitter node.

Actual behaviour
The texture does not carry through the TimeOffset node correctly in Nuke 11.3 releases

Workaround
Unknown.

Reproduced by support
This bug has been reproduced in:
Nuke 11.3v4 - Windows 7 - MacOS 10.14.5 - CentOS 7
Nuke 11.3v1 - Windows 7

Unable to reproduce bug in:
Nuke 11.2v6 - Windows 7 - MacOS 10.14.5 - CentOS 7

Earliest version tested
Nuke 11.2v6
- This issue no longer appears in this version and has regressed
 

    We're sorry to hear that

    Please tell us why