This has happened 2x lately in 2x different projects. 2026.2.1, MacOS 15.5. Simple Gmask Tracer, in this case punching a little AI cleanup into a plate. No keyframes. At some point later in my batch the Gmask “pops” and draws incorrectly. See screenshot. Like “Apply+Scale” is hallucinating anamorphic (even though it’s greyed out/Same as Front)?
Disconnecting and reconnecting node fixes it up, and it’s stable for 5-10mins before popping again. Usually on a full Render. My solve is to pre-comp that part of the batch.
We’re gearing up for 2027, just curious if anyone has seen this?
I’ve seen this a fair bit in 2026, particularly when working on non-HD material, toggling between F1 and F4 the displayed resolution jumps around. Don’t remember seeing it 2027.
I think it’s par crap when your project settings are 16x9 or whatever and the source footage is say open gate and doesn’t match, happens to me a bunch but I also can never repeat it
That tracks. I can’t repeat it either, it just starts happening. Have been using a lot more AI for cleanup, could be aspect ratio mismatch causing math errors in Flame.
This got fixed in 2027, can’t remember which version now, but definitely not happening on 2027.1
It’s when you pass a gmask through an action setup and use the matte upstream.
I found the only sure fire way of fixing it is to render the gmask out or use the old gmask node.
