Page 2 of 12
Posted: Fri Jun 15, 2007 5:49 am
Thanks for that, too. This tool is really helpful.
The syntax with the help text is a bit misleading, though, but works great.
Posted: Sun Jun 17, 2007 4:40 am
I used to rely on 3dsmax for small scaling/translation tweaks to source meshes, but when I didn't have access to it I was forced to use blender. Blender was quite hard to use and I ended up being forced to hard code minor mesh specific tweaks in my application. I was going to write a tool like yours so I can remove them, but now hopefully I don't need to.
Posted: Tue Jun 19, 2007 4:11 am
Great tool, thank you!!
An option to combine different meshes in an only mesh (interpreting different meshes as different poses of a same mesh) would be useful too, for exporting mesh poses when using exporters that can't deal properly with pose & pose animations.
Posted: Fri Jun 22, 2007 2:57 am
I've found this tool to be really handy, too.
Thanks for sharing.
Posted: Tue Jun 26, 2007 6:30 pm
I'm really excited to use this tool but can't run it for some reason. I get the error "The system cannot execute the specified program" when I run it from dos at c:\meshmagick with "MeshMagick transform -rotate=90/0/1/0 robot.mesh."
And when I double click MeshMagick.exe, I get the error "This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem."
Am I missing something obvious like putting the exe somewhere in the Ogre directories?
Posted: Tue Jun 26, 2007 7:58 pm
very usefull, thanks!
MeshMagick incorrect configuration
Posted: Fri Jul 06, 2007 7:54 pm
I have not been able to run the program.
I get the following message.
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem
I tried putting it with all the DLL, models, etc.
I get the same message. I'm not sure what it is looking for.
Help would be appreciated.
Posted: Fri Jul 06, 2007 8:07 pm
Hi Skorpio, this error is most likely because you don't have the microsoft C++ runtime libraries installed in the needed version.
You can download the package here: http://www.microsoft.com/downloads/deta ... laylang=en
Install this and afterwards meshmagick should work.
Posted: Tue Jul 10, 2007 5:37 pm
Thanks for the help haffax. I have successfully rotated the ninja.mesh with magickmesh however an exception is thrown when running Ogre with the rotated ninja.mesh.
Error #: 9
Description: Cannot find serializer implementation for current version [Mesh Serializer_v1.40].
Stack unwinding: <<beginning of stack>>
What do I do to fix this?
Posted: Tue Jul 10, 2007 7:05 pm
tarenar, your Ogre is an earlier version than the one used to compile MeshMagick. When a mesh is modified by default MeshMagick updates the mesh-version to the latest version, with currently is v1.40, which can't be read by your Ogre.
MeshMagick has a global option called -keep-file-version which does not update older mesh files to the new file version. Using this option your file can still be read by the ogre version you use.
Posted: Tue Jul 10, 2007 10:02 pm
Thanks for the quick response haffax. So i entered: MeshMagick -keep-file-version transform -rotate=90/0/0/1 ninja.mesh
And according to the output, all of the transformations worked fine. However when I ran the mesh in ogre, I get the following exception:
Error #: 9
Description: Missing M_EDGE_GROUP stream.
Stack unwinding: <<beginning of stack>>
It seems the ninja refuses to rotate without a fight
. Thanks for any suggestions.
Posted: Wed Jul 11, 2007 10:46 am
Hmm, this can be because of a change from mesh version v1.30 to v1.40 that might make using an old serializer for the new format fail in some cases, here with edge lists. I will have to look into it. What Ogre version do you use?
Posted: Wed Jul 11, 2007 5:02 pm
I'm using v1.23. Hah, didn't realize how old of a version it was until now...
Posted: Wed Jul 11, 2007 5:41 pm
In that case, updating your Ogre version is probably a good idea anyway.
Posted: Thu Jul 12, 2007 5:38 am
great work thanks
Posted: Thu Jul 12, 2007 6:38 am
First, thanks for making this. I'm finding it very useful.
Here's a patch to allow bootstrap with automake > 1.9:
Code: Select all
RCS file: /cvsroot/ogre/ogreaddons/meshmagick/bootstrap,v
retrieving revision 1.1
diff -u -r1.1 bootstrap
--- bootstrap 15 May 2007 21:09:53 -0000 1.1
+++ bootstrap 12 Jul 2007 05:34:01 -0000
@@ -17,7 +17,7 @@
-if test -z "`automake --version 2>&1|head -n 1|egrep '1.[6-9]'`"; then
+if test -z "`automake --version 2>&1|head -n 1|egrep '1.([6-9]|[1-9][0-9])'`"; then
echo "Automake 1.6 or above is required. Aborting build...";
Second, it would be great if you could add a build target that would statically link with ogre. The reason this would be useful is that I'm often switching between what ogre version is in my default library path. It would be nice if I could just statically link it and not have to recompile it very often.
Posted: Thu Jul 12, 2007 8:45 pm
btmorex, thank you for the patch, I will apply it. As for the static linking in Linux, this is something Blakharaz has to decide and implement, because I don't have a clue about Linux but he does.
Posted: Sat Jul 14, 2007 11:11 am
I ran into some problems with the meshmagick today...
for static meshes it works great...and for some skeletal animations as well...
But when i tried to scale my character the jumping animation went crazy. On the same mesh an animation where he just turns his hip forward and backwards everyting goes fine. But in the jumping animation (where the root bone is moved up and down) the whole mesh moves up and down (in unscaled motion).
To clear things out: in the original file the mesh never leaves the ground. In the scaled, the mesh goes straight to the floor and up again. It is as when he crouches to gain speed the root bone takes the whole mesh with it and as aI said..that motion is unscaled.
The same scaling works perfectly inside of Ogre with setScale().
Has this happened before?
Posted: Sat Jul 14, 2007 2:36 pm
Hi oddrose, did you try the binary version or the version in CVS?
I have fixed a few bugs regarding scaled animation which makes it work with our project's meshes among others I resolved this very issue. But there is (at least) one outstanding bug.
So if you tried binary please use the version in CVS and see if it works for you, else you have to wait a little while. I'm currently busy with another project and gsoc and can't do much in MeshMagick right now.
Posted: Mon Jul 30, 2007 7:57 am
Posted: Mon Jul 30, 2007 8:43 pm
Oh, thank you smernesto.
I take this as a cue, that I should really do a page with detailed instructions.
Though I have many projects running in parallel now, don't expect it to be done by tomorrow...
Posted: Mon Jul 30, 2007 9:46 pm
This is great haffax. I think this tool is the kind of thing that you don't realize you can use until it is available. Now I can see it incorporated into so many pipelines.
Posted: Mon Jul 30, 2007 11:23 pm
I really needed this tool! is very useful.
Posted: Thu Aug 02, 2007 4:19 pm
Very handy. I just added a few extra reporting features to it, because I needed them:
- Reporting default material name on SubMesh
- Reporting number of bone assignments per vertex
- Reporting total bones (out of the possible entire skeleton) referenced by a single set of vertex data
Posted: Thu Aug 02, 2007 8:16 pm
Nice additions, thank you Sinbad.
I'm glad you all find the tool useful.
As I mentioned earlier I'm open for input about what additions you find useful, as long as you can name a practical application for this.
I locally started work on a new tool called 'reorganise'. This is meant for unifying the structure of our project's mesh files. Options to change tangent semantics (tangents<->texcoords), add/strip LOD, edge list, shared vertex section and reorganising the vertex buffers with a simple syntax. But it is nowhere near ready for a commit and progress is slow, because of work load in other projects..
Btw, in the mean time Blakharaz added a new tool 'rename' that allows renaming materials, bones, animations, etc. It's working and already in the CVS.