# Flame 2025.2 Timewarp BUG? **URL:** \ **Category:** Flame Questions\ **Tags:** timewarp, bug\ **Created:** [November 5, 2024, 12:16pm UTC](https://forum.logik.tv/t/flame-2025-2-timewarp-bug/11694 "2024-11-05T12:16:55Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Fabi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/fabi/32/14709_2.png) [@Fabi](https://forum.logik.tv/u/Fabi)\ **Post date:** [November 5, 2024, 12:16pm UTC](https://forum.logik.tv/t/flame-2025-2-timewarp-bug/11694/1 "2024-11-05T12:16:55Z")
I may have found a BUG in 2025.2. The prieview of a timewarp whether in the timeline or in the batch does not update as soon as you change its settings. As soon as you move 1 frame forwards or backwards, the prieview updates itself…does anyone have an idea why this could be the case? Mac M1 Ultra (Sonoma 14.7.1) Flame version 2025.2 (2025.2.0.198) ---
**Author:** ![bryanb](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/bryanb/32/136_2.png) [@bryanb](https://forum.logik.tv/u/bryanb)\ **Post date:** [November 5, 2024, 2:27pm UTC](https://forum.logik.tv/t/flame-2025-2-timewarp-bug/11694/2 "2024-11-05T14:27:31Z")
I have the same issue with the same hardware. I was trying to figure it out yesterday and saw that it doesn’t update when you change keyframes in the timing field. You have frame forward/backward to get the update. ---
**Author:** ![hildebrandtbernd](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/hildebrandtbernd/32/3038_2.png) [@hildebrandtbernd](https://forum.logik.tv/u/hildebrandtbernd)\ **Post date:** [November 5, 2024, 2:47pm UTC](https://forum.logik.tv/t/flame-2025-2-timewarp-bug/11694/3 "2024-11-05T14:47:03Z")
Same here. Going track down and up also works but it rly is annoying when you are differencing sth and beed some offset in the time warp. ---
**Author:** ![cristhiancordoba](https://avatars.discourse-cdn.com/v4/letter/c/9e8a1a/32.png) [@cristhiancordoba](https://forum.logik.tv/u/cristhiancordoba)\ **Post date:** [November 5, 2024, 5:48pm UTC](https://forum.logik.tv/t/flame-2025-2-timewarp-bug/11694/4 "2024-11-05T17:48:26Z")
See this > [@Flame Family 2025.2.1 Out Now! hammer\_and\_pick](https://forum.logik.tv/t/flame-family-2025-2-1-out-now/11695/1): > > Flame Family 2025.2.1 is now available. It includes fixes such as the **Timewarp node** now working in Batch and Batch FX. 🙂 ---
**Author:** ![bryanb](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/bryanb/32/136_2.png) [@bryanb](https://forum.logik.tv/u/bryanb)\ **Post date:** [November 5, 2024, 7:07pm UTC](https://forum.logik.tv/t/flame-2025-2-timewarp-bug/11694/5 "2024-11-05T19:07:22Z")
That escalated quickly! Thanks ---
**Author:** ![cnoellert](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/cnoellert/32/559_2.png) [@cnoellert](https://forum.logik.tv/u/cnoellert)\ **Post date:** [November 5, 2024, 7:11pm UTC](https://forum.logik.tv/t/flame-2025-2-timewarp-bug/11694/6 "2024-11-05T19:11:23Z")
> [@Fabi](#): > > …I may have found a BUG in 2025.2.The prieview of a timewarp whether in the timeline or in the batch does not update as soon as you change its settings.As soon as you move 1 frame forwards or backwards, the prieview updates itself…does anyone have an idea why this could be the case?Mac M1 Ultra (Sonoma 14.7.1)Flame version 2025.2 (2025.2.0.198) Was going to report this today. Beat me to it. ---
**Author:** ![hBomb42](https://avatars.discourse-cdn.com/v4/letter/h/bbce88/32.png) [@hBomb42](https://forum.logik.tv/u/hBomb42)\ **Post date:** [November 5, 2024, 7:41pm UTC](https://forum.logik.tv/t/flame-2025-2-timewarp-bug/11694/7 "2024-11-05T19:41:36Z")
Did they really fix it? We’re super behind version wise so this isn’t biting us, but keyframing the timing curve of a TW TLFX is something I do alllllll the time… ---
**Author:** ![Quinn](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/quinn/32/9057_2.png) [@Quinn](https://forum.logik.tv/u/Quinn)\ **Post date:** [November 5, 2024, 8:47pm UTC](https://forum.logik.tv/t/flame-2025-2-timewarp-bug/11694/8 "2024-11-05T20:47:54Z")
We reported it at least a week ago. Glad they got the fix out ---
**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\ **Post date:** [November 5, 2024, 9:01pm UTC](https://forum.logik.tv/t/flame-2025-2-timewarp-bug/11694/9 "2024-11-05T21:01:24Z")
Was this was effecting ALL of the interpolation modes? Not just TWML ?