Cheat Engine

[mordax]

Hi. ive been using CE for quite a while and i like the features it offers, i used to use Tsearch and ArtMoney, which are more professional tools, like terms are correct and not noob-friendly.
CE is quite noob friendly, for example "find out what writes to this address" > in professional term it should be "breakpoint, on write"


anyway those are little things that doesn't effect features and capabilites of CE, but what really annoys me is this:

In one game, i KNOW 100% that value is in Float and it is 0.2939032423 (yes, this exact whole string).
however when i search it in CE, i get 0 results, WHY???

NOTE - Value is there and i have not made a noob mistake by searching different memory range ..etc. if i do search on float - unknown initial value and then keep on changing between "changed" and "not changed" i will find that address, holding that same value and CE shows it up. i can add the address into cheat list too, works fine, but only if i do unknown search. even when i copy - paste the value and search exact value in float, still 0.
WHY is this happening?

Bug #2 - super annoying too. when i search for float, like 0.1 .. then why do i see results that say 0.2, 1.1, 1.2 ..etc ?? wtf? and NO, it is not because they changed, i can see results changing, but those values remain even after rescanning like 100 times for exact value "0.1" it still lists everything that is below and above 0.1 ..

I think float based searching is broken in CE or am i doing something wrong?

Only way i managed to search for 0.1, is when i do "range" search and put from 0.1 to 0.1 .. then it lists more or less values that have 0.1.


> yes i know i could basically convert float into 4 bytes, but why? if i have values written down in float, its just waste of time to convert them all, specially when game uses float values, where like health is 100 in float.

anyway, i just want to hear what people say about this

[Dark Byte]

bug 1:
For a float it's not possible to encode 0.2939032423
The closest possible value it can encode is 0.2939032316

Anyhow, you can find this value using the Rounded (default) format, or scan for 0.2939032

(the other 2 rounding options for float can only go up to 7 digits)

Bug 2
This is the fix for bug 1
if you scan for 0.1 you're scanning for an inaccurate value
Because you only provided 2 digits it will be a very inaccurate scan.
If you scan for 0.100000 the accuracy will be a lot higher, so less inaccurate results

(also fun fact, 0.1 can not be encoded. The closest encoding is 0.1000000015 or 0.099999994)

[Gniarf]