talosh
commented
1 month ago Would it be possible to send Flame archive with this shot for me to check?Sent from my iPhoneOn 16 Jul 2024, at 20:18, jeffkyleflame @.***> wrote: This is my first time trying TWML 0.4.5 dev003 on Flame 2025.0.1. I'm using the Timing mode with a custom keyframed timewarp. I'm finding after a number of exports and restarts that since my Timing keyframe setup goes forwards and then backwards, my renders are not matching the timing of the keyframed Timewarp. It's a little hard for me to describe, but maybe to make it a little clearer, here are my frame rangers: 1-295 are unchanged 295 - 436 are mapped to 295-325 436-600 are mapped to 325-298 This results in my Timewarp node playing normal speed, slowing down, then reversed + slowed down. When I get my TWML render after it processes, I find that 1-295 plays normal, but when it gets to 295, it does not behave the way my keyframes are set up, and it clearly just "gets it wrong". I've run some additional tests since then and have found that when a Timing keyframe setup goes forward and then backward, it seems to corrupt the data somehow.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
jeffkyleflame
This is my first time trying TWML 0.4.5 dev003 on Flame 2025.0.1. I'm using the Timing mode with a custom keyframed timewarp. I'm finding after a number of exports and restarts that since my Timing keyframe setup goes forwards and then backwards, my renders are not matching the timing of the keyframed Timewarp. It's a little hard for me to describe, but maybe to make it a little clearer, here are my frame rangers:
1-295 are unchanged 295 - 436 are mapped to 295-325 436-600 are mapped to 325-298
This results in my Timewarp node playing normal speed, slowing down, then reversed + slowed down.
When I get my TWML render after it processes, I find that 1-295 plays normal, but when it gets to 295, it does not behave the way my keyframes are set up, and it clearly just "gets it wrong". I've run some additional tests since then and have found that when a Timing keyframe setup goes forward and then backward, it seems to corrupt the data somehow.