I'm having a really obscure problem when trying to edit memory via cheat engine. It works, but after enough changing values too much cheat engine will just fail to see the contents of the value and it won't be able to change it anymore.
Before freezing a value:
[
attachment=9763]
After freezing a value (this happens after a few seconds):
[
attachment=9764]
The really weird thing is that I don't get this problem at all when using Windows XP 32-bit, but I get the problem fairly quickly when running Windows 7 64-bit on the same computer. I've tried using different Dolphin revisions (various ones between 3.0 and 4.0) and it happens in every one I tried. It could be a problem with Cheat Engine, but I've also never seen this happen with any other program besides Cheat Engine.
Does anyone have a clue what's going wrong in this case? I could use Dolphin's native cheat support to do what I want to do, but cheat engine is a lot more flexible.
Cheat Engine is ONLY used for hacking programs (like PC games) or online apps (like the Facebook games).
If I were you, you´d better stop making tricks with Dolphin (using C.E.) before it gets wrecked.
You have to keep in mind that Dolphin has an easy-to-use cheat database for specific games, (don´t really know why are you messing with C.E.) while C.E. helps you modify the entire program (which it´s no use, at least for me).
Also, can you define "flexible" in this case, please?
I don't know how valid DJBarry's recommendations are, but I can tell you that setting Fastmem to False in Dolphin.ini will likely make it behave identically to XP (and incur a small slowdown). If you're using a 32-bit build of Dolphin on XP and a 64-bit build on 7, Fastmem is likely the cause, since it's only implemented in the 64-bit JIT.
You should use the built in features from Dolphin to do that. BTW, you said that C.E. worked fine in Windows XP, so, C.E. probably is incompatible with Dolphin x64 and this isn't new, seen that other programs that generally "inject" something in Dolphin only works with x86 builds (AfterBurner, Tridef 3D, etc)...
@pauldacheez: I used to make some hacks to Dolphin (including speedhacks), and in those times I was getting nothing but completely shitty results (it was just awful!!!!).
@Jhonn: That´s a posibility. AND it´s true that C.E. works best with X86 (not only Dolphin) software than X64.
I should point out that I've tried using x86 builds of Dolphin in Windows 7 and it still happens. I really don't have any clue why this works in XP but not in Windows 7.
(09-24-2013, 08:47 AM)DJBarry004 Wrote: [ -> ]Cheat Engine is ONLY used for hacking programs (like PC games) or online apps (like the Facebook games).
If I were you, you´d better stop making tricks with Dolphin (using C.E.) before it gets wrecked.
You have to keep in mind that Dolphin has an easy-to-use cheat database for specific games, (don´t really know why are you messing with C.E.) while C.E. helps you modify the entire program (which it´s no use, at least for me).
Also, can you define "flexible" in this case, please?
Flexible in the way that it has native support for more value types, it has more options for scanning memory and it allows you to define the freeze interval (I could probably do the same with dolphin if I edit the AR implementation and re-compile the code, but that would be a hassle).
(09-24-2013, 09:12 AM)pauldacheez Wrote: [ -> ]I don't know how valid DJBarry's recommendations are, but I can tell you that setting Fastmem to False in Dolphin.ini will likely make it behave identically to XP (and incur a small slowdown). If you're using a 32-bit build of Dolphin on XP and a 64-bit build on 7, Fastmem is likely the cause, since it's only implemented in the 64-bit JIT.
I have already tried 32-bit builds in Windows 7, but I tried adding this line to dolphin.ini anyway and it didn't change anything.
I did some more testing on this. I wrote my own small program for poking memory and that works without any issues, so whatever problem I'm encountering is on Cheat Engine's side. I haven't heard of anyone else encounter the same problem so it might be a rare bug related to my overall set up. I guess I'll work around this by using my own program for poking memory while using Cheat Engine for finding values.
(09-24-2013, 09:14 AM)Jhonn Wrote: [ -> ]You should use the built in features from Dolphin to do that. BTW, you said that C.E. worked fine in Windows XP, so, C.E. probably is incompatible with Dolphin x64 and this isn't new, seen that other programs that generally "inject" something in Dolphin only works with x86 builds (AfterBurner, Tridef 3D, etc)...
Dolphin doesn't have any usable built in features for this. Cheat engine works just fine with x64 dolphin, i use it all the time.
Oh, I thought cheat search feature in Dolphin could do that
Well, in theory, there are built in tools, they are just not reasonably usable, so it doesn't make sense to use them when cheat engine works really well already.