Search found 5 matches

by Screwtape
Sun Nov 03, 2019 11:52 pm
Forum: SNESdev
Topic: Telling LYs? (Input timing test ROM)
Replies: 2
Views: 3962

Re: Telling LYs? (Input timing test ROM)

The test passes for me in bsnes v112.7, as long as "run ahead" mode is disabled. With "run ahead" enabled, the game immediately leaps from the title screen to a screen that looks like this: https://i.imgur.com/ruuXBZl.png ...and although pressing buttons causes the arrow to move, no amount of pressi...
by Screwtape
Mon Aug 26, 2019 9:03 pm
Forum: SNESdev
Topic: How the Memory Map works exactly
Replies: 8
Views: 5457

Re: How the Memory Map works exactly

When data in ROM shows up at a particular place in the SNES memory map, that's because the physical cartridge is wired that way. The HiROM area starts at 0xC00000, or in binary, 0b110000000000000000000000. Some piece of logic on the cartridge (not a CPU that executes instructions, probably just some...
by Screwtape
Sun Aug 18, 2019 5:11 am
Forum: SNESdev
Topic: Target width for widescreen patches?
Replies: 37
Views: 18447

Re: Target width for widescreen patches?

The historically accurate way to render SNES output is with a 16-scanline overscan area (i.e. slightly letter-boxed) and aspect-corrected. While this was perfectly natural on the CRTs of the time, it doesn't play quite as well with modern displays for a few reasons: - Modern displays are 16:9 and th...
by Screwtape
Tue Jul 16, 2019 6:08 am
Forum: SNESdev
Topic: Mesen-S - SNES Emulator
Replies: 350
Views: 151384

Re: Mesen-S - SNES Emulator

If we can convince No-Intro to adopt this format now that apparently three emulators and counting do, I'll remove my HLE code again. I signed up for the No-Intro forums to politely argue for and request this. The SNES datfile now has separate "combined" and "split" variants, so it's technically pos...
by Screwtape
Wed Jul 10, 2019 11:53 pm
Forum: SNESdev
Topic: Mesen-S - SNES Emulator
Replies: 350
Views: 151384

Re: Mesen-S - SNES Emulator

I'm hoping to eventually get around to gathering them up either on a wiki page or github repo and defining their expected results (on different consoles, when it matters). At least that way there would be a central place to get information on the tests that exist, rather than finding them on random...