Was having a hard time finding this ROM, as the old links are dead. There was another link to the file on NESDev but the file is missing. After a bunch of digging (and a bunch more dead links) I found this "GrayBox.nes" in a torrent called "Unlicensed games", so I'm posting it he...

On the Famicomworld forum I found a thread with a list of games that might not listen to the expansion port, which does contain many Japanese games too:
https://www.famicomworld.com/forum/index.php?msg=167005

(Sorry for the bump, but I thought it might be useful reference.)

I don't think NESticle has any implementation of the sprite overflow flag: source link So a spinlock on that will hang, I suppose. For reasons sort of related, when waiting for sprite 0 hit I tend to use BIT with a mask including the vblank bit as a backup in case sprite 0 is never hit for reasons o...

Explicitly measuring both scanline length and frame length, as in the "overclock" ROM that became the "CPU clock speed" activity of 240p Test Suite, may be needed if you want to fully support overclocked CPUs. Incidentally, that test (or the earlier oc-r1a version ) appear to ju...

I agree with most of your points but I must say that I don't know of many emulators, even older and inaccurate ones, that would fail region detection. I feel like only the really early NES emulators on DOS would be relevant here. Well, for my own releases I haven't had any reports of a problem with...

I agree that adding more options is not always beneficial, but this is kind of a platitude? Yes of course, every option added is something you should think critcally about. I realize we're already very hypothetical here, but I don't really want to go to this extreme. The question was whether this op...

Yeah, to be honest I see no reason why they should make it an option. Timing is only going to be off enough to mess up automatic detection in extreme edge cases like super inaccurate emulators (that no one are using in 2023 for normal gaming circumstances), and in those cases you can't really do mu...

In my experience with releases, tepples' auto-detection routine has been appropriate in every case I've heard about. If you have an options menu, I think allowing the user to choose AUTO / NTSC / PAL / DENDY is nice, and could theoretically account for a weird clone or emulator, but I haven't yet ha...

I don't really understand the question. Are you asking me to justify variable initializers in C? This is a very normal and standard thing in C code. Variables need starting values, and an initializer is the most appropriate place for it. The cc65 DATA segment is to be able to do the initialization i...

I've added a few options: -Record system HUD (record avi popup): allows recording stuff like the fps counter, game timer, on-screen messages, etc. -Record input HUD (record avi popup): allows recording the input state overlay -Use fixed output resolution (in SNES->Video and PC Engine->Video): When ...

Technically the SNES only ever outputs 224 or 239 lines, it's the receiver's job to properly align them... :) Not really? The alignment is under the SNES' control by how many lines since vsync. It's not arbitrary, and it must be aligned the same way as other television signals. Consumer TVs rarely ...

Always rendering at 2x is kind of problematic when it comes to filters, since applying xBRZ on top of an already scaled frame will cause the filter to not have the same effect at all, etc. This is why the filters look like they have nearly no effect for PC Engine at the moment - the rendering resol...

Technically the SNES only ever outputs 224 or 239 lines, it's the receiver's job to properly align them... :) Not really? The alignment is under the SNES' control by how many lines since vsync. It's not arbitrary, and it must be aligned the same way as other television signals. Consumer TVs rarely ...

For the SNES switching resolution during avi recording issue, I'd have to see, but I don't think AVIs can support the resolution changing during the video itself, so it's not a super simple fix. Although, I think if you use the NTSC filter, the output resolution should be identical (e.g always 2x s...

The window size for quick integer scaling Alt+2 appears to be off by 1? In this screenshot I just pressed Alt+2 and the actual visible resolution is 511 pixels wide instead of 512. You can see the missing column of pixels clearly in the middle of the screen, squishing Ayla's face. Alt+3 and Alt+4 al...