I'd probably know more than nothing if you did.

I was hoping in that year, I would be able to load up skeletons and animations as well.
Lol. Never found the motivation to go further.

Here's the rest of the source (well, all the ones in the same folder anyways, there's a lot of source...)
Most of them are irrelevant.

I'm not sure which ones you might need lol

I'm getting the path of the directory using "rapi.getDirForFilePath(rapi.getInputName())", but it seems like in command line mode, the directory is just the empty string? Or at least, I have no idea what the current working directory is. Trying some more things, it looks like if I just ask...

Don't know, don't have the game nor the files.

Yes, I only need the bounds for the entire model.

Probably just another archive...

The 3ds files are just archives, not models.

Lol there are many different data stream chunk. In catherine and microvolts I think the blender import had like at least 7 different NiDataStream chunks (124, 128, 24, 30, ....) I wouldn't mind updating nifskope's XML file to parse the new structs, but...well, sort of lazy to read docs. For construc...

Db4, from illusion.

It stores data in another archive with the same name. I think that is what the other data buffer is for?
I could upload all the other code in the folder but most are for other games.

Think you could write some code to parse out the file entries?
lol then I can just focus on extracting the data.

mesh.uvs contains a list of vec3's.
I don't need the 3rd value. Fastest way to get it?

What I'm doing now

Probably wouldn't happen often. Not the kinds of things I expect people to be using it for anyways. Also, not sure how bounding boxes work, but the format I'm working with requires me to calculate the bounding box for an arbitrary model. Previously I just grabbed the "max" and "min&qu...

Oh ya, I just noticed all of the textures were being exported lol If a model used a large number of textures would it take a significant hit on performance? Like sure if it's only 4-5 small textures it probably isn't too bad but some models seem to like to have a whole bunch of textures, especially ...

That sounds like it would basically result in all plugins I write exporting the textures while it's parsing the file *just in case* they wanted to export to this particular format that stores textures inside the model file?