VaM 1.x Locking Elbow Target destroys Arm Geometry

[Ghostwalden]

I locked the elbow target and it destroyed the arm geometry.
I never had this before and i have no clue, what causes this...

Maybe someone an idea?

I just found out, that it remains as it should, when i go from Off to Lock.
But then, when i move the elbow target, the hand also moves and destroys geometry.
It says Link To: SelectionHandles, but when i select the hand, there is nothing linked.
Does someone know, where that SelectionHandles comes from?

 

[SlimerJSpud]

It only says SelectionHandles while you have the item selected and are dragging it around. I'd suggest not using Lock for anything. You might try using Hold instead. Also, you might want to hold the position, but leave the rotation in off or on, depending. I think it's the lack of rotation that's causing the deformation, because the hand wants to move, but the elbow angle is locked.

 

[Ghostwalden]

It only says SelectionHandles while you have the item selected and are dragging it around. I'd suggest not using Lock for anything. You might try using Hold instead. Also, you might want to hold the position, but leave the rotation in off or on, depending. I think it's the lack of rotation that's causing the deformation, because the hand wants to move, but the elbow angle is locked.

Thanks for your reply SlimerJSpud

Ah ok... SelectionHandles Question solved

I tried hold, but it sadly has not near the effect that i would like to have.
With Hold, the elbow still moves up and down like with On.

I never had a problem with lock.
I often lock feet or hands, but this time the problem i found out was, that the hand already was locked.
So with the hand only locked, there was no problem, but then with the elbow also locked it caused that problem i guess.
Strange is only, that the problem also occured, while the animation wasn't running

I guess locking should only be used sparingly then.

 

[SlimerJSpud]

I would say it's locking adjacent nodes that caused it.

 

[Ghostwalden]

I would say it's locking adjacent nodes that caused it.

Yes, it seems so.

 

[CV42]

Locking the position & rotation of two adjacent nodes and then moving one of them kinda always is problematic.

Setting the hand or elbow nodes position state to on should fix the problem. Maybe it is enough to just set their rotation state to off. The combination of Lock+lock only works when the nodes do not move or the joints rotation can compensate the movement.

In general I recommend locking only one node and keep adjacent nodes to on/off and tweak the spring when more force is needed on those nodes. Lock+lock of adjacent nodes leads to jittering sooner or later.

 

[Ghostwalden]

Locking the position & rotation of two adjacent nodes and then moving one of them kinda always is problematic.

Setting the hand or elbow nodes position state to on should fix the problem. Maybe it is enough to just set their rotation state to off. The combination of Lock+lock only works when the nodes do not move or the joints rotation can compensate the movement.

In general I recommend locking only one node and keep adjacent nodes to on/off and tweak the spring when more force is needed on those nodes. Lock+lock of adjacent nodes leads to jittering sooner or later.

Thanks for your Reply CV42

Yes, when i turned the hand position to on and only locked the elbow position, the problem was gone.

Normally I only lock feet or hands and that never caused problems.
But now I know, that locking adjacent nodes can cause massive problems.

I'll keep this in mind, for the case, that i need to lock adjacent nodes i ithe future, that I try out to only lock position and not the rotation.