I’m finding some odd behavior with linking axes in batch with expressions. I have an axis called “Track,” then I have various other instances of batch with a linked axis to the original track.
When I want to use this setup on another shot, I retrack the Tracker axis. However, this breaks the link with all the other axes in the setup, so I then have to manually go and paste those back in.
Anyone know of a workaround on this? I’m doing lots of shots where this would automate things better…
I’m using this exact workflow and it works for me. 2026.2.1 Linux.
I track an axis in a gmask tracer node which is linked to an axis in an action downstream. It just works when I copy and paste into a different batch setup.
Check that your axis/node names are not something that can be a default node name in Flame. Name them steve or lisa. Not kidding. Node names have interrupted my workflow more than once
This means you are making a copy and pasting it into another batch, correct? Expressions are very picky about how they get copied and duplicated. The safest way to move expression-linked nodes across batches is to build a base with all links and expressions and save it into your user or project bin. Whenever you want to re-use it for another shot, pull it out of the bin fresh. By doing so, when you pull out a new base and the system needs to change the name. which it usually does, it ripples all the expressions to match. By just copy and pasting, when you paste the nodes into a new batch it will change the name of your original node, but not ripple through the expressions. Duplicate might work, but that is only within the same batch. Pulling a new set from the bin is always the safest way.
I set up a bunch of axes with expressions in the setup, all working fine. When I leave BFX to the TL, then go back in — the expressions are broken and there is no animation in the linked axes. So when I go back in, I manually copy the axes around, and abandon expressions.