Hello,

So I've finally been able to make my digital asset that works.

In it I have a wave node that controls the movement of a pathcv node.

In a new file when I import the asset and set my controls to move the path point as I want it will do so for the entire current Frame Range as it was when the asset was imported.

If I change the Frame Range the motion will only go for as long as the original Frame Range when that asset was imported.

Of course with a new Frame Range and importing the asset again then setting the controls again will ensure that it's motion continues for the entire Frame Range.

Is there a way to get the wave node to interpolate to any new Frame Range setting?

Or is this just a matter of having to decide what Frame Range I will be using and stick to it?

I guess I could write a script that initializes the settings of my asset/s.

Since this one asset controls one point and I will be having about 50 independant points moving with different settings each ( and about 5 controls each), it might quit a bit of work each time the Frame Range is changed.

Thanks

This is a bug with using “Use Full Animation Range”. I've submitted a bug for this (#73201). The problem is that the CHOP nodes aren't recooked. So if you simply save-and-reload the file, the CHOP nodes would get recooked.

If this is an important feature for your asset, you could also workaround the issue by explicitly using $FSTART and $FEND. So you'd set the channel range to “Use Start/End”, and set Start and End to:
# Start
($FSTART-1)/ch(“rate”)
# End
$FEND/ch(“rate”)

For the waveform CHOP, you'd have to use ch(“vex_rate”) instead of ch(“rate”).

Thank you very much for this info awong.

The save and re-load file is the perfect solution for me.

I thought I would try the suggestion of using “…$FSTART….”

but for some reason it doesn't work for me.

I selected “use start/end' for Channel Range parameter,
and played around with Sample Rate( starting with 24 ).

I also made sure Expression Language was set to HScript.

But it always stops at the original 240 fps ( which was the setting when the asset was imported. )

I don't need to know how to get around this or ”fix" it since the first solution works better for me but I thought I would mention it and say again I appreciate your feedback

Thanks - BabaJ