@scrimpeh: Sure it's possible for input to have an impact when the screen is off, especially if IRQ's are on. The correct way to time runs is with cycle count. Gambatte also requires this, as TIKevin83 pointed out in a recent submission (just to a lesser extent.)
The pallets are not displayed correctly for Felix the Cat on GBC mode.
I got IR comm working now too, in 3x version as well.
This one seemed to give Shonumi some trouble so I used it as a test case to see how robust my implementation is. I didn't run into any trouble, but the games are changing speed a lot during the IR comm process, which is pretty strange. I didn't look into why they do this or too heavily into the IR algorithm since it seems to work just fine. One thing I did notice is that you can't have both players press 'A' near the same time or it fails.
http://tasvideos.org/userfiles/info/58555860013787500
Finally, this long exercise is at an end and I have a complete re-sync of the pokemon crystal run in GBHawk.
This has been an excruciating but also very rewarding task, as I learned a great deal about the GBC in the process and fixed many bugs both small and large.
With both the crystal run and yellow run working, the Gen 2 catch em all should be doable with realistic accuracy (although linking is not tested for accuracy itself.)
Now we should finally be able to start pushing forward with other games. I already pass many more sprite timing tests then Gambatte does, and with these two runs as bench marks it strongly constrains what in the code can be changed in the future.
With both the crystal run and yellow run working, the Gen 2 catch em all should be doable with realistic accuracy (although linking is not tested for accuracy itself.)
Looks like the site parser identifies GBCHawk movies as GB platform, probably because the header doesn't include the IsCGBMode flag that Gambatte movies have. So we either need to implement this flag for GBCHawk or add more logic into the site code.
