Re: Cheat Engine 5.5 Free Download For Windows 7 32 Bit
Lora Ceasor
Read before download: Cheat engine is for educational purposes only. Before you attach Cheat Engine to a process, please make sure that you are not violating the EULA/TOS of the specific game/application. cheatengine.org does not condone the illegal use of Cheat EngineDownload Cheat Engine 7.5
Read before download: You must be 18 years or older, or deemed an adult, to install Cheat Engine. Cheat engine is for private and educational purposes only. Before you attach Cheat Engine to a process, please make sure that you are not violating the EULA/TOS of the specific game/application. cheatengine.org does not condone the illegal use of Cheat Engine
Since some time after Dolphin version 4.0.2 (I'm not exactly sure when it stopped working), you cannot use Cheat Engine to find the start of a game's RAM addresses. Because of this, Windows users cannot use the newer versions of Dolphin with Cheat Engine, because the addresses always change every time Dolphin is opened, and there is no way to set up a pointer for the addresses. I can only confirm this for the 64 bit version of Dolphin, as I only use a 64 bit system.
That post has nothing to to with this one. This one has been a problem for a long time, and it is simply that you cannot find the start of the game's RAM address. You would normally find this by searching for the game ID as a string, and it would show up as xxxx0000, but this doesn't work with versions of Dolphin after 4.0.2.
If that's not it, I believe one of the game properties settings caused problems for my Cheat Engine scans at one point. I want to say it was Synchronize GPU Thread, or maybe something related to MMU. So you could try messing with one of those settings.
I have those settings checked in Cheat Engine, and it still doesn't work, even for that specific version of Dolphin that you specified. I messed with those settings as well, and got no different results.
Perhaps I should specify: I can load up Dolphin 4.0.2 and do the scan for the game ID, and I will always find the address that it is supposed to be. Then, I can open a newer version of Dolphin, open it in Cheat Engine without messing with the settings at all, and do the scan, and the correct address will not show up. So to sum that up, Cheat Engine is not the problem.
Hmm... so on newer Dolphin, what addresses does the scan turn up for you? I actually tend to get 3 or 4 addresses ending in 0000 when I scan with a game running. For example, on 4.0-7365 I get 7FFF0000, 27FFF0000, 2FFFF0000, and 33FFF0000.
Those addresses do show up, but they will not work. You need addresses that are not that far into the memory. For example, on 4.0.2, the one that works for me is around the 0BD00000 area, and it can increase/decrease depending on how much memory is being used by my computer at the time.
I actually don't ever remember getting the 0B... address to "work" as far as finding useful addresses (such as position, velocity, health, etc.), yet I was able to work with 7FFF0000 and later. Maybe both of them work, but the offsets to find the useful addresses are just different?
You could try re-scanning for the addresses you are interested in (position, health...) and keep track of them based on, say, 7FFF0000. See if the address offsets remain consistent when you restart your game and restart Dolphin. Maybe the offsets will be different from what you were used to before, but as long as the offsets are consistent, that base address should be usable.
This is the problem though. The offsets do not stay the same. Every time you close and reopen Dolphin, the offsets will change. So if you use 7FFF0000 as the base, the offsets will change every time. Therefore, you can't use 7FFF0000 as a base address.
Does the offset from the base address change too? Just to be clear, here's what I mean by the offset: in Super Mario Galaxy, I can find the X value of the control stick input at (base address) + 0x61D3A0. So here I call 0x61D3A0 the offset of the X stick input.
If you are saying that the offset of something is changing with respect to the base 7FFF0000, but is constant with respect to the base 0B..., then maybe I'm on the wrong track here. I've only worked with RAM watch for a select few games so I can't claim to have seen everything.
The offset from the proper base address does not change. If I were to use 7FFF0000 as the base address, several problems would occur. For starters, I am 100% certain that all of the game's RAM actually ends before that address. If I tried to apply an offset to this address, it would have to be a negative one, which does not work properly. Secondly, 7FFF0000 will not ever change, while the game's addresses do. This would cause the offsets to change. Obviously, the offsets are not supposed to change, otherwise the pointer wouldn't work in the first place.
The offset from the proper base address does not change. If I were to use 7FFF0000 as the base address, several problems would occur. For starters, I am 100% certain that all of the game's RAM actually ends before that address. If I tried to apply an offset to this address, it would have to be a negative one, which does not work properly.
Secondly, 7FFF0000 will not ever change, while the game's addresses do. This would cause the offsets to change. Obviously, the offsets are not supposed to change, otherwise the pointer wouldn't work in the first place.
I've found that many interesting values do have their addresses changing, yes, even as the base stays the same. But these values can often be reached with a two-level pointer from the base address. Again taking Mario Galaxy as an example, there's a value I call the "reference pointer". To find the reference pointer, I first take the value at the address (base + 0xF8EF88), then add base to that value, and subtract 0x80000000. Then, for example, I can find Mario's XYZ position at (reference pointer + 0x3EEC).
While it's not the easiest thing to reach interesting addresses this way, it is possible. I haven't had a ton of luck with using CE's address list interface to keep track of multi-level pointers, but I've made a Lua script demonstrating this kind of thing if you are interested ( -watch-cheat-engine/).
The RAM addresses for games in Dolphin don't go anywhere near 7FFF0000. From the base address, the end of the game's RAM addresses is usually around 0x330C040 away if you apply it as an offset. So if you apply this to the base address that I stated earlier, it doesn't even come close to 7FFF0000. So yes, there are no interesting addresses after 7FFF0000, or even close to it.
I'm not sure where I stand on this as far as Dolphin issue tracking is concerned, since I'm not sure how much the RAM layout is under the developers' control. As far as helping you RAM watch your game, though, maybe someone could help further if you provided a specific game and address example?
b1e95dc632