Thanks for the scene Andy,
I've tracked down the issue and it appears to be a max bug. In code terms, max is not processing the validity interval argument properly in the post-WSM tm query function...the incorrect validity interval is causing max to believe that the modifier doesn't need to update over time, and thus your geo remains static because the stack evaluation procedure skips over it when the frame is changed.
The weird part is that the introduction of the line of code which causes the issue was many, many versions ago....far earlier than v0.16059.
Either way, the issue will be fixed in the next build. If you're on a time-sensitive project, email support@tyflow.com with your desired build version and I'll send you a fix.
I've tracked down the issue and it appears to be a max bug. In code terms, max is not processing the validity interval argument properly in the post-WSM tm query function...the incorrect validity interval is causing max to believe that the modifier doesn't need to update over time, and thus your geo remains static because the stack evaluation procedure skips over it when the frame is changed.
The weird part is that the introduction of the line of code which causes the issue was many, many versions ago....far earlier than v0.16059.
Either way, the issue will be fixed in the next build. If you're on a time-sensitive project, email support@tyflow.com with your desired build version and I'll send you a fix.