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
The current address for chunk coords [[[[[[[WorldChrMan]+10EF8]+0*10]+190]+68]+A8]+18]+D0..D8 aren't actually chunk coords but some sort of player focus point.
They appear to be set to the local coordinates of the lock-on target when the player locks onto something.
The text was updated successfully, but these errors were encountered:
Yeah, the name is misleading. A proper name would be "local coordinates origin" or "physics coordinates origin", cause that's what they're used for. Here is what I recall working with them; it was quite a long time ago so if you find out any of this is wrong after testing please tell me:
They are the origin of the player's local coordinate frame expressed in the last loaded map's frame. The game periodically modifies them to minimize floating point error in physics calculations, which use the local coordinates. In particular, when there is no lock-on target, the game tries to keep the absolute value of each component of the local coordinates below 32. When there is a lock-on target, it uses the position of the locked-on entity (at the time of lock-on) as the origin.
The current address for chunk coords
[[[[[[[WorldChrMan]+10EF8]+0*10]+190]+68]+A8]+18]+D0..D8
aren't actually chunk coords but some sort of player focus point.They appear to be set to the local coordinates of the lock-on target when the player locks onto something.
The text was updated successfully, but these errors were encountered: