AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Marble it up switch crashes on startup12/14/2023 ![]() ![]() If you delete one of the 'switched to' child-layers the Switch's references to it are not updated, but that referenced layer name also no longer exists - so the Switch layer defaults to showing the top most layer in its place (and even showing it as ticked in the right-click switch layer selection list of the layers panel - even though internally it still references the 'old' deleted/missing layer name).Īnd. I believe that it is related to a 'feature' of Switch Layers:Ī Switch layer uses the child-layer name as the reference for switching. Looks like the crash occurs across MH 12, 13, 13.5. Never seen this crash before - until now! and that's probably because I don't use the selection/preview window that often. Maybe it's creeped back in for 13.5? Unconfirmed, so just a guess.) ![]() ![]() (The earliest release of 12.x had this problem, but this was fixed before 12.5 was released. ATM, some of us suspect Auto-Save is causing crashes and data loss problems. (Technically, uncompressed audio should be more frame accurate too, so better for lip syncing.) If it's the latter, run Wes' Find And Delete Negative Keyframes script to clean up the file.Īlso, see if disabling Auto-Save reduces or eliminates the crashing. Uncompressed requires less processing and is less likely to cause trouble when scrubbing back and forth. Just a feeling, but maybe something else is causing the crash? Like the audio file (if one has been imported) or maybe there's a distant negative keyframe? If it's the former, and it's a compressed audio file, try an uncompressed version. So far, I'm not seeing such crashes in 13.5 either, but admittedly I haven't stressed 13.5 as much as I have 12.5 yet. I use Switch layers all the time for lip sync and other animations, but I'm not seeing the crashing, at least not in Moho 12.5 and I've been using this version in production for years. ![]()
0 Comments
Read More
Leave a Reply. |