nesdev.org

It's not a fix, it's a kludge, and one that shouldn't be committed as a fix. The relevant SRAM is 8KBytes; changing the .xml to force 16KB or 32KB SRAM/WRAM just allows for one, somehow, to work around the real issue. I'm really growing sick and tired of every single Nestopia-related thread/issue h...

How did you fix this with 32?

hehe Quietust, you match your facepic very well!

I filed a ticket for nestopia to add a menu option, im hoping it can be implemented like rainwarrior's way! Great work! I think this is the hotspot if im not mistaken though, correct: In NstCpu.cpp void Cpu::Ram::Reset(const CpuModel model) { std::memset( mem, 0x00, sizeof(mem) ); } I'm currently me...

Maybe I should think about adding such an option to FCEUX. I have added an option to FCEUX now: https://sourceforge.net/p/fceultra/code/3275/ 1. default (the 00 00 00 00 FF FF FF FF pattern it's been using for years) 2. FF 3. 00 4. random That's probably enough. I don't think there's much reason to...

I tested out river city ransom and it indeed does rely on startup ram to "randomize" enemies. On nestopia (when the ram was 0xFF) you will ALWAYS get the frat boys on nestopia (with the new changed 0x00) now it will ALWAYS will be the generic dudes. So definitely adding an option like the ...

In going for authenticity, it would be great to have some sort of generator that cycles between a few values on startup, doesn't have to be millions and millions, but a few 0xwhatever numbers we know. We could call it a startup ram generator. Indeed some games used this to "randomize" enem...

Sorry for the double post, I went back and decided to look at some reading about the 0xFF and 0x00 and came across this post: "The pirate dump came from a multi-cart, which apparently allowed the user to set the world number to start on before beginning the game. The ROM code was hacked to prev...

Thanks for posting that up, that was an interesting read!

interestingly enough I wonder what other little oddities this may fix with nestopia loading games, (as I think ive already seen it fix something else) and puNES if it gets implemented or was this a weird quirky case for the f-1 proto?

I've owned two front-loading NES (NTSC U/C) consoles. One had $00 (dark gray) in CGRAM, visible when no cartridge was inserted or when the CPU bus wasn't making a good connection. The second had $28 (yellow). So, why does nestopia and puNES have ff? Does this affect games in any kind of way? SO bas...

Thanks for putting that up koitsu!

So in terms of an actual nes, there are really no correct start up values right? It can differ and be random from one nes to another, correct?

so zepper, your emu should also have the same issue as puNES and nestopia then if you are following those start up values with the f-1 proto right?

Yes, Nestopia and puNES both initialize RAM to a very specific set of values: wiki These were determined from some particular person's particular NES once, and were kind of stupidly propagated as some "authentic startup values for RAM" (as if such a thing exists). Those two emulators impl...

Just for fun, tested with the emus I had: FCEUX/Nintendulator/MyNes/Mesen all display the title screen first. Nestopia UE/puNES both skip the title screen and start a race immediately. Since both Nestopia & puNES have no debugger, figuring out why their behavior is different might be a bit of a...

Sorry to dig this back up, but a prototype of F-1 race was released by Skrybe over at lost levels yesterday. The prototype seems to jump right into the race on nestopia. With this being a proto, these issues are seemingly related correct? He states it works fine in fce but not nestopia, so im wonder...