Search options (Page 10 of 60)

Hi,

you can follow the official code updates here : https://code.google.com/p/maratis/source/list

But there is also paralell developments, like from the user Dahnielson who is very active right now : https://github.com/dahnielson/Maratis/

It moves by waves, right now I don't have a lot of free time, so I spend most of my energy responding mails and forum questions related to Maratis. But I believe it's quite active for a small open-source project.

don't, it's a valid point, I'm just showing the pros and cons

A "not so good in english" french developer ?

Changing the default folders can cause some incompatibility with previous projects if not implemented correctly,
the examples and documentation will also need to be checked and updated. I'm not sure the trouble is worth it.

But, the folder names are only important for the publishing process,
it parses each specific folders to transform the files in binary or to add them to the package.

It's also used (in a cosmetic way) by the file browser in maratis editor :
"add entity" opens the meshs/ folder by default
"add sound" the sounds/ folder
etc

The Assimp importer also converts files directly inside the meshs/ folder.

Till you publish, you can actually use different folder names and everything will work,
you will just have to browse more folders when you import meshes.

So, let's say this naming convention is really a problem, I can force the publishing process to look at
all the folders inside the project instead of the current names. But, it will be a bit slower so I'm not sure it's worth it either.

The last option would be to specify the name of each folder in the maratis project file, so older projects could still use the current names, and the editor will be able to use the correct default folder when browsing files.

Actually, I checked the xcode again and the flag is there, so it's not that.

I checked the settings and tried different fixes but I don't understand what is the problem,
it might be an issue with the Clang compiler or with c++11 standard, but if I switch to gcc there is some different errors,
or it's a dependency problem.

Assimp code is not very attractive, specially to debug.

I will check deeper, but I need to go to Paris for some work, till Saturday,
so I'll come back to you later when I'm back home.

Hi,
read this : http://www.maratis3d.org/?p=277

good

yes, that's what I figured out, a non-uniform scale (not the same scale on each axis) can deform the rotation angles, it's a bit tricky.

Hi !

I should look again to be sure, but I didn't find the flags "ASSIMP_BUILD_BOOST_WORKAROUND ASSIMP_BUILD_NO_OWN_ZLIB" anywhere in the xcode project, or I missed it or it didn't get generated ?

What I specially have a doubt is the order of the matrix multiplication for the offset, I need to check my math.

What you should do to check this potential axis problem is to visualize the bones in space,
disable the physics and all the parenting of your ragdoll objects and copy the bones transformation to the ragdoll objects.
At least you'll be able to see how the bones are oriented.

MMatrix4X4 boneWorldMatrix = (*entity->getMatrix()) * (*bone->getMatrix);
*object->getMatrix = boneWorldMatrix;
object->setPosition(boneWorldMatrix.getTranslationPart());
object->setEulerRotation(boneWorldMatrix.getEulerAngles());

I don't see something wrong in the code, if you get the same result, your code is right too, but you should not call "armature->processBonesLinking();" multiple time in your loop (it's slow because it update all the armature each time).

So if it's not that, the problem should be that the bones and the ragdoll objects axis are not synchronized :
- because the ragdoll objects are not oriented the same axis as the bones
- or because the bones are not oriented in a consistent way

Lets say they are not synchronized, but you manually placed the ragdoll on the first frame.
You can calculate the offset matrix at the first frame and store it.
Then, when you update the bones, you use this offset.

I think I'm more Lity than Tity.
But the latter sounds better, damn... Am I wasting my life ??

The Xcode for mac is generated.
But there is some error when compiling :

STEPFile.h "STEPFile.h:198:64: Use 'template' keyword to treat 'To' as a dependent template name"

I don't have errors with Assimp when building with Scons, but maybe we don't use the same version, did you update the Assimp lib ?

Maybe missing the flags "ASSIMP_BUILD_BOOST_WORKAROUND ASSIMP_BUILD_NO_OWN_ZLIB" ?

Additionally (but not related to the previous error), I didn't see the flag :
"M_PACKAGE_WRITABLE" for maratisEditor (not needed for the player)

I'm also not sure the runpath search path is defined (depending on the dylib installation path) but should be "@rpath"
or "@executable_path/../Frameworks @loader_path/../Frameworks"

With the ios option it stops before generating the xcode project :

CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
OPENGL_LIBRARY
    linked by target "MaratisApp" in directory /Users/anaelseghezzi/Desktop/Maratis-ios/M/Additional/iOS