Vitruvian Bones Crashing

[EricTheFish]

Hi all,

I'm working through the Vitruvian Bones tutorial but keep crashing out Moho to desktop at around the same point. I'm using 13.5.3 on Win10x64 Pro.

Following the tut, I have two basic arms, each with parented bones, flexi-bound to the arm layers and members of a V-group as per the tut.

I can move the bones for Arm1 and create keyframes OK. The playhead is now over the last keyfame for Arm1.

I then select the V-Bone tool and go to the Active Bone drop menu and selected the second bone in the list (there are only two per the tut).

After a couple of seconds, Moho crashes to desktop - every time. This is such a simple test file.

Any chance someone could have a look at the tut file I'm playing with to see if they can spot what might causing it? (It's not negative keyframes).
https://drive.google.com/file/d/1PGeAd4 ... sp=sharing

thanks for advice

[Víctor Paredes]

I'm not sure about the specific reasons for the crash, but probably it's related to some keyframes that shouldn't be there:
- Bone Lock
- Bone Target
- Bone Parent
- Bone Dynamics
- Bone Motor Speed

Try this:
- Select the bone layer
- Go to bone -> Disable all Vitruvian Bones
- Press Esc to unselect all the bones
- In the timeline, click over each of the channels listed above. That will select all the keyframes on those channels
- Press Delete to remove those selected keyframes
- Go to bone -> Enable all Vitruvian Bones
- Now the file should work well

PS: Maybe those extra keyframes appeared because you added the bones on a frame higher than 0.

[EricTheFish]

PS: Maybe those extra keyframes appeared because you added the bones on a frame higher than 0.

Hi Victor, that appears to have fixed the issue! Thank you.

I built everything at frame 0. However, I recall doing a cut/paste on some keyframes for Arm1 after moving following keyframes further down the timeline out of the way.

I'm wondering if problem keys were introduced during paste? I thought I was only pasting keys for the selected V-bones into the timeline area where they were still the current selection.

I'll keep a lookout for spurious keys appearing whilst I'm experimenting with V-Bones.

Thanks again for the advice.

[alanthebox]

hope it's okay if i hijack this thread! vitruvian bones aren't crashing for me in 13.5.3, however, i am getting this strange timeline flickering whenever i enable onion skins. just wanted to see if anyone else has come across this? strangely enough, i don't get any flickering when experimenting with the included vitruvian man project files in the library...

[Víctor Paredes]

Can you share that file to take a look here?
Thanks

[alanthebox]

Sent off via PM!

Thanks!

[Víctor Paredes]

Ok, I'm not having any issue with your file here on Windows 10 using 13.5.3

Now, and maybe this is related to what you are seeing, the timeline works in a special way with this bones.
If you a vitruvian bone is visible on the frame your are at that moment, you will see all the keyframes of that vitruvian bone in the timeline.
If you go to a different frame on which a different vitruvian bone is visible, then you will see the keyframes of that other vitruvian bone.

So, in your file, you can try this:
- Go to frame 17
- You will see the keyframes of the vitruvian bone B4
- Now move the arrow left to go to frame 16
- You will see the keyframes of the vitruvian bone B2
- If you use the arrows to move the cursor from 16 to 17 and back to 16
- You will see the timeline keyframes changing every time

(This behavior is especially visible when you use the arrow keys on the keyboard. If, instead, you drag the mouse to go to a different frame, then the timeline will be updated only when you release the mouse)

That's one of the reasons we have the special "Vitruvian Bones Consolidated" channel. That channel shows you if any of the bones, visible or not visible at the moment, have keyframes at any momemnt.

[synthsin75]

I can verify that behavior:


It seems the onionskin is conflicting with the Vitruvian bones. So when the onionskin tries to show a v-bone not showing on the current frame, it can flicker like that.

[Víctor Paredes]

Thanks. For some reason it worked fine her yesterday, but now I opened the file again and can clearly see the issue.
I'll investigate a bit more.