Cheat Engine

[KalasDev]

I know you can find those via Memory View but Is there a way with Dissect Data?

Anyone Got a Tutorial on this and can share?

[Filipe_Br]

This video should help. Game Hacking: Technique To Find No Recoil/No Spread /Accuracy

[KalasDev]

Oh yea I know this guy, He is great but he said there are more ways of finding those values, Is there any other tutorial you know that might explain it with other technique.?

[SunBeam]

Why don't you tell us the game you're playing and how you can't find those? It would be much easier than running around in circles, asking volatile/masked questions.

[KalasDev]

Oh I just thought It's pretty much the same on Shooter games, like same technique.

For example Dying Light, I tried looking for it in Memory Viewer exactly like the video Filipe Posted above, I just can't understand how to find one of the 3 features, Is there any way you can help me out ?

EDIT: Dying Light does not show those values in Memory Views, It does but It's not located near the Ammo whatsoever.

[SunBeam]

I use the same technique this guy uses in his video, but not starting from the clip or magazine ammo. I simply look for an unknown value (as float) when the crosshair spread is expanding, then 0 when not focusing. As for recoil, value (or values) is 0 when not doing anything. When shooting, they increase (so pause game, and look for 'has increased'). The only way to test once you have a few addresses left in your search result is to freeze their values. The one(s) that keep recoil/spread locked should then be debugged

BR,
Sun

[++METHOS]

Techniques may vary, depending on how the data is being handled and how the target has been programmed. Using data structures is a great way to find useful values - just be sure to set your update interval to 1ms and clone/lock your data structure for comparative analysis. Using speedhack on the target can also be helpful for values that rapidly revert back to their default state.

[KalasDev]

[++METHOS]

Oftentimes, such values are stored inside of the same data structure. So, finding any relative weapon values can usually point you in the right direction (e.g. current ammo value, clip/reserve ammo value).

Once found, check to see what is accessing the address. The debugger window should open and populate with a list of instructions. Here, you will be able to get a better idea regarding what the relative offset is to the base of the structure (e.g. if the instruction is mov [eax+80],edi then your ammo address is most likely +80 offset from its base address). This usually won't matter much, however, unless you see different offset values being used for various instructions.

From there, you can click to view the instruction in disassembler (after clicking stop in the debugger window). With the instruction highlighted in memory viewer, you can right-click on it to see what addresses it is accessing. A new window should open. In this window, with the ammo address highlighted, you can right-click and select 'Open dissect data with selected addresses'. Now the work begins.

EDIT:
User deleted previous post, so this response does not make sense.

[KalasDev]

Ok I understand, It's pretty much what I was thinking, Bad English sorry and sorry for deleting my previous post I just didn't knew if to keep or delete.

[STN]

nvm my post doesn't make sense either. removing what i posted....

[KalasDev]

Is there any way of increasing my Cheat Engine progress, It's really slow and effects my Computer, I know I need an SSD but Is there any other way ?