Bones / Moho Stop Working

[katxande]

I'm having this problem for the second time, already contacted moho team once and they didn't find a way to fix this. Sometimes i get this bug or processing problem from the program when i move/rotate any bone the program just stop working and i have to wait like 30 secs until it comes back. Any one knows a solution for this problem?

- I have a good graphic card, processor and 16gb ram(is there any way to give me "power" to the software?

- Already tried to restart, don't help.

- I don't know if it is a "project problem" or a "software problem.

I know the bug only started happening now.

In the past the way i have found to fix this is just copy all the project and associate all the bones again in the vectors layers, but at this point i cant do it.

Thanks.

PS: I´m doing a animation test for a job, I'm a bit in a hurry.

[synthsin75]

It's likely the project. I'd have to see the file to diagnosis it more than that.

Are you running the latest version of Moho?

[katxande]

It's likely the project. I'd have to see the file to diagnosis it more than that.

Are you running the latest version of Moho?

Yes, i am running the most recent update. Yeah must the project file, because the "bug" its not happening in the backup file.

Can you pm your mail, i cans end you the corrupted file.

[synthsin75]

It's likely the project. I'd have to see the file to diagnosis it more than that.

Can you pm your mail, i cans end you the corrupted file.

If you upload the file somewhere, like FileDropper, mediafire, etc., you can PM me the link to it, and I'll take a look.

[Greenlaw]

In the past, I've run into a situation where a keyframe gets created thousands of frames behind 0, and this error seems to create a huge performance problem, and possibly making the scene unstable. I haven't run into that bug in a while but maybe that's what happened in your project?

The solution was to find the keyframe and delete it. Tracking the keyframe down within Moho could be easy or difficult, depending on the complexity of the project. (It also doesn't help that we can't see anything before frame 0 like we can in other animation programs.) You can probably find the keyframe and kill in a text editor but I'm not sure how to do that. Maybe Wes can offer more info for this?

[synthsin75]

In the past, I've run into a situation where a keyframe gets created thousands of frames behind 0, and this error seems to create a huge performance problem, and possibly making the scene unstable. I haven't run into that bug in a while but maybe that's what happened in your project?

The solution was to find the keyframe and delete it. Tracking the keyframe down within Moho could be easy or difficult, depending on the complexity of the project. (It also doesn't help that we can't see anything before frame 0 like we can in other animation programs.) You can probably find the keyframe and kill in a text editor but I'm not sure how to do that. Maybe Wes can offer more info for this?

There do seem to be one or two channels that have legitimate keyframes at -1000000. But yeah, it's easier to find them by looking at the file code itself.

[Greenlaw]

Thanks for checking that Wes. I hope it fixes it for katxande.

Just curious but, if you have the file open in a text editor, can you post a screen cap of the the key frame data and what part to delete? I haven't seen this error in a long time but want to be ready to deal with it in case it happens here.

[synthsin75]

Thanks for checking that Wes. I hope it fixes it for katxande.

Just curious but, if you have the file open in a text editor, can you post a screen cap of the the key frame data and what part to delete? I haven't seen this error in a long time but want to be ready to deal with it in case it happens here.

Sure, but I haven't heard back from katxande yet.

[katxande]

Thanks for checking that Wes. I hope it fixes it for katxande.

Just curious but, if you have the file open in a text editor, can you post a screen cap of the the key frame data and what part to delete? I haven't seen this error in a long time but want to be ready to deal with it in case it happens here.

Sure, but I haven't heard back from katxande yet.

Sorry for the long time, my brain needed some sleep. I´m going to upload the file somewhere and pm you the link for it.

[katxande]

In the past, I've run into a situation where a keyframe gets created thousands of frames behind 0, and this error seems to create a huge performance problem, and possibly making the scene unstable. I haven't run into that bug in a while but maybe that's what happened in your project?

The solution was to find the keyframe and delete it. Tracking the keyframe down within Moho could be easy or difficult, depending on the complexity of the project. (It also doesn't help that we can't see anything before frame 0 like we can in other animation programs.) You can probably find the keyframe and kill in a text editor but I'm not sure how to do that. Maybe Wes can offer more info for this?

I think the problem, was a non parent bone. Because in the backup file i have parented it and the bug was gone. But in the corrupted file i have done the same, but the bug still there. And if i open the Smart actions, the vectors are making a picasso art

[synthsin75]

Dennis was spot on. There were some keyframes hidden in the negative timeline. Here's how to fix it from within Moho.

1. Go to frame 1000000 by entering that next to the play controls into the Frame input, where is says "Frame _ of _", and hit enter. You can just put in more zeros than needed because Moho will only let you reach frame one million anyway.
2. With your top layer selected, use the "Animation>Set Layer Start Time" menu command.
3. Select your bone layer and hit the "Previous Keyframe" button, next to the play controls, twice.
4. This should show you some bone keyframes at frame 263. If it doesn't just type 263 into the Frame input.
5. Delete all the bone keys at 263.
6. Select your top layer and frame one and use the "Animation>Set Layer Start Time" menu command to set the layer start time back where it was.

All odd behavior should be fixed now.

[katxande]

Dennis was spot on. There were some keyframes hidden in the negative timeline. Here's how to fix it from within Moho.

1. Go to frame 1000000 by entering that next to the play controls into the Frame input, where is says "Frame _ of _", and hit enter. You can just put in more zeros than needed because Moho will only let you reach frame one million anyway.
2. With your top layer selected, use the "Animation>Set Layer Start Time" menu command.
3. Select your bone layer and hit the "Previous Keyframe" button, next to the play controls, twice.
4. This should show you some bone keyframes at frame 263. If it doesn't just type 263 into the Frame input.
5. Delete all the bone keys at 263.
6. Select your top layer and frame one and use the "Animation>Set Layer Start Time" menu command to set the layer start time back where it was.

All odd behavior should be fixed now.

Good morning and thank you for take the time to look for it.
Yap this worked. But why do this bug happens?

Can you teach me how to open and look at the file code itself so next times i can just find the (bugged) key frame and do it my self.

Once again thank you.

[synthsin75]

Good morning and thank you for take the time to look for it.
Yap this worked. But why do this bug happens?

Can you teach me how to open and look at the file code itself so next times i can just find the (bugged) key frame and do it my self.

Once again thank you.

I didn't need to look through the code to find this, but a Moho file is really a zip file, so you can open it with something like 7zip, WinRAR, etc.. Inside is the thumbnail image and a Project.mohoproj json file, which is plain text. But in your case, searching that for "-1000" shows a lot of legitimate keyframes in the negative timeline, so it's not very helpful.

I'm not sure why this happens.

Glad I could help.

[Greenlaw]

I've never understood how this error happens either but when I notice a sudden slow down in performance between two project versions, this is one of the first things I suspect. Fortunately, for me anyway, I haven't seen this happen for a long time.

It is, however, one of the reasons I create many versions of a project as I work on it. When I have to step back to an earlier version for any reason, it doesn't cost me too much lost time. (IMO, this is good practice with any program, not just Moho.)

[synthsin75]

I'm working on a few scripts to check for negative keyframes and unzip/beautify the Moho file format (might only work in Windows).