Mshex/Mshex4Max/Meshtool source code / MSH documentation

[RepSharpshooter]

Upon request, I have released the source to these mesh programs. I coded these as a highschooler, so they are a bit disorganized. Mshex4Max is the most organized, because it uses object oriented programming. All are written in C++

Contained in the mshex/research folder is documentation on the msh file format that was once posted online (may be gone now). It can serve as reference to people writing new tools to for with msh.

Download link:
http://www.mediafire.com/download.php?iuzbb175mjbici0

[Cerfon Rournes]

Awesome! Thanks Rep!

Hidden/Spoiler:

Nice to see you on Gametoast.

[AceMastermind]

Thanks for sharing! There has always been a lack of actual source code for inspiring programmers to work from regarding the msh format and this will provide a great way to incorporate new or modified features without having to rewrite an import/export program from scratch every time.

[THEWULFMAN]

Thanks for releasing these, I'm sure they will be useful sometime. Nice to see you around Rep, good luck with college.

[tirpider]

ZOMG, Awsome!
Thank you for releasing this, RepSharpshooter.

I'm looking forward to seeing some real code that handles these files.
I've been re-inventing the wheel, just trying to get the msh info into editable listboxes.

[RepSharpshooter]

No problem, I hope they go to use somehow.

Like I said, the first mshex was coded very sloppily, yet it runs for the most part. The comments also have my deranged ramblings I'm not sure if even I can make sense of it.

Mshex4Max is more properly structured, so it should be used as a better reference on how to handle the msh file. It lacks .XSI import algorithms, but combining the old ones from Mshex wouldn't be that hard.

[tirpider]

Definately going to be useful.

I wont be able to directly use your functions as I am writing with autoIT (a basic like scripting language.) But I can get a good look at how to handle the various tags in memory.

Right now I'm stuck with arrays (big, slow, and smelly muti-dimensional ones.) But with no programming background, basic and arrays will have to do.

The end result will be a stand-alone MSH specific hex editor thing. With controls and features built in to handle repetitive and complex tasks associated with post xsi tweaks.
(updating size fields, validating known datatypes, import/swap features(tags and chunks), validating tag sequences and prerequisites (ie making sure MODLs have TRAN and FLGS if they need it), and ultimatly, direct manipulation of the vertexes and strips.)
It will also be usefull in determining the structure of some of the unknown tags, possibly paving the way for converters that can handle collision meshes.
I plan on releasing my source as well, once it gets out of alpha.

So, yeah, your source is the only example out there. And your tools are solid.
I'm definatly looking at it.
Thanks for writing them, and super thanks for releasing the source.

[ANDEWEGET]

Yes, thank you very much! Youve done me a great favor with this.
@tirpider: Actually its possible to "decompile" Nimlots msh tool(forgot the name) into any .NET language(C#, IronPython etc...).

[naru1305]

wow, thx for these codes, they will be ver useful