Jump to content

Ryan Witmer

+AtariAge Subscriber
  • Content Count

  • Joined

  • Last visited

Community Reputation

885 Excellent

About Ryan Witmer

  • Rank
  • Birthday 03/08/1979

Profile Information

  • Custom Status
    Fleeing all W'rkncacnter
  • Gender
  • Location
    Burien, WA
  • Interests
    Programming, board games, martial arts, baseball, cricket
  • Currently Playing
    Shining Force
  • Playing Next
    Space Harrier II

Recent Profile Visitors

16,006 profile views
  1. Every morning I wake up hoping that the Pope has appointed a new Holy Roman Emperor.  Every morning I'm disappointed.

  2. RealSports Curling has a CPU vs. CPU mode. Super Pro Football on the Intellivision does too. I don't remember if the other Super Pro sports games do. Just remembered, Super Pro Wrestling also has this mode.
  3. I've hit a bit of a creative block on my PC game so I decided to get some stuff done on this today. I think this picture sums it up pretty well: All three control methods are now at least partially implemented. Trigger mode is basically done, needs a couple of tweaks but no big deal. In this mode, the bottom fire button throws your disc in the last direction you moved. Press it again will recall a disc in flight. The top button toggles block/crouch, functioning exactly like the 5 key in keypad mode. Twin-stick mode is not quite done, but pretty close. Stick 2 throws your disc, pressing roughly in the opposite direction of your flying disc will recall it, like you're pulling it back. I plan to make all of the keys on the second stick toggle block/crouch mode, including the start/pause/reset row. I haven't don't this part yet, since I need to work on the code to allow reading from multiple keypads. Keypad input is a major pain on this system. I know I've said that before, but it needs repeating. Twin-stick isn't all that effective, and I was pretty sure it wasn't going to be. Unlike Robotron or Space Dungeon, you don't have continuous fire in this game so it's kind of hard to find your direction on the stick. One interesting thing about the trigger and twin-stick modes is that they allow the player to throw a disc in 16 directions, just like the enemies do. The different control modes aren't actually selectable yet, I've been hard-coding them in for testing. I have a hare-brained scheme surrounding this that ties into the game's surprise feature. I'm pretty confident I can show the beginning of that feature this weekend.
  4. Ryan Witmer


    Screenshots and media for Intellidiscs for the Atari 5200.
  5. I always release my source code when the game is finished, and there's a guy who has ported all my 5200 games over to the computers. He'll probably do this one too. The fire button mode is also going to be supported on the 5200, so code for that will already exist. Should make the conversion easier. The Intellivision game had 16 directional movement and the game is really built for that. Full 360 degree movement on the 5200 sticks is actually really hard and awkward to do because the sticks are just way too inconsistent. Each controller has a calibration that can get out of whack, put the console itself has a calibration, and different controllers have different ranges and it's just a huge mess. The only real solution is to break it into chunks, usually 4 or 8 depending on the nature of the game, and provide enough buffer space in each direction to compensate for how inaccurate the controllers are. Real 360 degree movement also requires a lot of math that the 5200 is just not very good at. I have a couple of reasons to keep the joystick code as fast and light as I can, one reason is the twin-stick mode where I need to read two sticks at once. The other is still a secret, but I should be showing it soon, maybe even this coming weekend.
  6. The colors on the title are continuously cycling, every shot looks different depending on where I caught the animation. Like this one! I kept the old sprite data around for the Intellivision-style recognizer. I'm calling it the "Identifier" just to be safe about any Disney trademark crap. Since I have plenty of space left, I decided to put both recognizers in the game and let the player choose which one they prefer. Intellivision purists can have the one they're used to and the rest of us can have the cool new one. Don't say I never did anything for you people!
  7. So here's some of the stuff I did yesterday for a live audience on twitch: All the little guys on the screen are animated, just running in place. This was really fun to do, and now I'm working on making the menu for choosing your control mode. Once I have that menu, I can start working on twin-stick and fire button modes. Good stuff.
  8. I did a little bit of work on this today during some creative downtime on my PC game project (meaning I need to think of something and I haven't done it yet). I went ahead and a added a animated color cycle to the title logo. This is the lower resolution version of the title image. The color pattern is animated and it looks pretty cool in motion, or at least I think it does. I still don't like the logo itself and I'll probably make some edits to it.
  9. A couple hours after I posted that image I discovered that I couldn't really use the high-res graphics mode. The coloring options in that mode are extremely weird and limited. If you aren't happy with black and white, it's a pretty awful mode. I redid it in a lower resolution mode, and it looks OK, or at least bad for all the same reasons. I started playing with some interrupt-based shading but didn't get too far. I might mess with it a little more tonight if I feel up to it.
  10. Here's something kind of cool I did tonight. I started putting together the title screen. I'm not sure about the font I used. It's actually the "official" Tron font from Disney. I had to modify that D a little bit since it looked terrible before, just the the C but flipped around. I plan to add some color with creative screen interrupts. What's cool about this is that the title is using the super-high-resolution monochrome mode. I've never used this mode before, so it was kind of fun to mess around with it.
  11. Yesterday I finally rewrote the aiming code in front of a live audience on twitch. It's a LOT better now, might still need some adjustments but my overall approach is working really well. This is exciting because it was the last real technical hurdle in this project. From here on out, it's bug fixes and details. I also implemented 16 directional movement. It seems to be working pretty well, but you can never really tell with those 5200 joysticks. I had to do this work on my real 5200 since testing it on an emulator is basically impossible, and I spent a lot of time just playing the game, amazed that it's pretty much a real game at this point. I just got done making a release checklist. I do this whenever I feel the end of a project getting close. I have just about everything that needs to be done listed and now it's time to just start banging those things out. I'm not making this list public because there are some things on there I haven't announced yet and I love surprises. I might knock out a few of the smaller things on the list later today. It's also possible I'll start doing a few things during the week. I really want to get this thing done and move on to the next project. One thing that's refreshing is that I have plenty of ROM space left. At this point in Magical Fairy Force's development I was running out and desperately trying to reclaim space wherever I could. 32KB should be enough for anybody, but sometimes it isn't.
  12. SNK, you aren't going to make me buy a console for KOF XV, are you?  Are you?

  13. This was a weekend with two major bug fixes: First, I think I finally got that disc erasure bug sorted out. I know I've thought that before, but this time is different, I promise! I also fixed some of the broken logic around new enemies appearing. By incredible coincidence, the first bug happened to be related to the second, which was interesting I guess. I also got the pause button working, so hurray for that. The next big thing is to finally fix the aiming code. I plan to spend some time thinking about this over the course of the week and hopefully I can knock it out next weekend along with a bunch of smaller stuff. Still moving forward, just a bit slowly right now.
  14. Well, I wasn't able to get as much done this weekend as I wanted to, but I'm going to put this build out anyway. This is "Playable preview 1" and it even says that 256 bytes from the end of the file! This version is a completely playable game, but with no sound, simple controls, and lots of bugs. A few notes: Keypad-based disc throwing only Only 8 directional movement, 16 will come later A lot of things still need adjustment, various timings and speeds are wrong If it seems like the enemy's aim is terrible, it is! If it seems like the recognizer probe can't find you very well, it can't! If it seems like the 1,000,000 point guards are drunk, they are! All three of these things use the same aiming routine and that logic is pretty much broken right now. There is a known bug where the enemy discs will not erase properly and you'll see little squares in weird places. I've been trying to track this down for months with no success. I did see some stuff this weekend that might finally lead me to the cause for this. The recognizer probe doesn't yet go into "high-speed" mode when you stand above the recognizer. There is another known bug where you will sometimes get credited for finishing a wave before reinforcements, but then a new enemy will show up during the final enemy's death animation. I'm working on a fix for this. The recognizer door repairs are way too slow. The game just locks when you die. If you die to enemy discs, the reset button should work. If you touch the recognizer like a fool or die to the guards, the game is just locked. Do a hard reset. I'm probably forgetting some stuff. I'm also posting a build with the Intellivision style solid recognizer. This build has an ID string that says "Playable preview 1, old recognizer" So here are the builds. I may start posting new builds every week, not really sure. intellidiscs_or.bin is the "old recognizer" build. intellidiscs.bin intellidiscs_or.bin
  15. The first character trailer is here!



  • Create New...