Failure messages in emulator tests
Posted: Sat Dec 29, 2018 8:06 am
In this topic, Molive posted a test ROM titled "YourEmuSuxx.sfc". In reply, byuu wrote: "Your file naming removes all interest I would otherwise have in looking into this."
Now I'm worried. I wrote two Game Boy test ROMs to point out particular problems with Game Boy emulation in the Qt version of the emulator mGBA. First White tests that the first frame after turning on the LCD is drawn white, on which Pokémon Pinball and several other games depend. Telling LYs? tests that the joypad interrupt doesn't always occur on the same scanline, on which a game might depend to gather a quality seed for its RNG. They display the same message on failure:
The font choice is inspired by Internet meme culture, and the text is inspired by a screenshot under "RF-Modulator/Video Amplifier Characteristics" in "accurately reproducing the Video Output of a Commodore C64". The screenshot titled "c64_emusux0r.png" reads:
Now I'm worried. I wrote two Game Boy test ROMs to point out particular problems with Game Boy emulation in the Qt version of the emulator mGBA. First White tests that the first frame after turning on the LCD is drawn white, on which Pokémon Pinball and several other games depend. Telling LYs? tests that the joypad interrupt doesn't always occur on the same scanline, on which a game might depend to gather a quality seed for its RNG. They display the same message on failure:
The font choice is inspired by Internet meme culture, and the text is inspired by a screenshot under "RF-Modulator/Video Amplifier Characteristics" in "accurately reproducing the Video Output of a Commodore C64". The screenshot titled "c64_emusux0r.png" reads:
Emulation Still Sucks!I assume this is from a Commodore 64 demo by the demo group Crest. Can someone identify it? And how if at all do I need to change my own practices for failure messages?
PAL-Emulation my ass!
Thumbs up for hires!
a friendly reminder
from the Crest QA department