# Gmask Tracer "popping" in 2026.2 **URL:** \ **Category:** Flame Questions\ **Tags:** gmask-tracer\ **Created:** [September 29, 2026, 4:57pm UTC](https://forum.logik.tv/t/gmask-tracer-popping-in-2026-2/15002 "2026-09-29T16:57:34Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![aaronneitz](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/aaronneitz/32/3874_2.png) [@aaronneitz](https://forum.logik.tv/u/aaronneitz)\ **Post date:** [September 29, 2026, 4:57pm UTC](https://forum.logik.tv/t/gmask-tracer-popping-in-2026-2/15002/1 "2026-09-29T16:57:34Z")
![Screenshot 2026-09-25 at 2.00.34 PM](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/0/060922d14c361f8df0f88dd7c546b0353ec81532.jpeg)’ 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? ---
**Author:** ![space\_monkey](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/space_monkey/32/49_2.png) [@space\_monkey](https://forum.logik.tv/u/space_monkey)\ **Post date:** [September 29, 2026, 7:05pm UTC](https://forum.logik.tv/t/gmask-tracer-popping-in-2026-2/15002/2 "2026-09-29T19:05:34Z")
Ive seen it and I believe its been fixed in the up coming release. ---
**Author:** ![leowoo](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/leowoo/32/1371_2.png) [@leowoo](https://forum.logik.tv/u/leowoo)\ **Post date:** [September 30, 2026, 3:43am UTC](https://forum.logik.tv/t/gmask-tracer-popping-in-2026-2/15002/3 "2026-09-30T03:43:24Z")
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. ---
**Author:** ![JonoAmes420](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@JonoAmes420](https://forum.logik.tv/u/JonoAmes420)\ **Post date:** [September 30, 2026, 4:30pm UTC](https://forum.logik.tv/t/gmask-tracer-popping-in-2026-2/15002/4 "2026-09-30T16:30:43Z")
this happens to me since I upgraded to latest 2025. ---
**Author:** ![joelosis](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/joelosis/32/72_2.png) [@joelosis](https://forum.logik.tv/u/joelosis)\ **Post date:** [September 30, 2026, 5:18pm UTC](https://forum.logik.tv/t/gmask-tracer-popping-in-2026-2/15002/5 "2026-09-30T17:18:32Z")
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 ---
**Author:** ![aaronneitz](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/aaronneitz/32/3874_2.png) [@aaronneitz](https://forum.logik.tv/u/aaronneitz)\ **Post date:** [September 30, 2026, 7:10pm UTC](https://forum.logik.tv/t/gmask-tracer-popping-in-2026-2/15002/6 "2026-09-30T19:10:22Z")
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. ---
**Author:** ![Jason\_Chambers](https://avatars.discourse-cdn.com/v4/letter/j/ecb155/32.png) [@Jason\_Chambers](https://forum.logik.tv/u/Jason_Chambers)\ **Post date:** [September 30, 2026, 8:09pm UTC](https://forum.logik.tv/t/gmask-tracer-popping-in-2026-2/15002/7 "2026-09-30T20:09:58Z")
Had this yesterday, added a matte edge after the tracer and that fixed it. Could also have been a total coincidence. Was also with mismatched resolutions. ---
**Author:** ![stu](https://avatars.discourse-cdn.com/v4/letter/s/3ec8ea/32.png) [@stu](https://forum.logik.tv/u/stu)\ **Post date:** [September 30, 2026, 9:22pm UTC](https://forum.logik.tv/t/gmask-tracer-popping-in-2026-2/15002/8 "2026-09-30T21:22:59Z")
> [@aaronneitz](#): > > … 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? 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. ---
**Author:** ![JonoAmes420](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@JonoAmes420](https://forum.logik.tv/u/JonoAmes420)\ **Post date:** [October 1, 2026, 4:25pm UTC](https://forum.logik.tv/t/gmask-tracer-popping-in-2026-2/15002/9 "2026-10-01T16:25:36Z")
after many rogue gmask pops I’ve come to this: Dragging the mask onto media front (onto picture) there hasnt been any popping. Dragging it into gmask tracer schematic I get the popping.