Ram Search issue with some values in N64 game(s)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start a file of the european Majora's Mask debug ROM
2. Try to find the value of the current amount of bombs in inventory solely via 
Ram Search

What is the expected output? What do you see instead?
The expected output is the address 0x23F835. But it is nowhere to be found, 
even if I make the simplest search (e.g. one "equal to specific value" search) 
and look the address by scrolling through the found addresses. I specify 1 
byte/unsigned when searching, which is correct for this particular value.

What version of the product are you using? On what operating system?
1.5.1. Windows XP SP3 (x86).

Please provide any additional information below.
I have tried enabling "include mis-aligned" as well. I also tried disabling 
"fast mode" and "preview mode" (not really sure what either does, but tried it 
anyway).

Original issue reported on code.google.com by TheNisto on 18 Sep 2013 at 4:06

[GoogleCodeExporter]

What makes you think that is the correct address?  If you are getting that from 
another emulator, the addresses will not match since you are using a memory 
domain.  The default for n64 is a subset of the open bus which is likely the 
address set used by another emulator (and if you are using something like Cheat 
Engine or MHS, it most definitely will not be the same)

Original comment by adeli...@tasvideos.org on 29 Sep 2013 at 1:55

[GoogleCodeExporter]

I am not getting it from another emulator. I made use of the built-in RAM hex 
editor. I was able to find the region in RAM where stuff like current amount of 
hearts/max hearts and other inventory stuff lies (I'm used to how this region 
looks and what values it usually holds). From there I just looked in the hex 
editor as the bomb value changed. And I wasn't running any other emulators -- 
or other game related software at all.

Have you personally tried watching this exact address to verify it (or better 
yet, tried tracking down the address by the RAM Search utility only)?

Original comment by TheNisto on 2 Oct 2013 at 10:08

[GoogleCodeExporter]

Looking into this

Original comment by adeli...@tasvideos.org on 7 Oct 2013 at 1:12

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I didn't have any problems finding this address in the latest SVN, which has a 
completely rewritten Ram Search.  I think this issue has been fixed, and will 
be reflected in the next release (and interim builds)

Original comment by adeli...@tasvideos.org on 7 Oct 2013 at 7:24

• Changed state: Fixed

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Nice, thanks!

Original comment by TheNisto on 7 Oct 2013 at 8:50