Hmm that's interesting actually. I would've thought both methods should ideally produce the same results, given the same index buffer lol

Hmm, there aren't that many models in the folder you sent though.
I'm wondering why it freezes on like, 20 files (when it loads C9 maps which is like, 60+ files at a time)

That's a pretty big difference in indices they're storing...
Did you release any code?

I think if someone can create a private server with that kind of feature they could probably port it as a stand-alone tool.

Here's the japanese mgame site.

Looks like they like cute stuff.

Anyone have a link to Furinkazan?
viewtopic.php?f=16&t=6479

Great, they have multilingual versions as well and the idstring is even longer. Looks like we can't just say "read 39 bytes". Instead, we should read 38 bytes, and then read another byte to see if it's a newline char 0xA. If it's not, then I guess we read some more... Or just read it one b...

Ya, it's just a typical inheritance structure. Naturally the generic parser (which would be an interface of abstract class in C++ or java) would contain a bunch of structs that are common and really don't change, while the child classes add or override things like NiMesh, NiDataStream, etc. as neces...

The nif docs indicates two version numbers: the engine version, and a "user" version. These are the 8 bytes after the idstring. If you've found two formats with identical versions but different structs for the same node...well that is a huge problem then lol. Otherwise you can do your type...

Alright it works. Ya, I use reload plugins when writing importers. For export, I just use command-line cause it's faster to test. The format I'm exporting to does not support dds (choices I have are bmp, tga, or png). This actually leads to several issues and design decisions when I'm writing plugin...

Did you call
Before committing the triangles?

How do I specify texture/animation export format in command-line?

Also it looks like I can't use outFile.tell() without it throwing an exception

What's the existing import script?

Which one.

Ya, the concept seems pretty straightforward and how they are stored can be pretty straightforward as well. I just never actually took the time to sit down, look at the examples, and see what kind of functions I will actually use. The plan was to just grab an existing format and re-write it in noesi...

Do you mean, you want to import the model, or do you mean the model is not imported correctly and the UV coords are wrong?