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.

It is now on ticalc.org. Along with another game I made for the last week of school.

Geometry Wars

For the screen shot, I played until that point on a real calc, then sent the save game appVar to WabbitEmu and played it in 1/4 speed. It is much harder on the computer because WabbitEmu successfully incorporates the key board glitch where when specific 3 keys are pressed, a fourth is pressed also. Which means only 4 moving directions and 8 shooting directions.

There, I'm feeling generous. Arrows.

I actually have some far fetched goal of by the time I'm a senior having F-Zero Game Cube ported to the calculator and having it multi-player. But there is a lot I would have to learn before making that.

It's so weird to see speed TAS's of my own games lol. On missile I recently watched my friend get a 105 on a real calc. Somehow he uses two hands.

But for the 83+ issue. I have only seen 1 83+ at my school so the way I looked at it is, why limit myself when no one will really notice. I use the crystal timers just because I can, they don't have t,o be used. If you really wanted to, I'm sure you could use interrupts to almost perfectly emulate them, or just use halts or a loop to slow it down suffering from overspeed and then lag. If you run the games on a calculator without the timers, it will just display one frame and then stop as it is waiting for something that will never happen.

But as far as fast mode goes, I think all my games need it except for maybe missile. Orbit used to run without it and lag starts appearing around 25 and the game is half speed when it maxes at 68. Tetris, I don't think there is anyway around it. To have a fast functioning gray scale game I believe takes fast mode. True, desolate was done without it, but if a tetris game had the control lag of desolate it would just be unplayable. Missile is the one game I think you could get away with. I did not put any effort into optimizing once I had the scaling system in place, so that could be fixed. You could also just go with a slower frame rate and make the in-game speed faster.

Orbit, I believe is optimized the best it can be. Tetris is not, but I don't think with grayscale it was any possiblity. (It actually lags when you clear more than 1 line.) But if some one were to optimize, missile would be the one that has possibility.


And since you guys like my games so much, I'll post my second game on here although I never actually finished it. This was basically my learning asm game and was about 6 months in the making. I recently figured out how to fix the bug where it would eat the program after it. This was caused by deleting an appVar that was earlier in the VAT than it. So the VAT moves, but Mirage stored the VAT as static. You can see the change in my source right before it quits. When looking at the source, at about September last year, I switched from all caps to all lowercase.

I would really like to see some one TAS this one, it uses 17 buttons for controlling the game. It is hard to get used to, but there is a lot of depth to this game. Enjoy.


Here's my pathetic screen shot. I just went to a wall since moving on a keyboard is mostly impossible.

Ok that makes sense. I didn't realize that it needed that much memory. I noticed there should be like 3KB of space after the video buffer, but I guess that's not nearly enough.

What is going on that it needs that much memory though?

I'm not sure if this has been said before because all 40 pages is a bit much to read. But would the new 84+'s have any chance of running the ROMs if the emulator just said bye bye calculator memory and deleted every thing?

With 49KB of RAM, is that enough memory to run these ROMs? To make it prettier you could archive it all. But I would much rather have a RAM clear than have nothing.