Skip to content

skipping UNKNOWN1 causes massive issues#3

Open
WeaselOnaStick wants to merge 1 commit intoTelltale-Modding-Group:mainfrom
WeaselOnaStick:main
Open

skipping UNKNOWN1 causes massive issues#3
WeaselOnaStick wants to merge 1 commit intoTelltale-Modding-Group:mainfrom
WeaselOnaStick:main

Conversation

@WeaselOnaStick
Copy link
Copy Markdown

@WeaselOnaStick WeaselOnaStick commented Oct 23, 2024

As far as I understand UNKNOWN1 is the size of UV Transforms block, and wasn't utilized in TWD games (size 0). But in Sam&Max remasters I'm working with it's used quite often. For now I'm just skipping the blocks (size 20 = Int32+4xFloat32) but you should probably make appropriate vectors. I'm not too knowledgeable in the code base for that.
This should probably be renamed to something like mUVTransforms in the future too

So far I can only verify that the converter is reading data correctly, by comparing vert counts and objects/MeshBatches count
image
image

This should probably be renamed to something like mUVTransforms in the future
@Lilothestitch16
Copy link
Copy Markdown

How did you port that in Blender?

@WeaselOnaStick
Copy link
Copy Markdown
Author

How did you port that in Blender?

I'm developing my own d3dmesh importer for blender

@Lilothestitch16
Copy link
Copy Markdown

That looks cool.

@iMrShadow
Copy link
Copy Markdown

A little bit too late to this conversation, but these are indeed UV transformation blocks which consist of an index and 2 2D vectors (scale + offset). The index stays less than 4, presumably indicating the order of the transformations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants