Skip to content

Invalid TMM decoding of model names #2

@CryShana

Description

@CryShana

Hello there, I'm just a passing developer that is very interested in your progress. I found something that may help you.

The file armory_a_age2_damaged.tmm has 2 model names, and they aren't specified directly one after the other in the way your current code is decoding the model names. They have exactly 4x4 bytes in-between each other.

The first two bytes (out of these 4x4) are bytes you named HeaderEndBytes which are indeed always 2024, but in fact every model name has those bytes after it, not the header itself.

For reference, here are different 4x4 byte values from different TMM files:

E8 07 07 00 05 00 1A 00 08 00 2D 00 34 00 AC 02		- from "armory_a_age2_damaged"
E8 07 07 00 05 00 1A 00 08 00 2D 00 35 00 66 02		- from "armory_a_age2_damaged"
E8 07 07 00 01 00 1D 00 0A 00 0D 00 37 00 E0 02		- from "hoplite_gold"
E8 07 07 00 05 00 1A 00 08 00 20 00 20 00 5F 00		- from "villager_greek_male"
E8 07 07 00 05 00 1A 00 08 00 20 00 20 00 1C 00         - from "villager_greek_female"

I don't actually know what they are at this moment, but maybe you do.

The really confusing part to me is that the DataOffset (that we read before model count) actually points to an offset inside these 4x4 bytes, right after those 2 starting bytes "E8 07" (the "2024" value) of the last model name. So I'm not sure what's going on there yet.

So far I have not found any TMM files with more than 2 models in them. I'm not actively working on this, but I hope I can be of help

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions