Moin,
@U-snafu:
Someone must do it, right?
@ref:
I forgot to mention some additional information.
Quote:
|
Originally Posted by ref
...I'l have to figure out a logic for that ordering before starting to write anything, I'll check other commonly used animation formats (quake, etc.) to see if they are similar, ...
|
Itīs an issue of the 3d graphics program. The logic your searching for will be found in the *.obj file. Open the COUNTRY_FLS.obj with any hex editor and youīll see that the vertices are stored in this order. I assume that the COUNTRY_FLS.obj file (Type 1/101, size 2389) tells SHIII the texture coordinates and determines the verticesī order. My problem is that the vertices in the *.obj file are described by 24 bytes (8 bytes per axis). But the frames use 6 bytes only at 2 bytes per axis.
EA 93 B1 36 46 7E 71 3D controls the size. Iīve managed to resize the flag but unfortunately not to the exact size I wanted to. Setting the first 3 bytes to
FF results in a smaller flag, setting them to
00 results in a bigger flag. Changing the fourth byte (
36) to values lesser than
35 or higher
37 results in disappearance of the flag. I think itīs getting to small/big to see when exceeding 35/37. Note that the flagīs
position changes when altering these values. The highlighted values (.. .. ..
36 .. .. ..
3D) are the same at the beginning of each frame. So I assume that the first three bytes define the position of the "basic" vertex. And that would be vertex #
6/
25, I guess. All three values (X,Y,Z) are the same (7CD4 7CD4 7CD4).
36 seems to be some kind of multiplier. The following three bytes possibly define the last vertex in the row. But Iīve no idea about the last byte (
3D) then!??? I canīt imagine they use four bytes to define the position.
I would be content with a tool that converts all vertices to the 6 bytes format. Hope you manage to write your tool asap.
Regards,
DD