Problem with Vectorpoints in MOHO 14.30 compared to 14.20 ??

[martin_mrt]

oooook.
I just wanted to show the the first complete Rig for my film to someone and almost fainted when it was suddenly "broken".
I opened the exact same file i rendered a test animation from some months ago but suddenly the knees of the charachter (vector points) jumped wildly around.
After calming down a bit i tried to open it in the Version the file was made: 1420.
In 1420 the knees are fine. No juming around. To illustrate the problem I attached two images: same file same frame one opened with 1430 one with 1420:


LEFT Moho 14.20 RIGHT Moho 14.30

...on the one hand im glad that my rig is not suddenly broken and i dont have to be devastated. On the other hand I planned to use the new Stroke features in 1430 to rework the look. It would be awesome to be able to work with the latest version on my film and not having to stick to 1420 because of that bug...

..anyway is it a version bug? is it maybe some preference which is diferent now?
Im happy for any statement, advice, tip which is shadding light on the situation!

[martin_mrt]

Does anyone have a clue what the differnce in point handling between MOHO 14.20 and 14.30 could be?

[Greenlaw]

I've never seen anything like that. Can you post a project file with the relevant part of the rig and pants legs?

[martin_mrt]

I've never seen anything like that. Can you post a project file with the relevant part of the rig and pants legs?

Yes here it is: https://www.dropbox.com/scl/fi/eiomjfn8 ... f2ktr&dl=0
I deleted most of the other things in the rig.
On the 0 Frame it only occurs when in Manipulate Bones Tool or Bonestrength Tool. Maybe thats a clue?

[hayasidist]

actions Turn Torso and USR / USR 2 both try to manipulate the same points -- Moho can't resolve the conflicting motion / curvature commands.

[Daxel]

I can't check the file right now but I think this is a bug related to the new 360 smartbone improvements on 14.3. From my notes: This only happens on 14.3, if the smartbone has a smartaction for one direction but not for the other, and it's pointing to a target bone. The solution is to add the missing smartaction. Let me know if that helps.