Ah I see, that sounds great!
Hm, I understand. Do you think a data loss is acceptable since we aim for wc3 models ?
Therefore information not being relevant for the wc3 engine could be exluded.
If you ask me myself, I would be absolutly happy if it only supported mesh transfer,
the data that is basically shown in a mdl file, or also less,
like only the information about the model structure, vertices and stuff and
the texture coordinates of the wrapping.
I read a bit through some threads and it seems supporting animations is hell to do or not even possible in OBJ ?
If it is after me, that could be easily exluded.
My suggestion would be to import the mesh, vertices/tris and their texture coordinates, and then generate a bone as a node to attach everything to it.
Similar to importing a geoset to Magos. Everything else would be great,
but not necessary from the aspect of a modeller, I suppose.
Our main concern is to be able to actually convert appropriately and if our
favoured tool supports this feature, it would be awesome!
About the texture paths being wrong, one can easily edit them, can't one ?
For me myself this would be an aesthetically aspect that is not absolutly required to use the tool.
I would be more than ready to test converted files and compare them to the original ones!