Cheat Engine

[GenevensiS]

Hello, I'm new to this, but from what I understand, there are additional steps that need to be taken to find pointer paths for games that are emulated?

When I do an initial pointer scan, I get 1.5k results, most of them start with "WinKawas.exe"+... (the name of the emulator that I am using),
but when I close and restart the emulator and reload the game, all pointer path found previously now point nowhere.
There literally just is a dash in the "Points to:" column.

How would I go about solving this?

Thanks for your help!

[Dark Byte]

all offsets need to be increased by the base address of the emulated memory base

or try the emurpm plugin which is in ce's github which lets you move that base to address 0

[GenevensiS]

Thanks for the response.

How can I find the base address of the emulated memory base ?

[Dark Byte]

That's emulator specific
Epsx2 stores it st 0x20000000 but others just allocate randomly. In which case you first need to find a pointer to the base
To find the base find a value that belongs to the emulated system and then check in view-memoryregions where the memory starts

You may also need some knowledge of the system being emulated, as some have split memory regions

[GenevensiS]

Okay, so I find a value in the game that is emulated (It's a Neo Geo game). It has address 03AB7931.

I look at the memory regions, there is one that starts at 039D000 and ends at 03BCF000.

So I should look within the emulator for a pointer to the address 039D000 ?

When I do that, I get the same problem that when I restart the emulator, all pointer paths to this address now point nowhere.

The memory region where the game sits also changes address every time I load the emulator.

How can I know if there are multiple memory regions?

Thanks again for your responses.

[Dark Byte]

You'll have to confirm that the address you found it actually the start of the emulated system , some emulators pad the memory with custom emulator info.

Also, are you sure the address you type was correct? Or is those one of those 716mbit cartridges ?

[GenevensiS]

Okay, so I think I just found a pointer to the address of the memory region.

I didn't find it earlier because I wasn't allowing negative offsets.

So now I have to replace all the pointer paths that I had:

"WinKawaks.exe"+[initial value offset 1]; [initial value offset 2];

with something like:

"WinKawaks.exe"+[memory region offset 1]; [memory region offset 2]; [initial value offset 1]-[memory region address]; [initial value offset 2];

Is that vaguely correct?

How can I do that for all the 1.5k results of my initial pointer scan?

My end goal is the be able to use the pointer path in Livesplit to make an autosplitter, so I'm not sure I can use the plugin you were referring to... could I use the results I find with it in another program?

[GenevensiS]

Yes, it is one of those 716mbit cartridges actually.
Why, do they have some sort of special quirk to them?

Because I'm pretty stumped, I tried adding the emurpm plugin, but even with that, I still get the same problem.
Every time I rescan for pointers, I get 0 results.

[Dark Byte]

if so, then perhaps the memory address will always be 03AB7931-039D000=371A931 bytes away from the start address of the emulated memory

so if you you can find a way to find the emulated base (e.g a pointer just to that) you may be able to use that to get to the destination address