XeNTaX

The contents of this post was deleted because of possible forum rules violation.

Packed geometry commands, what might that mean?

Anyways I took a quick look at it, and the offset in the material struct that you have in the outline is the offset to the next material. If the offset == 0, then there is no "next" material and so you know that's the last one.

Then you can jump to the mesh offset.

finale00 wrote:Packed geometry commands, what might that mean?

Anyways I took a quick look at it, and the offset in the material struct that you have in the outline is the offset to the next material. If the offset == 0, then there is no "next" material and so you know that's the last one.

Then you can jump to the mesh offset.

Can you whip up a script or two for it?

Don't know the vertex format or how the faces are drawn.

Or even how to get to the vertices.

The bone struct is not consistent either. For example, many of them are 80 bytes, but some of them are bigger.

finale00 wrote:Don't know the vertex format or how the faces are drawn.

Or even how to get to the vertices.

The bone struct is not consistent either. For example, many of them are 80 bytes, but some of them are bigger.

Damn. So in other words, it's a spaghetti of sorts. As in a little more or less scrambled.

There's probably a value in there that determines how many extra bytes to read.
There are three offsets at the top of the file, and the material offset is easy to work out, same with the bones offset.

But then the third offset just takes me to the bottom of the file with a bunch of other offsets that I'm not sure what to do with.

finale00 wrote:There's probably a value in there that determines how many extra bytes to read.
There are three offsets at the top of the file, and the material offset is easy to work out, same with the bones offset.

But then the third offset just takes me to the bottom of the file with a bunch of other offsets that I'm not sure what to do with.

So, was it a lot more complicated than it seems to be?

It seemed complicated from the start cause I saw "NDS" and thought "must contain all sorts of ways to squeeze as much info as they can into a small file"

Upload a couple dozen more of different sizes (particularly objects that do NOT have bones).
Maybe it will become more obvious what the values mean.

I rarely get anything done with only one file.

For example, the third offset sends me to a section that tells me how many offsets there are, and it seems to coincide with the number of bones.

In fact, they may not even be bones despite being called "RightShoulder"

The contents of this post was deleted because of possible forum rules violation.

What did low lines use to decompress it.
I found a "batchlz77" tool for NDS games but it doesn't recognize this.

finale00 wrote:What did low lines use to decompress it.
I found a "batchlz77" tool for NDS games but it doesn't recognize this.

Might try asking him on how did he decompress the files, but he doesn't seem to be online ATM.

Decompress script: viewtopic.php?f=21&t=8373

You can see that some of the files don't even have that third offset and just end with what I would assume to be geometry data.

Thanks. If you need some more files to be RE'd, let me know. I actually needed the models for some game conversion, and, well, just for the lulz. I could've used them 3D ripping tools instead, but none of them work well on any DS emulator, perhaps due to the way how the DS GPU works.

Since the models are extremely small I wouldn't mind if you just uploaded all of them
That way I can go through them myself and look for what's good to compare with.

The contents of this post was deleted because of possible forum rules violation.