Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

366 Excellent

About FifthPlayer

  • Rank

Recent Profile Visitors

5,804 profile views
  1. I think the issue is that the SIO2SD tries to load a patch to the OS at boot, to enable high-speed SIO operation. But the OS patch fails on the 400/800 ROM.
  2. I have a 130XE and it also has the vertical bar issue on modern TVs. I've tried a few scan converters but they don't help and it costs too much money to keep buying different models to try out. I only want one Atari in the house, and if I were to do it over again I would go with a 600XL or 800XL.
  3. There's a bigger issue here as to whether realism is a good thing for a game to strive for. I'm of the opinion that the game would be more fun if it reflected the knobs and dials that an epidemiologist would reasonably have on hand, but doing so runs the risk of turing the game into a dry, boring spreadsheet exercise. For me personally I'd like to see enough attention to reality for the simulation to be plausibly realistic, but still retain the elements that make it a game. Are nuclear weapons part of that? Regardless of what certain world leaders today might or might not do, one could argue in practical terms nuclear weapons aren't really a solution, but a cure that is literally worse than the disease. Still, I do admit that I find this game intriguing.
  4. Personally I'd like to see a more realistic simulation game that has you as an epidemiologist for a fictional WHO-like organization combatting the spread of a virus worldwide. Epidemic! doesn't look terribly realistic from the science point of view (nuclear weapons? shooting down meteors?). A realistic game could be a good teaching tool.
  5. Stuff like sprite flicker because of multiplexing hardware sprites, or soft-sprite character cell cutouts, I have no issue. But one game showed random electronic garbage on the screen when the player went from one screen to the next because the game didn't manage the display list properly. Another had stutters and hiccups in the background music because the author was lazy and disabled the vertical blank interrupt at certain times, which also disabled the music player. These issues were bugs plain and simple. Programming experts here gave the author simple ways to solve these fit-and-finish issues and he refused to do so. And programming glitches like those are still OK if it's a homebrew game you're giving away, but if you're putting it on a cartridge, claiming it's profressionally made, and asking $40 for it, for me that's a non-starter.
  6. My issue with this developer isn't so much their hard-core insistence on cartridge distribution, but that the titles themselves are generally glitchy and unpolished. Display garbage when transitioning between screens, sprites lingering outside screen borders, hiccups in the soundtrack, lackluster graphics on some of the titles. For the asking price you should be getting something that at least in presentation looks professional.
  7. I remember all the early IBM software releases for the then-shiny-new PC were in three-ring binders with punched-hole documentation. I don't think this was just an Atari thing.
  8. Generally the arcade ports were sub-par, but there were some that I enjoyed in their own right, partly because the hardware limitations put a new spin on the gameplay. Defender is one of those games, owing to how the smart-bomb works with the single-button joystick and the overall easier play because there's fewer enemies onscreen. And then there are the games that are pretty faithful to the arcade but have their own unique style on the 2600. Space Invaders, Asteroids, Missile Command, Ms. Pac-Man, and Frogger are a few examples.
  9. Hi, just a friendly reminder that these posts about hardware belong in the main Atari 8-bit forum, rather than the programming forum.
  10. I'm not a big fan of design by committee, and I think rensoup should make the presentation the way he wants. But I do think Jose's mockup looks much nicer than a stark white on black intro. @rensoup and @TIX have deviated from the original in some really brilliant ways that improve on the experience, but in this case the white-on-black design is neither true to the original nor an improvement. I think the argument about flicker is a red herring - it's the white-on-black design that's really lacking in feeling or inspiration. If @rensoup doesn't like the tiled border, I'm sure there's a compromise where the tiles are eliminated but the colorfulness is kept.
  11. I would try to contact the author of the MS blog article linked in the first post of the thread. He's a program manager for command-line tools. Though he's probably not the exact person you're looking for, chances are good he knows the person who is.
  12. Source code for the 5200 version of Galaxian is here.
  13. It was designed and built expressly for playing games. Enjoy it for that! For utility, maybe consider an A8 computer. The 800XL would be the perfect entry point into the A8 family for you.
  14. I have to agree. As much as I like that the 5200 exists, it's redundant if you have an A8 computer. There are one or two 5200 homebrews that haven't made their way to the 8-bit (Tempest comes to mind), but I can't think of any other reason to own one. Most 5200 enthusiasts seem focused on overcoming the controller issues, finding new ways to adapt alternative controllers to the machine.
  15. Without a keyboard and with a much more minimal OS than the 8-bit machines, a lot of non-game software would not be an easy port to the 5200.
  • Create New...