Ooh, we can do Twitter.
Phew, I don't want to jinx it, but now it looks like it's fully working on real hardware. Here's what was happening before: I had NOP'd the instruction to write a screen coordinate to a register, but what I neglected was the fact that a huge-ass pointer value was sitting in the register at the time it was supposed to be filled with that screen coordinate value. When the game engine looked for the screen coordinate later, it had to pull that huge pointer value. In other words:What FW thought he was saying:
Hey, game engine, I don't want you to write this thingie to the screen because it just ain't gonna fit in English. So I'm gonna tell you not to figure out the coordinate. Mm'kay?What FW was really saying, because he wasn't paying close attention to register values:
Hey, game engine, I want you to write that onscreen element about two miles to the left. Mm'kay?SSF's response:
Sure, I'll do that for you, buddy! Real hardware's response:
So I had to figure out another way of doing what I wanted, and now the hardware doesn't seem to have a hangup about it. Check out Konsolkongen's latest hardware test here!http://www.youtube.com/watch?v=EjHyy2QCbLY