You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a second use of "Load textureblock" "sub_42D680(3);"
-the first is on Load Model function, because model and Textures are linked.
-the second is on a function witch
-read 4 bytes for cheaking (xx < 1700), else it's a infinity loop.
-copy 0x1A90u bytes in a global variable.
The text was updated successfully, but these errors were encountered:
Pretty sure you are talking about this (patched US version):
//----- (00447420) --------------------------------------------------------voidsub_447420() {
// Open textureblocksub_42D680(3);
// Read 4 bytes from the textureblock and swap it; this is the number of texturessub_42D640(3, 0, &dword_E9823C, 4u);
dword_E9823C=swap32(dword_E9823C);
// Ensure that we have 1700 or less textures, hang otherwiseif (dword_E9823C>1700) {
while(1);
}
//FIXME: Unknown// Global variable: `int32_t dword_E93860[1700];` - Texture pointers probably?memset(dword_E93860, 0, sizeof(dword_E93860));
// Close the textureblock againsub_42D6F0(3);
return;
}
There is a second use of "Load textureblock" "sub_42D680(3);"
-the first is on Load Model function, because model and Textures are linked.
-the second is on a function witch
-read 4 bytes for cheaking (xx < 1700), else it's a infinity loop.
-copy 0x1A90u bytes in a global variable.
The text was updated successfully, but these errors were encountered: