Problem with updating position

[RoKFenris]

or use Method B :

class CMovementInfo
{
public:
    char		unknown0[16]; //0x0000
    float x;	// 0x10
    float y;    // 0x14
    float z;    // 0x18
    float unknown1c; // 0x1c
    float direction; // 0x20
    float tilt;      // 0x24
    float		unknown[4];    // 0x28 
    OBJECT_GUID TransportGuid; //0x0038  
    DWORD       NewIn3_1;  //0x0040  
    DWORD		MoveFlags; //0x0044  
};

enum MovementFlags
{
    MOVEFLAG_MOVE_FORWARD  = 0x01,
    MOVEFLAG_MOVE_BACKWARD = 0x02,
    MOVEFLAG_STRAFE_LEFT   = 0x04,
    MOVEFLAG_STRAFE_RIGHT  = 0x08,
    MOVEFLAG_TURN_LEFT     = 0x10,
    MOVEFLAG_TURN_RIGHT    = 0x20,
    MOVEFLAG_PITCH_DOWN    = 0x40,
    MOVEFLAG_PITCH_UP      = 0x80,
};

class OBJECT_STRUCT
{
public:

    ...
    CMovementInfo* m_pMovementInfo; // at pObject + 0xD8 !!!!
    ...
};

Greetings

Apollo

I believe you need to recheck your movement structure. The TransportGuid is now at offset 0x08, I'm currently using it on my radar project.

[dskle]

Thanks for the feedback guys, I've experienced the same issue (xyz not updating while holding down a movement key). I will try the suggestions listed.

[Jadd]

This does not answer the question....

i read from wow.ReadUInt(wow.ReadUInt(wow.ReadUInt(baseAdress) + 0x34) + 0x24) the playeradress and then using 0x7D4,0x7D8,0x7DC as offsets.

That's because those are the wrong offsets.

Change these:
0x7D4 -> 0x798
0x7D8 -> 0x79C
0x7DC -> 0x7A0

[dskle]

Several people have suggested the same "fix", that is, the same offsets. Having the correct offsets is not our issue.

The issue is the fact that the coords do not update in real time as we move the char. However, once the input key (wasd, mouse left+right, etc) is lifted, ie. wow input is idle, then the coords are updated.

I am still trying to figure this out, and at this point my best guess is it is something to do with the way we have implemented a thread/loop that is periodically reading these values in the background.

[flo8464]

Several people have suggested the same "fix", that is, the same offsets. Having the correct offsets is not our issue.

The issue is the fact that the coords do not update in real time as we move the char. However, once the input key (wasd, mouse left+right, etc) is lifted, ie. wow input is idle, then the coords are updated.

I am still trying to figure this out, and at this point my best guess is it is something to do with the way we have implemented a thread/loop that is periodically reading these values in the background.

No, its the issue.
The offsets I used before showed the right coords, but delayed.

The ones people here mentioned are working perfectly.

[unbekannt1]

Yes with the "right" coords the values are updated live

[dskle]

Ok, I thought that might be the issue, but just not as likely. In any case with the coords posted (the ones I'm using) they are not updating in real time. I guess I'll keep messing with it.