Hey guys!

I am currently working with my artist so we can get a workflow up and running to import static and skinned meshes in our own engine.

He is using the biped tool in 3ds max.

At the moment we have 2 options to go for:

-ASSIMP and importing .dae(Collada) files

-FBXSDK and importing .fbx(obviously)

We tried to go with the ASSIMP way and I am having a problem with bipedal animations. Normal bone animations with example files from the internet. Does anyone have experience with this kind of workflow and can explain to me the weird behaviour in the attached screenshot?

Secondly I tried using the FBXSDK but its a pain in the ass. I am having trouble with simply loading normals...

To anyone out there having a custom engine or experience in those things: How would you/do you handle biped animations?

Best regards,

Flo

I've used ASSIMP (the .NET port anyway) before, what does your loading code look like? My first guess looking at this (skinned?) model is that there's some offset error in the indexing of the bones to the weight values the mesh is being given, or in other terms "the mesh has the bones it's referencing all out of order".

The code is ok, because I tested it with the example file from this tutorial: http://ogldev.atspace.co.uk/www/tutorial38/tutorial38.html

It has something to do with my artist using the bipedal tool from 3dsmax and then converting it to collada.

Have you compared the .dae file that your artist gave you to the "working" one from the demo?

Nevermind that, just checked out the demo code, that's a .md5anim and .md5mesh file, which aren't the same layout as collada, correct? So how are you sure your loader will do the correct work with a collada file?

Assimp gives the same interface for every format. So in theory it should work...

Are there spaces in the bone names? This thread seems to indicate that could cause a problem. It also suggests using the OpenCOLLADA exporter from 3dsmax. Sounds like all COLLADA exporters aren't necessarily created equal...