dmg-acid2 VS mooneye-test-suite

My Game Boy emulator has almost passed dmg-acid2, except that it has the "Eye displayed instead of right chin" failure mode. The README says that this signals an issue with the "window internal line counter," but I don't see where that's documented. Can someone enlighten me?

I tested it with the classic dmg-acid2 test rom and another rom called sprite_priority.gb which is part of the Mooneye Test Suite.

For everything beyond opcodes, and especially graphics, the pandocs go over almost everything you need. For testing graphics, you can use the dmg-acid2 test roms which have tests for most of the common graphics errors.

Adequate PPU emulation (passes dmg-acid2 test). This emulator uses Pixel FIFO, as opposed to common scanline renderer.

acid-dmg, this is a really nice PPU test, you can try to complete it step by step.

The thing about the Game Boy (or most consoles, really, but especially the Game Boy since it uses a custom CPU) is that we don't know all the details. People have had to reverse engineer it to figure stuff out. /u/gekkio is one of the people doing that work, and his technical reference and test suite are the (ongoing) results of that.

I tested it with the classic dmg-acid2 test rom and another rom called sprite_priority.gb which is part of the Mooneye Test Suite.

I am working on my Game Boy emulator and I'm trying to get the timer to work with mooneyes acceptance tests. Take this one as an example.

The mooneye-gb test suite has very specific tests for the timer (maybe too precise, they require emulating every little detail — but if you want that kind of accuracy, way to go)