Search options (Page 1 of 6)

Sorry, forgot to add that the script must be saved as 'premake4.lua' (posts edited)

Just a precision, MCore.so & MEngine.so are not required on linux as no linking is required.
You just need MSDK headers (includes). Look http://forum.maratis3d.com/viewtopic.php?id=825]here for more details.

For network using kNet, you can take a look at https://sites.google.com/site/maratis3d/home.

In lua you can use the isVisible(object) function.

Looks promising...

Awesome!

One thing to also keep in mind is that the mesh modifiers are automatically applied.

Blender 2.69 introduces a new FBX importer in its trunk, currently with severe limitations: only static meshes + binary format + version 2013. Hopefully a first step to full support...

Collada is intended to be a standard, but unfortunately you might often have issues, as more advanced features are not interpreted in the same way by different parsers, so weird results are possible.

Blender Maratis exporter is robust and allows to work seamlessly with Maratis. Related Wiki is self-explanatory. Maybe we could add a few tips and a checklist for easy "debugging", some things like "mesh has a material assigned?", "a mesh is selected?"...

For those who can't use Blender or have issues converting meshes, there is Noesis, a great freeware both versatile, robust and in constant development. Its only flaw is that it triangulates the meshes, but you can later switch back to quads in your favorite app.

For issues, maybe the tracker is not the best place as they are more likely due to user, not bug in themselves.
So we could do something like :
- submit an export issue in this thread with full console report, steps to reproduce the issue and if possible a blend file
- the community gives answer and update the wiki
- if a bug is actually discovered, we push it in the tracker, with a corrective patch if possible
In this way we won't overload Anaël and the community will get involved.

And for dynamic/procedural/non linear animations, you need to implement a library of this kind.

One easy way to solve the problem is to use ghost colliders (invisible planes/boxes with ghost physics).

You put a collider just in front of your obstacle (on the floor, on a wall...) and when the player hits it (collision detection) this triggers a specific action/animation.

So for example for a wall climb, you put a collider on the floor that triggers a climb (automatic or if combined with a key press) and one on top of the wall that triggers a transitional animation.