Page 1 of 1

trouble using the mesher

Posted: Tue Sep 18, 2007 6:48 pm
by Beowulf
Hi,

I just tried to use the mesher for the first time but I'm getting a strange error that I cannot make any sense of. I used the blender python script to convert the model to xmesh and then tried

Code: Select all

florian@beren:victory1 [0]> mesher HULL_LOD0_None_HULL_LOD0_None.xmesh vsd-1.bfxm xbc
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::erase
Any ideas what I'm doing wrong?

Posted: Tue Sep 18, 2007 7:15 pm
by hellcatv
can you provide the .xmesh file on some website so we can see it...maybe it's got a mesh with 0 triangles or something odd

Posted: Tue Sep 18, 2007 7:23 pm
by Beowulf

Posted: Tue Sep 18, 2007 7:42 pm
by hellcatv
one problem could be the texture=""

why not fill in a correct texture---in fact why not add bumpmapping specmapping glowmapping and damage mapping while you're at it (texture4 texture1 texture2 and texture3 respectively)

Posted: Tue Sep 18, 2007 7:51 pm
by Beowulf
I get the same error even after inserting a texture and a specmap (the only two that I have at the moment for this model). Also shouldn't the blender export script fill in these values? I think I set everything up correctly texturewise in blender...

Posted: Tue Sep 18, 2007 8:55 pm
by hellcatv
I'll take a look at it more when I'm home and have access to the mesher

Posted: Fri Sep 21, 2007 6:37 pm
by Beowulf
This issue has been resolved, my mesher was broken. I recompiled it and now it works fine.

Posted: Sat Sep 22, 2007 11:54 am
by Beowulf
http://vegastrike.sourceforge.net/wiki/ ... MESH_files
in respect to which texture is which the wiki page is incorrect, isn't it?