Working with Midway machines (mid?unit): tips?
Posted: Tue Jan 07, 2014 7:21 pm
Hi:
I'm looking for insight on how to more accurately pinpoint memory address changes on Midway MID?UNIT machines (working with UMK3 right now). Using the cheat engine on a "word" level provides me with the best results so far:
Using the above init, I have been mostly successful in detecting the memory addresses I've been looking for. There are some values that I know exist (and are incrementing / decrementing) but I am not able to detect them using "cn in, cn de, cn eq, #, etc". The reason I know they exist is because I was able to find the values I want stored in the NVRAM, but I haven't been able to detect them in memory while the game was running. The value is only a single byte in length.
I know that these machines handle memory space in a weird way. I am aware of the memory space offset (0xFF800000).
Is there a way to break down midway (MID?UNIT) debugging to the byte level (for doing cheat search analysis)? Another option that I have considered is to diff multiple memory dumps.
Thanks.
I'm looking for insight on how to more accurately pinpoint memory address changes on Midway MID?UNIT machines (working with UMK3 right now). Using the cheat engine on a "word" level provides me with the best results so far:
Code: Select all
ci uw, 0, 0xffffffff
I know that these machines handle memory space in a weird way. I am aware of the memory space offset (0xFF800000).
Is there a way to break down midway (MID?UNIT) debugging to the byte level (for doing cheat search analysis)? Another option that I have considered is to diff multiple memory dumps.
Thanks.