Attempting to load a .Zprj file containing an animation that I worked on just a few days ago. First, an information window pops up to report "NULL." Then, a second one that says "Failed to load the animation file. The vertex count between the Garment and the Animation files are different."
I assume the NULL is the result of the animation file load attempt.
I was able to load the file before. Could it have become corrupted somehow during the last save? Everything seems to be loading fine except the animation.
Unfortunately, the file was saved at the last frame, and now I need the avatar (and garments) back at the start position. Am I out of luck? And if so, what is the most efficient way to restore the garments to the start position?
I've been using MD for several weeks now, and this is the first software problem I've encountered.
Lesson learned: Always save animated files at frame 1.
Any suggestions would be much appreciated, thanks.
You can try reimporting your avatar as a morph target (export your first frame as an obj), this won't fix your animation issues, but should be able to reset your avatar back to start position.
Thanks for the suggestion. I ended up replacing the avatar and manually moved the garments back into position. Took a little time but everything is back to start. Made a backup this time.
It looks like the problem may be related to the 5.1.445 upgrade. After building and saving the new file, I still got the "NULL" warning every time I opened the file. This got me worried - I don't want to lose another animation - so I spent an hour or so troubleshooting the avatar file, which was an FBX animation exported from Maya.
I finally realized that the only thing that had changed was the recent upgrade to 5.1.445. So I reinstalled the previous version (5.1.431) and the NULL warnings went away.
The problem seems to be created when you save a file with an FBX animation. Files saved with previous versions open fine. Files saved with 5.1.445 open with a NULL warning.
This is based on a quick test, and it may be that the warning is harmless. But I'm planning to use 5.1.431 going forward.
Please sign in to leave a comment.