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
This function also seems to handle LOD selection, or even drawing:
intv51; // [esp+5Ch] [ebp-20h]intv52; // [esp+60h] [ebp-1Ch]
[...]
v27=-(dword_EC86BC!=1); // This checks the model distance settingLOBYTE(v27) =v27&0xFE;
v51=1934380868; // 'sLOD'v52=v27+2;
sub_450C00(v10, (int)&v51);
In turn, sub_450C00 is a function which resolves a handler for an object type (of a1; nota2).
The types are pointed to by off_4BFEC0 which points at off_4BFE98 which points at an element at dword_4BFD30 ['Test'], then dword_4BFD58 ['Toss'], etc. - These handlers also seem to be tightly packed. The DWORD[9] is a function to a handler which does something.
I assume the handler for the podracer (only Test seems to handle sLOD), will then handle the sLOD somehow.
The text was updated successfully, but these errors were encountered:
(Patched US version offsets)
sub_475AD0
seems to handle pods.Cases are:
This function also seems to handle LOD selection, or even drawing:
In turn,
sub_450C00
is a function which resolves a handler for an object type (ofa1
; nota2
).The types are pointed to by
off_4BFEC0
which points atoff_4BFE98
which points at an element atdword_4BFD30
['Test'], thendword_4BFD58
['Toss'], etc. - These handlers also seem to be tightly packed. The DWORD[9] is a function to a handler which does something.I assume the handler for the podracer (only
Test
seems to handlesLOD
), will then handle thesLOD
somehow.The text was updated successfully, but these errors were encountered: