Jump to content

Recommended Posts

Posted

The same process I have used since day one with Ultra no longer works and has rendered all my animations entirely useless. 

When importing a mixamo animation into the editor -- i now get this.

image.thumb.png.89e9e0858fcee2f1d31f135372a19e1b.png

I recall awhile back some people mumbling about the system not working when in actuality it worked flawlessly but was being used wrong., I can only assume you followed up on  their complaints and decided to correct it when in reality it now appears to be broke as far as everything i created since my first day of beta. 

The process is simple, I export a model out of mixamo in tpose..  i then export an animation sequence out of mixamo and Load Animation in the editior.  The above pic is the new results.

 

 

Posted

I think I know the cause. I removed bone scaling when loading files from the Leadwerks 4 model format to fix this problem:

But it looks like that is causing more serious problems.

Here is what your model looks like when I add bone scale back into animation keys.

image.thumb.png.b98802d41eafff25a7f7c42be8c9d4e0.png

  • Like 1

Let's build cool stuff and have fun. :)

Posted

I just imported 4 anim sequences into the editor and the base model seems to take them just fine, everything is looking normal that is.

That is, with newly converted mesh.. Everything prior to new conversions is messed up.

But I suppose we'll just have to live with that, being beta and all.

 

image.thumb.png.c3b606b2b557682e1fff415c0ce7fd46.png

Posted

I am seeing the same thing.

There are two different versions of the MDL format, so if you save the MDL after conversion, you are saving it to the new format. Apparently there is some problem in that, but I am not sure yet where because the saving the loading code both appear to be including the animation key scale...

I'm sure I will figure this out but it will take some more time.

  • Like 3

Let's build cool stuff and have fun. :)

Posted

I'm going through all the bone data on the original and resaved models. So far everything matches up perfectly. Will continue looking to see where the error is...

Let's build cool stuff and have fun. :)

  • Solution
Posted
On 3/28/2025 at 10:32 AM, Dreikblack said:

Could be related to recent changes how models now loads (for faster loading)

@Dreikblack wins the prize for best clairvoyant debugging. (The boneindices elements are each an unsigned char.)

mesh->m_vertices[v].boneindices[0] = stream->ReadShort();
mesh->m_vertices[v].boneindices[1] = stream->ReadShort();
mesh->m_vertices[v].boneindices[2] = stream->ReadShort();
mesh->m_vertices[v].boneindices[3] = stream->ReadShort();
//stream->Read(&mesh->m_vertices[v].boneindices[0], 8);// No, no no no! https://www.leadwerks.com/community/topic/68279-animations-messed-up/
  • Like 2

Let's build cool stuff and have fun. :)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...