[TOOL] OBJ to M2 converter + Sources

[fearless_wind]

Just awesome! First stable converter for static models)) Do you plan to make smth with other formats supporting animations?

[Arid]

Haven't worked on the texture but with the converter I've done a statue of one of my characters I roleplay on in D-X (They won't let me back on their modding team for SOME odd reason)

[Garthog]

Just awesome! First stable converter for static models)) Do you plan to make smth with other formats supporting animations?

Yeah, I plan to work on FBX format !

[fearless_wind]

Realy good news) So, you need to know that about 15% of  on wowdev wiki about m2 animation sections is wrong. Also one section with bone memory is unexplained at all. Now not  even one converter can convert animations rightly, even the Tigurius' one.

[Eliphas]

Excellent. Thank you.

[PhilipTNG]

Just awesome! First stable converter for static models)) Do you plan to make smth with other formats supporting animations?

Yeah, I plan to work on FBX format !

That'd be cool!!  Though there are a few different variants of it, which program are you using that generates fbx files?  3DS Max 2014 I reckon?

[Steff]

If someone know that dev wiki is wrong,  and even know how ots right.  Make an account and correct it.  This will help coders to do tools.

[fearless_wind]

Vel told me some information aboutr wrong information on wowdev. Sadly, he doesn't want to contribute to smth except his project. All I know is that one section about bone memory is unexplained on wiki and 15% of animation sections is wrong on wiki.

[Steff]

I know that Vel is not realy a teamplayer.  Make an account and write down what you know ;-)

 it will help to male this tool happen.  We will only get forward if we work all together.

[fearless_wind]

It's not needed anymore because as I know, Vel yesterday agreed to help Garthog with the tool)

[Steff]

But still it should be documented for the future.
It is always needed.

[LIMEEE]

it will help to male this tool happen.  We will only get forward if we work all together.

I am sorry Steff, but you really did serve me this one, if you say he should update the docs to help "everyone" out, maybe you should make noggit open soruce so actually people that want to add features / fix bugs, can do so, like you said, "We will only get forward if we work all together"

[PhilipTNG]

Alrighty had some free time so I tried this out, Door's UV's are messed up but I'm gonna delete the door anyway so no biggie.

[Garthog]

Anthony : this issue might be caused by texture coord not being set per vertex. Meaning multiple texture coords for only one vertice ( which is possible in 3DS / any tool, but not in wow. For WoW, one vertex must have only one texture coord )

one solution might be to convert to save to .3DS, then convert 3DS to OBJ with any tool ( not 3ds max ) and use the obj generated.

Another solution someone told me, is using two-sided renderflag ( dunno if it actually corrects it )

Last solution i got, is to detach all vertice

[PhilipTNG]

Anthony : this issue might be caused by texture coord not being set per vertex. Meaning multiple texture coords for only one vertice ( which is possible in 3DS / any tool, but not in wow. For WoW, one vertex must have only one texture coord )

one solution might be to convert to save to .3DS, then convert 3DS to OBJ with any tool ( not 3ds max ) and use the obj generated.

Another solution someone told me, is using two-sided renderflag ( dunno if it actually corrects it )

Last solution i got, is to detach all vertice

Thanks for the reply, anyway I went and the 3ds thing as you mentioned..... and exported to obj through Max, then imported it into Blender 2.6, exported out as a 3ds, re-imported the 3ds it into blender, re-assigned the texture, export to obj and used your converter, all was well after that.