Cheat Engine

makotech222

Context: Using Cheat engine 7.1 (and 6.7) on latest YUZU release on D(iablo) 3

I'm using CE to find and freeze character's mana pool. I'm encountering a very weird issue i've never seen before. It seems that the CE scan sometimes skips over the address I'm looking for.

When I run the scan and get lucky, Ill find the Mana address (float) at value 200. I can freeze it and everything works fine. However, if I scan for the value again, CE will not show it in the search list! It seems to be skipping it over for some reason. I can fiddle with the Start/Stop addresses and sometimes get it to work again, but, usually the address is missing. I've tried fiddling with multiple settings like Fast Scan, but nothing seems to be working.

Most of the time, CE can't find the address, which is a problem when I boot up the game for the first time. I'm not sure whats triggering or causing this, so I'm posting here to get some hints of whats going on and why CE would miss the address.

ParkourPenguin · Posted: Sat May 30, 2020 10:34 am Post subject:

Perhaps it's not exactly 200. Try setting the rounding type to extreme, or scan for a value range like 190-210.
Some other value might be getting written to that address and the scan just happens to read that other value. I doubt this is the case, but you should look at what values are being written to that address regardless.

makotech222 · Posted: Sat May 30, 2020 9:46 pm Post subject:

Ah, i've tried that already. And in the first case, i already found and saved the value of 200. So i could already see what its exact value was; searching again however, cheat engine couldn't find it again.

makotech222 · Posted: Mon Jun 08, 2020 9:13 pm Post subject:

Bump, no other ideas? What situations would CE not read a value?

Dark Byte · Posted: Tue Jun 09, 2020 12:39 am Post subject:

so you did set the rounding type to extreme?

makotech222 · Posted: Tue Jun 09, 2020 7:47 am Post subject:

Tried multiple rounding types, but like I said, i've already found the value and saved it. Searching the same exact value brings up nothing.

ParkourPenguin · Posted: Tue Jun 09, 2020 10:17 am Post subject:

No one else has complained about this. It's something to do with what you're doing or some software on your system. e.g. poorly designed antiviruses can make non-thread-safe hooks in APIs such as RPM that cause undefined behaviour with CE.

Assuming it's not you or something else on your computer, it's probably the game. Look at the code that accesses that value and check what values are being written to that address. I made a script a long time ago that could do this here (use breakpoints instead of timers).

makotech222 · Posted: Tue Jun 09, 2020 11:42 am Post subject:

Oh its probably most definitely Yuzu related. I'm reasonably comfortable with CE and using it on many different games. Never seen this behavior before. Next time i find the address ill try and debug it a bit more.

Dark Byte · Posted: Tue Jun 09, 2020 4:37 pm Post subject:

Try disabling fastscan

makotech222 · Posted: Wed Jun 10, 2020 10:17 am Post subject:

Yep tried that already too.