Search options (Page 1 of 8)

I've disabled the physics (commented every part of code which has something to do with the physics).
Ragdoll parts have now no parent-child relationships, no physics and no constraints.
Copying the bone rotation and position from the armature to the ragdoll, the result is what is seen in the first image that I've posted (the one on the left): http://forum.maratis3d.com/viewtopic.php?pid=6377#p6377, as expected.
Which is the default position of the armature, the same that it's on the Blender file.

If this is of any help, in the Blender file the bones in their default position (as seen in the image) are considered to be at rotation zero (0,0,0) on the 3 axis. In Maratis tough it's not the same, because if I set them at (0,0,0) they all point straight to the axis +Y.

Yes, the order is important but I got it right.
I use a makehuman mesh (basic rig), the bones are already put in a decent order in the mesh file and there is only one root bone, so your code solution is not required.

Anyway, both my original code and yours give the same result.
So the bug is not about the order.

My for loop is

for(i=0; i<bonesNumber; i++)

and the mesh has one single root bone, which is bone 0.
After each bone is rotated, I do:

armature->processBonesLinking();
armature->updateBonesSkinMatrix();

inside the brackets of the for loop, and then I process the next bone (i++).
So I don't really think that the problem is about order.

I will try your code anyway and let you know.

I'm back working on my ragdoll system and I have problems.

I have a ragdoll made of ragdoll parts.
Each ragdoll part is just a parallelepiped entity which visually simulates the bone.
Each ragdoll part is in world space (they are parented only with constraints).
I have a characterEntity and its armature.
The armature should "follow" the ragdoll (and this is what is not quite working).

First, at the start of the game, I position and rotate each ragdoll part, copying the position and rotation from the bones.
Then, I let the physics run and each step I do the inverse: I rotate every bone to match the ragdoll part rotation, so the mesh should animate and fall down to the floor.

It works almost fine but there is some kind of offset, e.g. the leg's bone is ~15° off on the X axis in respect to the ragdoll part, the arm's bone ~ the same, etc.
The ragdoll is currently only about the skeleton, so it's not about e.g. the arm not being perfectly in line with the bone or uncorrectly colliding: I'm making a ragdoll of the skeleton only. Only when this works, I will attach actual body parts for the collisions.

My code is actually pretty long, complex, and separated into classes and files, I just can't post it all. But I'm pretty sure the problem is only about matrices and rotation, and lies here:

[...]
        //Ragdoll's part copys rotation from bone (works perfectly fine)
        MMatrix4x4 boneWorldMatrix = (*characterEntity->getMatrix()) * (*bone->getMatrix());
        ragdollPart->setEulerRotation(boneWorldMatrix.getEulerAngles());
[...]
        //Bone copys from Ragdoll's part (DOESN'T WORK)
        MMatrix4x4 myMatrix = characterEntity->getMatrix()->getInverse() * (*ragdollPart->getMatrix());
        MObject3d* parentBone = bone->getParent();
        if(parentBone)
            myMatrix = parentBone->getMatrix()->getInverse() * myMatrix;
        bone->setEulerRotation(myMatrix.getEulerAngles());
[...]

The grey lines are the ragdoll parts. They are in "x-ray mode".
The red little squares are the bones (the head of every bone).
In the image on the left, the game is just started, and everything is right. The ragdoll parts are positioned and rotated copying the bones position and rotation from the armature.
As soon as I activate the physics (only one step of physics), you can see how the bones don't match the ragdoll parts correctly.

Oh ok Doxygen automatically puts the link when it finds a class name.
But what if in the wiki I've something like this:

all the properties that will be used by the [[MPhysicsContext|physics engine]].

How can I simulate this in the header file?

Hi.
There are old information which was input manually e.g. bottom of MOEntity page.
I can easily put the general description of the class before the API list simply moving it before

{{:classMOEntity}}

but what about the old API information like this one:
http://wiki.maratis3d.org/index.php?tit … ties#Ghost
I guess it should be moved on the header files, although in this case you may loose the links inside the text.

Mmm.. doesn't work.
I'll try to set up a very simple and basic scene to do some testing with. It will take some time but at least I can be sure the error is somewhere else, I have too much code here.

Here I am again with my total lack of success with matrices and rotations. And I'm sorry to post again but I've lost way too much time on this trying to get it to work.
I'm trying to copy the rotation from a bone to another bone.
You provided me the code for copying the rotation from an object to a bone, here http://forum.maratis3d.com/viewtopic.php?pid=5346#p5346 , so I thought that basing on that, I could do:

                MMatrix4x4 myMatrix = (*entity->getMatrix()) * (*boneToCopyFrom->getMatrix());
                MObject3d* parentBone = bone->getParent();
                if(parentBone)
                    myMatrix = parentBone->getMatrix()->getInverse() * myMatrix;
                bone->setEulerRotation(myMatrix.getEulerAngles());

but the final rotation is not as expected.
p.s. I want to copy bone world position to bone world position.

No, I want to add keys that are not recognized. I was not able to find how Maratis read the input (from square one I mean, at the lowest level of abstraction) so I don't know what to change.

It uses autohotkey, you can't use it with Maratis.
Actually you can't use any GUI maker with Maratis, because you will always need some sort of interface between Maratis and the GUI maker so to be able to use buttons, etc, so you will always need C++ code.

It's in the to do list.