VVVVVV for MSX

ohoho, I chose screen 1 cause colortable is only 32 bytes, and I can use multiple patterntables. I didn't add a sprite flickering routine, I need the sprite overflow bit for mid-screen pattern table split later.

@hap

Is it running on screen1?! Really impressive! With it's "8 patterns colorbleed" limitation, you got a hell of a good result on this game!

I did some tests to check for bugs, and here are the results. I hope they help you:

1) Turbo test: passed!
2) SubSlot handling: passed Acid1Test!
3) MSX coding guidelines compliance: Failed Acid2Test, uses some hardcoded I/O access.
4) BIOS interface test: Passed running both on C-BIOS and on the Sharp Hotbit!

3) fails: I like to write to I/O ports yes, such as out ($98),a for vdp. IMO using BIOS-calls is unneccesary, and I'd have to learn a new 'API' when I'm already expert on direct hardware access.

Err, doesn't the Acid2 test merely require that you check the system variables to find out which I/O ports to use for the odd MSX computer that uses different I/O ports?

also, which MSX computer(s) is the odd MSX computer that uses different I/O ports? I can imagine that the NEOS MSX1-to-MSX2 kit uses different ports, but I've never seen one.