Menu
▾
▴
#604 RAM Watch file got corrupted
Hello, I was recording and when I started up my project again, my watch could not be opened. I shut down and restarted fceux and my watch was able to be opened but I was missing a dozen entries. I had saved a screenshot elsewhere so I can recreate the missing ones, but this is not a good thing...
Using fceux 2.2.1.
Need more details.
Send me the corrupted .wch file so I can examine it.
I attached one of the watches that got corrupted last yesterday. This watch had more than a single page worth of entries, but now almost all the useful entries are gone. What is left are some possibly useful values I was watching.
I am wondering if that "couldn't store debugging data" has anything to do with it. I have also been using the option to restore from where the emulator was closed last (forgot what that is called atm).
This bug might not exist anymore after you had fixed that "couldn't store debugging data" bug since they might be related. Just a thought.
I might have also been running a lua script at the time, but I do not see how that might have affected the watch.
No, this bug isn't related to storing debugging data (that one was due to archive filenames).
It seems, RAM Watch is a bit buggy, but no one noticed it since almost everyone uses Memory Watch instead.
Oh, was not aware of that. I guess I will take a look at Memory Watch. I was assuming that Ram Watch was the way to go since clicking the "Watch" button in Ram Search automatically adds in an entry to Ram Watch. Do I have to copy paste every interesting address to view it in there?
A bug?
Well, when I select Help -> MemWatch Commands I get a "This program cannot display the webpage".
Also, on the help page for Memory Watch, the "Ram Filter" link is just text, looks like it is not a link.
I'm not saying you should switch. Use whichever tool you like more. The Memory Watch was ported to FCEUX from FCEU-RR, so it's historically more popular among NES TASers. RAM Watch is ported from Gens alongside with RAM Search. I'll see if I can fix that strange bug you've found.
Fixed the link to help file in r2959.
Yes, it is just text with trolltastic markup, since no one seems to know how to (and why) use the RAM Filter, except his author. Here's link to his blog entry about it: http://www.the-interweb.com/serendipity/index.php?/archives/90-Release-of-FCEUXD-SP-1.07.html
If you happen to like the RAM Filter more than Cheats finder or RAM Search, you can write an article for FCEUX help and I'll add it.
That Ram Filter looks rather...obscure. It looks like the code is in monitor.c, copy of monitor,c, and monitor.h, but they are not referenced anywhere else but the makefile. The two monitor files are different as well. I would think it would need to be at least referenced in some sort of main class (not exactly up to par with C++ ATM). Also, when running the binary, the window title is "RAM Filter", but his screenshot says "Byte Filter" so I am not even sure the code version is right let alone how to use it. Maybe I will look at it later.
As it is I am pretty happy with Ram Search. My only gripe is that window re-sizing would be nice.
Wow, what a bug was it. Fixed in r2972.