The svn is not up to date atm. but thank you very much ^^

They should both work 100% acurate. Please convert your testmodel using it and report bugs/errors.

Ah and yes. it WONT work with uvw texture coordinates.

I will try it later tonight (if i can find some spare time)

Of course I think that my obj parsing code is a big weak atm. Thats just because I was to lasy to put a "checker" in that is taking care bout this shit instead of make the programm crash.

Mjollna, your house6onemesh have dozens of errors.

You only have  939 texture pairs. But dozend of surfaces use indexies higher than that:

f 1031/844/939 1032/843/939 1033/865/939
f 1031/844/939 1032/843/939 1033/865/939
f 1031/844/939 1032/843/939 1033/865/939
f 1034/862/940 1035/864/940 1036/863/940
f 1034/862/940 1035/864/940 1036/863/940
f 1034/862/940 1035/864/940 1036/863/940
f 1037/863/941 1038/865/941 1039/862/941
f 1037/863/941 1038/865/941 1039/862/941
f 1037/863/941 1038/865/941 1039/862/941
f 1040/870/942 1041/869/942 1042/845/942
f 1040/870/942 1041/869/942 1042/845/942
f 1040/870/942 1041/869/942 1042/845/942
f 1043/850/7 1044/852/943 1045/851/8
f 1046/861/944 1047/859/944 1048/845/944
f 1046/861/944 1047/859/944 1048/845/944
f 1046/861/944 1047/859/944 1048/845/944
f 1049/873/945 1050/859/945 1051/861/945
f 1049/873/945 1050/859/945 1051/861/945
f 1049/873/945 1050/859/945 1051/861/945
f 1052/870/946 1053/845/946 1054/869/946
f 1052/870/946 1053/845/946 1054/869/946
f 1052/870/946 1053/845/946 1054/869/946
f 1055/869/947 1056/856/947 1057/846/947
f 1055/869/947 1056/856/947 1057/846/947
f 1055/869/947 1056/856/947 1057/846/947
f 1058/846/948 1059/848/948 1060/849/948
f 1058/846/948 1059/848/948 1060/849/948
f 1058/846/948 1059/848/948 1060/849/948

f.e.

Heh, thanks for your motivation your little .....

So. Whats up.
First of all: No progress. Im still in the same situation. The reason is that I noticed many new "problems" in the colligion chunks. So for example it turned out, that some formats i expected seems to be wrong. Other wow wmos seem to use a complete different notation.

fe. The Booty bay plank have a list of surfaces indexies that have to be used. Everything seems to be in a single BSP. No problem so far.

But at the other hand the wmo for a typical house (u had seen the screenshots before) dont act anything like that. The def Chunk does tiny indexies and use alot of chunks. The index list is no index list after all. It looks more like a bunch of flag def's.

So of course this have to be re-reverse engined. But as i said. I lack at motivation atm.

Okay. Here a short Update:

- Tintai is not dead ^^ The work will continue next monday
- It seems that the reformating algo needs a major update. Sometimes just bugs happends and I dont know why. Thats odd but well, have to be done
- The BSP Code have to be done, hopefully that it will kill many weird things that still happend.

Well. Beside of that I think redoing the wmo2obj code is also a good idea. I would like to insert new flags for many things. just as "export colligion data" or "bounding boxes" or flags for different materials. In other words: make more of the "how a wmo file works" visible in the export. In worst case and as least as comments.

tintai WMO 0.2      (c)2011 Tharo Herberg
Usage: test [-options] [files...]

where options include:
   -o <>
   -outdir <>         to set the output direcotry
   -? -help              prints this help message
   -version              prints product version

I got bored in the office and wrote an auto generating extended argument handler.
Its odd to be not able to test anything here -.-" If this keeps going on i will extend it by an "pass all arguments via xml" handler ...

In fact the reason for doing it is, that The wmo-generator as well as the wmo-injector both need tons of additional input infomations ..

So ok. Just did a quickie with the Abey Gate:

• Its Green. But yes that is because I was not updating the textures. In other words: I was to lazy. Ignore the missing textures - it is nothink important.
• No colli detection - that .. should not be like this. I could bet i told him to take EVERY surface for the detection. But nvmd .. Its just something to fix.
• Model is dissapearing - The screen is a manipulation (as sharp eyes can see). If you come to close to some parts of the model it will dissapear. This problem had been there before .. and its typical for "something gotta be wrong with your surfaces!" - This could be a problem of the mentoined sort algo ..

In fact i was surprised it worked "that" good after all. Seems that outdoor models will work pretty soon.

im afraid to tell that today i noticed several problems with taliis.
in other words: it seems that taliis is broken atm