xpunkrockyugox wrote: ↑Sat Aug 22, 2020 5:28 pm
I've been looking at the picture, opening up the files in AMR and even trying to look at it in a hex editor
EVEN? Observing the data within a hex editor is what you're supposed to start with.
xpunkrockyugox wrote: ↑Sat Aug 22, 2020 5:28 pm
but could I possibly ask where you got the numbers from in the Grem screenshot?
Refer to the below image:
gremlin_ibuf_grouping.png
As you can see the indices are in ascending order as they generally are. And you'll encounter the 1st jump discontinuity, or say, a pretty obvious gap between the two values, at address 0x5364. Then the indices are ascending again untill you encounter the 2nd jump discontinuity at address 0x53C4, and so on you'll find the 3rd jump discontinuity at address 0x71A0, and the 4th at address 0x7278. Then you can test these indices in AMR using the address of the jump discontinuities you found, combined with the addresses of different vertex chunks in the vbuf file, which can be acquired only from a hex editor.
Then you'll see the indices between the 1st and the 3rd jump discontinuities actually belong to the same submesh group, so as those from the the 3rd jump discontinuity to the end of file. So all together there're 3 submeshes, as you've seen in my previous post.
xpunkrockyugox wrote: ↑Sat Aug 22, 2020 5:28 pm
I have to say, it's really amazing and impressive that you can do this hex editing and params stuff so easily!
So you see, it's nothing magical but only some trials and errors based on experience. And it's obvious that you can't handle such cases without looking into the data itself. So I suggest you to learn from the beginning. Check the 1st link in my signature if you're interested.
You do not have the required permissions to view the files attached to this post.