1.7.3 Animation glitch?

[muchogrande]

Hi Jesse, love everything about the new version, except for this possible bug I found...

I've rendered a number of animations out of 1.7.3 no problem. Then, I tried to use the "start with index" and something strange happened -- M3D rendered over the same image file for every frame of the animation, (it didn't add the #### suffix at the end). So at the end of rendering 100 frames, I have 1 image file (which is the last frame of the animation).

I've tried restarting M3D, and changed the "start with index" back to 1, but now it only renders to this 1 image file.

Is this my mistake?

[djeaton]

Does your file name have a period in it?  I had that same issue and Jesse fixed the issue with file names with periods and just released 1.7.3.1.

[Jesse]

Yep, djaeton is right, just tested it.
The ani-maker had the same issue with dots in the name in program version 1.7.3, please upgrade to version 1.7.3.1, thx!

[kon16ov]

Ok, so...I've been out of the loop for a while and just started generating a fairly large anim using 1.7.3.1.  In reading this post, I'm not sure if it's related inasmuch as the cause, but I've run into a scenario where 2,500 or so frames in, every frame from then on is black.   Now, if I load the keyframe from the ANI maker, it renders beautifully and all is well. 

Is this something where you need to just see the .m3a to see if there's corruption or if I just need to rebuild it from keyframes and see if that helps? (Or is there something else that's going on?)  There are no dots, by the by, other than the file extension one in the filename.

I'll keep poking it and post back if I have an "aha!" moment or something changes.

[Jesse]

Just send you a private message with my email, if you want to mail me the m3a file.

Might be an issue with new features, are you using lightmaps?