Let's talk about operation delays and lag again

[sang820]

My newly created model is experiencing severe lag, which I believe is due to Moho's excessive memory usage. My Moho project file is 1.58MB; after deleting actions, it's down to 332KB. I suspect the lag is mainly caused by the interactions and features between actions and nodes.（This leather-clad girl has 55 actions）.

My testing revealed the following order of lag influencing factors: Actions > Skeletal Dynamics > Displaying Full Detail > Number of Nodes > Gradient Colors

1- Use a large number of smart skeletons; 2- The model has a large number of nodes; 3- Minimize operational lag.

If these three conditions are met, I believe only reducing the number of history steps can alleviate Moho's current excessive memory consumption. (Or, I'll fantasize that Moho has revolutionary optimization features.)

What do you guys think? Discussion welcome =）

[Greenlaw]

Hi sang820,

I ran into a lag problem recently.

At first, I suspected the negative keyframes bug, but Synthsin75's Find & Delete Negative Keyframes script did not find such keyframes. Which got me wondering, could there be positive unintentional keyframes thousands of frames ahead?

Sure enough, I found unintentional keys starting at frame 998,877, far beyond my animation range. To eliminate the keys, I moved the Playhead past my last intentional keyframe, and selected Clear Animation > From Document After Current Frame. The lag went away immediately.

I'm not sure yet how the unintentional keyframes were created. I haven't had time to investigate this fully, but maybe I can revisit the issue over the weekend.

I don't know if this is the cause of the lag in your project, but it's worth checking.

[sang820]

Hi sang820,

I ran into a lag problem recently.

At first, I suspected the negative keyframes bug, but Synthsin75's Find & Delete Negative Keyframes script did not find such keyframes. Which got me wondering, could there be positive unintentional keyframes thousands of frames ahead?

Sure enough, I found unintentional keys starting at frame 998,877, far beyond my animation range. To eliminate the keys, I moved the Playhead past my last intentional keyframe, and selected Clear Animation > From Document After Current Frame. The lag went away immediately.

I'm not sure yet how the unintentional keyframes were created. I haven't had time to investigate this fully, but maybe I can revisit the issue over the weekend.

I don't know if this is the cause of the lag in your project, but it's worth checking.

Actually, I haven't adjusted the animation keyframes yet, I just finished making the model. I will go around 1000 frames to look for the 'ghost frame' you mentioned, hahaha. I like the name, but I don't like the delay, lag, or lag

[slowtiger]

I think I never had any negative keyframes, but in my longer scenes (over 20 sec) I noticed some lag sometimes when there were unintentional keys faaar away from the actual animation. Quite often I have something stay still or invisible for half a minute, then burst into action for some seconds, then going still again. So I made it a habit of "scaffolding" my animation: set the layers in question invisible on #1, and create keys before and after the animation before I go inside and actually move the object. It seems that setting it to invisible when not in use even speeds up rendering, albeit that difference is not important anymore on my Mac Mini ...

[mionorz]

hi！ 　The behavior I experienced was this: while working in the Windows version of MOHO version 14.4, I noticed that as memory usage steadily increased during my work, once it exceeded 3GB, significant delays occurred that hindered my work. My work environment has 32GB of memory, with over half still available. I was using a PSD file, and the .moho file itself was only about 600KB for a roughly 2-minute animation. Closing and restarting MOHO reduced memory usage to around 300MB, allowing it to run smoothly again. However, as I continued working, memory usage steadily increased again, causing it to slow down. Consequently, I found myself restarting it repeatedly after about an hour.

I haven't encountered ghost frames in version 14.4. It's possible some countermeasures were implemented.
The brief freeze in the work window during timeline scrubbing is caused by bone dynamics. Disabling dynamics via the Animation menu improves this. I suspect this relates to GPU optimization issues affecting display, separate from memory-related problems.

I don't use many plugins, but based on these behaviors, I suspect the sluggishness related to memory usage might stem from garbage accumulation in areas like auto-save or undo processing. If created data like actions or smart bones were the cause, I'd expect sluggishness right after startup.

[sang820]

hi！ 　The behavior I experienced was this: while working in the Windows version of MOHO version 14.4, I noticed that as memory usage steadily increased during my work, once it exceeded 3GB, significant delays occurred that hindered my work. My work environment has 32GB of memory, with over half still available. I was using a PSD file, and the .moho file itself was only about 600KB for a roughly 2-minute animation. Closing and restarting MOHO reduced memory usage to around 300MB, allowing it to run smoothly again. However, as I continued working, memory usage steadily increased again, causing it to slow down. Consequently, I found myself restarting it repeatedly after about an hour.

I haven't encountered ghost frames in version 14.4. It's possible some countermeasures were implemented.
The brief freeze in the work window during timeline scrubbing is caused by bone dynamics. Disabling dynamics via the Animation menu improves this. I suspect this relates to GPU optimization issues affecting display, separate from memory-related problems.

I don't use many plugins, but based on these behaviors, I suspect the sluggishness related to memory usage might stem from garbage accumulation in areas like auto-save or undo processing. If created data like actions or smart bones were the cause, I'd expect sluggishness right after startup.

Hello, if the animation duration in a single Moho file does not exceed 60 seconds, the lag may occur later. Moho outputs animation clips (PNG sequences or MOVs with channels) and then enters post production software synthesis. It is necessary to process 2-minute animations in this way. Usually, I only have animations within 30 seconds per Moho file