Jump to content

MemberAtarian

Members
  • Content Count

    388
  • Joined

  • Last visited

Everything posted by MemberAtarian

  1. The biggest problem is that without the not so great multisprite kernel, there will be a lot of flicker with much buildings. The other problem is that just there is not enough variables, even with splitting them, so I will need to write directly into the memory with assembly. (The program is made with Batari Basic)
  2. 2019-03-06: Ouch, how should I beginn? I found a lot of bugs, most of them were bad goto bank commands or the on <var> goto went on wrong value. I redesigned the cursor placement, rewrote most of the AI and now 1/5 of the code is in assembly (I optimized the output asm bB made and inserted it into the bB code). I tested it on real hardware, somehow I couldn't fix all the issues with the colors (It never goes over 262 scanlines, but Stella shows it as red and the color goes missing) and my recorder couldn't handle it (the TV was not suffering that much, only a little black blinking). There is one mouse and one dpad (sega master system) recording, if you are creating your island, the dpad seems faster, but on the sea, it's easier to navigate the ships with the mouse. And yeah, I couldn't check the sensors as much as I wanted, so it's a bit over-sensitive, but an interesting experiment. 2019-02-11: New improvement. I know that most people play these games at home, alone, so I made the AI for the computer. It was really hard and has a lot of limitations, even with SARA Superchip, but it tries to do best by placing buildings and controlling ships (the most limited part is this, of course). What's left is searching for bugs, optimizing the code, testing the mouse and doing the ending screen. ---------------- After half years, I decided to get this project back with my improved programming skills, I made this night the title screen. I'm pretty sure that the song is familiar to you. I was a big WarCraft and StarCraft fan in my young ages and I really love the strategy game of Don Daglow for the Intellivision, so I decided to make a TBS for the Atari 2600, probably the very first strategy game for the system. At my first attempt, I had problems with the playerscore minikernel and even with the multisprite kernel, but I managed to learn how to use the kernel (even modding it) and of course, I modded the minikernel as well, so, here we go! The game will support Atari ST mouse control if you have one! 2018-12-29 As you can see, I made a little gameplay against myself. There is no AI yet and there is no ending screen, and there are some errors still, but the game is now in a playable state. Some new rules and elements are added, like: -Some buildings and the ships need a minimum number of people if you want to build them. -Fields of wheat disappear at the end of every number (it is harvested!) and converted to food, like the fish, if you are standing on it with a fishing boat. First you start with no people at all, but if you build house and have food, they will move there and work for you. If there are too many factories, the more people die, but you can give them better healthcare at the lab, etc. Ships are moving freely on the sea and battleships can attack other ships. If a battleship is attacking another battleship, there is a little chance that the attacking ship will be destroyed, due the better weaponry. The goal is building the giant cannon, develop weaponry and destroy every HQ of your enemy. I tested gameplay only with joystick, because the mouse control will need a lot of optimizing anyway. Distopia0.43_NTSC.bas.bin Distopia0.49_NTSC.bas.bin Distopia0.74_NTSC.bas.bin Distopia0.82_NTSC.bas.bin Distopia0.95_PAL60.bas.bin Distopia0.95_NTSC.bas.bin
  3. I don't think KK would like to use any co-processors, he's more interested in surpassing the limitations of the original hardware.
  4. Okay, guys, I'm just sitting here, in my workplace, and just sh*t my pants. Never imagined someone would try to make UT for the console! Keep up with the good work!
  5. Just found this topic and I can't wait to check it on my computer. And it fits in 4K, amazing.
  6. Not bad for a first game. What I was thinking is there any reason to not pressing the fire button all the time? I like the Indiana Jones kind-of feeling with the hat and the rock following, but I would put there more levels and make it a lot harder. Platforming games should be about your skills and reflexes, and most Atari fans are over 25, so, we just got worse in them. XD
  7. You know, the problem is the size of the randomizing scrip itself. You have to be sure that every single room is connected, and with that, you would have to remove the air-duct part. That takes a lot of space and would be really hard to randomize. Right Difficulty switch is used for musin on/of. I would put selection in the title instead, BB allows you that.
  8. Tested on real hardware. Apollyon_PAL50_0.41.bas.bin Apollyon_PAL60_0.41.bas.bin Apollyon_NTSC_0.41.bas.bin
  9. I'm really impressed that you are doing something for the very first home console. It's a shame that you cannot get a console in EU easily.
  10. Unfortunately, there is not even enough space for a reset command in the main loops (the stage and the air-duct). It would take 160-160 bytes and I have only 80-48. :/ I'm working hard on vectorizing every element to make clear elements for the visuals. And really thinking around how to make a strategy game for the VCS.
  11. How much sprite is left for all the other character then? This means you used 4 sprites as layers?
  12. Looks really cool, I like it! Detailed animation with NES graphics.
  13. Hmmm, so you want to reset during the gameplay? I only programmed it for the menu.
  14. Interesting, something must be wrong if you could save the game with humans around, I will have to check it. Also the popping out. 2 bytes of ROM space left in bank 1 0 bytes of ROM space left in bank 2 10 bytes of ROM space left in bank 3 3 bytes of ROM space left in bank 4 33 bytes of ROM space left in bank 5 19 bytes of ROM space left in bank 6 3 bytes of ROM space left in bank 7 88 bytes of ROM space left in bank 8 This is where I am right now. Every room is built up like: pfcolors (12 lines code of color) check if there should be something, like a soldier or dead soldier setting position of the enemies, and room variables to zero check to room type and gosub to the code segment of soldier or sciencetist behavior if they are in to room setting if there are directions you can go to, so if there are walls or doors if the playfield was not drawn, gosub to the code segment that contains the pf variations the room has, go for sprites (that's a very complicated segment, but I don't need to talk about it here) A room takes up at least 200 bytes even if it's empty. So the biggest free space is 88 bytes in a bank, that's circa 2 or 3 lines of more advanced code. How could I randomize? My other problem is that how could I randomize the layout of the map with checking if there are no dead ends and every room can be accessed? The air-duct is a pure fixed thing, there is a variable that is changed by pressing the directions and that shows the program which fixed image to draw on the screen and purely, that's all. The only thing I could do is removing colors of the rooms or making the two enemies act the same to gain free space. The only way to go with randomizing would be upgrading for 64K, but that size is too much for the Harmony cart for example.
  15. Sometimes I feel that even Atari players don't have any patience. The cannons can't turn, so can be destroyed from behind with one hit. The maze and the layout is always the same, so you have to memorize the map, like in the old days, you will know where the enemies are. The enemies die by one hit and for me, the scientist is harder, the soldier rushes into you and if you attack while running it's a win for sure. The sciencetist at least tries to avoid you. I have two problems I really can't handle. One is that I ran out of space. Really. The 32K ROM is full. I put the Queen at the end instead of Ripley because there was not enought space for a last fight. The same goes for the feeding, originally you would have to find cats and eat them, so you can evolve, but I had the reorganize the banks so any of them will go over 4K. The other is that if a character goes 1 pixel per drawscreen, it's the normal speed and 2 pixels are that hostile mess that you can see. Mayble I will slow down the soldier a little, but that is the only thing I can really do. Originally, I wanted to do 64 rooms and two air-ducts, but that also was too much for the ROM.
  16. That '82 game was my inspiration, I just thought WTF as I saw it.
  17. Done the things you requested. Now you have 6 blocks before it gets faster. 6 blocks is more then enough. I really don't like to change codes I had not worked with for a long time, I already finished Apollyon and constantly thinking about Distopia that will be a building centered TBS (turn based strategy) for the VCS. PlagueFinalNTSC 1.02.bas.bin PlagueFinalPAL50 1.02.bas.bin PlagueFinalPAL60 1.02.bas.bin
  18. You are just right. I'm working on the manuals right now. It will be shaped like the egg (ovomorph)
  19. Actually this is how the titlescreen looks. It's not an unreadable font, but as you shrink it to 96 and import it to the titlescreen maker, it gets ruined. That's why in Apollyon, there is no additional text on the titlescreen, just the logo, I think any gamer who played Atari could guess Fire or Reset is used for beginning the game. With the falling blocks, belive it or not, that is only "speed 2", so the "ball" adds to his y coordinate by drawning. The first three blocks are dropped by 1. In Apollyon, I felt the same problem as the Facehugger and the Chestbuster moves by 1, the adult Xenomorph seems very slow if it just goes by 1 as well, but 2 is too fast, if you know the right tactic like me, you can kill everyone without dying.
  20. Already changed it in the code, you are right. Plan for the visuals:
×
×
  • Create New...