Ya, use this chart. If the game handles multiply key presses, which of course Geometry Wars has to, just make a square on the chart.

A fun example is when you press 1, 4, and right. Left is also pressed and you fly into that enemy who was chasing you. My original control scheme thankfully did not line up or else there wouldn't be much of a game. I really noticed this though because 4, XTON, and DEL, while rarely pressed at the same time, also press Zoom, which quits. So I just made Zoom a single key press only.

But for a while, this, with all the other problems I had with Mirage, made this game very confusingly unstable.

I was just talking about the little chart with all the buttons on it. If you make a box of buttons, it presses the fourth. The numbers don't even mean anything. Using that method, I have played mario without touching the arrow pad.

I was just talking about the little chart with all the buttons on it. If you make a box of buttons, it presses the fourth. The numbers don't even mean anything. Using that method, I have played mario without touching the arrow pad.

That's strange... But wait, how can you convince the hardware that you pressed, say, right, without touching any of up, left, down, or right? Wouldn't you be required to press at least one of those? I'm just curious.

Someone excited at BuckeyeDude's Pokémon port while on caffeine

I was bored as you can see

Haha awesome! Especially shortly after picking the box

And looks nice as always

Yeah even at slow speed it can still be hard, especially with complex physics. It's hard to calculate exactly where the character will land/jump. If Wabbitemu had quick save/load and advance frame by frame like most console emus with TAS support, it would be even easier

what I thought about is that as soon as Wabbit reaches a direct input or getkey type command, you could set it to stop completly until a key is pressed. Screenshooting would be temporarly halted, as well, and in sync with the speed at which emulation goes at.

As for 5, it was set this way since this is what I suggested before (it was 25% but I wanted slower mode). I guess you could maybe ask Buckeye to implement some other options like this.