[Problem] Cannot read the ChangeDirection

[Basser]

@Impulse
You could also use a breakpoint and look through all data first.

@Korvacs and Kinshi,
I know it has to be Input[22], so offset 22, but it doesn't work.
Why would the direction be above 200?

[Korvacs]

Direction should never be more than 7, it ranges from 0 -> 7 are you sure you have the right general data type? It should be 79. If your getting weird numbers like 200, sounds more like you have the action general data type which is 81.

[Basser]

Originally Posted by Korvacs

Direction should never be more than 7, it ranges from 0 -> 7 are you sure you have the right general data type? It should be 79. If your getting weird numbers like 200, sounds more like you have the action general data type which is 81.

Could it be that the offset is 18?
18 seems to be the only value changing, and always is below 8.

EDIT:
18 seems to work.
Problem should be solved, weird..
This may be closed.

[Korvacs]

Where are you counting your offset from? If your offset starts after length and type then 18 fits, if it starts before length and type then 22 fits. Although that could make sense if your using structured data packets.

[-impulse-]

Direction offset changed after some versions...

[Korvacs]

Originally Posted by -impulse-

Direction offset changed after some versions...

Well i was basing it off the various released 5165 source releases..

[Basser]

Originally Posted by Korvacs

Well i was basing it off the various released 5165 source releases..

It should be around 5165.
I think it might be 5173?
Is that possible?

[Korvacs]

If its 5173 its definately possible that the offset has changed.

[kinshi88]

Retail is still a byte at offset 22, doesn't seem likely they would change it, then change it back.
Dump the packet dude, it would be the easiest.

[Basser]

Why?
It works, Offset 18 works.

[kinshi88]

So you got it working then?

[Basser]

Yes, I have.
In this example it is 0, but 0 is also a direction.
I've made a circle, and it worked.