[00:23:56] <Dominus> ok, tracked down to r5911 Marzo's "BIG Commit (TM). Quite likely, there are a lot of bugs." https://sourceforge.net/p/exult/code/5911/
[00:24:52] <Dominus> there he deleted the entries of the special animation section in shape_info.txt and voila, belt broken, I *think*
[02:50:14] --- DominusExult is now known as Dominus
[12:26:01] <Dominus> so, the bug is in objs/animate.cc:404 case Animation_info::FA_LOOPING:
[12:39:30] <wjp> what exactly is (visually) going wrong with the animation?
[12:39:36] <wjp> (Can't test here)
[12:41:34] <wjp> oh, it's looping back to frame 0 instead of to frame 1?
[12:56:37] <Dominus> Wjp, yes
[12:57:08] <Dominus> Same for the end points of the axis
[12:58:09] <Dominus> I think the last if in theredoesn't properly reflect the chance hence it never animates
[12:59:08] <Dominus> If I leave the first if out thatdeals withe chance it animates more
[13:00:27] * Dominus got baby in arm, not in front of the computer and has to type with left hand, so I'm a bit cryptic ;)
[21:39:13] <Lightkey> teach the baby to type for you
[22:58:11] <Dominus> Marzo: did you see the bug report about broken millsaw animation in BG? When you figured out the animation bit of BG and removed the millsaw from the shape_info.txt, you killed the animation.
[23:00:17] <Dominus> In objs/animate.cc:404 I think there is something wrong that allows the animations to run through the frames >0 and thus it returns to frame 0...
[23:00:43] <Dominus> But I need to sleeeeeeeep now....