Irrlicht Engine

Huzzah!. If you're up for sorting it, then I'd respectfully suggest that until and unless accurate per-node meshes are available, that IAnimatedMesh::getMesh(s32 frame,...) both assert (_IRR_DEBUG_BREAK_IF(...)) and return 0 for skinned meshes, rather than return an incorrect mesh. rogerborg: Even ...

here are the specs on the b3d format.

http://www.blitzbasic.com/sdkspecs/sdks ... _specs.txt

it's public domain so it's as free as you can get.

yep, that was one of the problems with the old system.

that's why I added the "Node->animateJoints();" function.

have a look here: http://www.irrlicht3d.org/wiki/index.ph ... tionSystem

something like this one: http://www.molebox.com/ (just a random google)

not sure if there are any free ones.

that's a pretty bad bug, cannot believe I missed it. code left over from the old system I think.

it shouldn't be affecting anything other then when you manually parent to joints but.

having a quick look though the code, I cannot see anywhere that empty bones are removed. I don't think I did that for your reason. so you might want to check that your exporter is not removing them. hmm, btw if no bones have skin attached, and you have no animation, your mesh is not marked as animat...

I'm happy to have a look at what's wrong.

could you post the code and mesh file maybe.

sorry I haven't been active lately. thanks BlindSide and sio2, for the dx vbo patch, I'll look into applying it. (Although looking at CMeshBuffer.h now it seems that hybrid recently changed the function header for setDirty() to allow for the user to specify the type buffer in question, so something ...

The bounding boxes are not correctly calculated and updated for Skinned Meshes. Just check the meshes in the meshviewer with enabled debug output.

why aren't they correctly calculated? and being updated isn't a problem, as it's a static mesh.

anyway I'll have a look

I cannot see how this could be related to the bounding boxes problems.

could you post an example or some code and the mesh?

I looked at the svn it seems changed, might want to try that.

sorry about that, didn't test with the debug build, so I didn't get that crash.

the array was allocated to the right size, but the array bounds check doesn't like it.

fixed now.

btw there are no problems with fragmentation as the array is never truly resized

b3d, ms3d, and x formats use skeletal animation so you can use joints etc.

md2 uses vertex based animation so it has no underlining skeleton. thereof no joints

looks nice, nice site too. I'm glad someone took on the exporter, I'm not enough of a blender user yet.

I haven't really been following it that much lately, I'll have to test it out.

but the funny thing, that it isn't always... if i change something at the joints place (in the code), it becomes slow, and if i start to use other things (programming, but not the joints), then it becomes good... xD maybe just the debugging? try updating the absolute positions after you move the jo...