Jump to content

ultima

Members
  • Content Count

    235
  • Joined

  • Last visited

Posts posted by ultima


  1. Sometimes you eat the beam and, well, sometimes the beam, it eats you!

     

     

    (personally, I say if it looks good on real hardware then that's what's important. That's me, though. Some people don't ever even use real stuff anymore.)

    Lol, true dude very true. I do want to play it on real hardware in the future.

    I did free up some processes this afternoon still trying to organize all the code to figure out if there are other areas that have become to complex or useless. Then the game still has lots of fine tuning. It seems like a never ending task to build a game engine just right. I still would like to see about adding more music and sound effects too.


  2. Nice work I added the title screen in and fixed a couple errors the mod to the breakable walls was missing some placement arguments. I also fixed the starting screen issue of firing at the dead tree to enter the dungeon and also fixed the boss.

    Ill post the .bas later when i grab my pc.

    • Like 1

  3. Thanks SI02 & GroovyBee for the help. The version I posted seems to be useless for real hardware so I will return to an earlier build with the cycle savings (at least it has a more stable picture.)


  4.  

    The best optimisations come from algorithmic changes. Posting your "slow" code and asking for optimisation tips or better algorithms than the ones you are currently using, would be a better approach in my opinion.

    I managed to cut around 6 cycles removing some of the if..then statements with on..goto. It seems to blast out as high as 10 cycles over during certain enemy movement phases. BTW the enemy program under the headers _MaelstromAI & _MaelstromAI_II were modified from Random Terrain's collision prevention code to keep enemies off the playfield (as long as I establish pre-configured starting locations which at this time are only partially implemented).


  5. It compiled and ran for me

    That's good! I'm not crazy, but now I've got to track down the problem. I have no idea why it's not compiling this but it did all 8 banks on shadow of the colossus. Maybe windows 8.1 was sabotaged by micro$oft. But I must be missing a file or something. I'll try another install and hope for the best.

     

    **tried reinstalling again, no go. I guess if I needed a push to try learning pure asm coding I seem to have no other options.


  6. Late post but did manage to kill the 16th colossus Malus. Unfortunately till my bB gets up and running again I can't update the collision detection so it's still the "rub the wall and get sucked in" style. Also the score graphics are from sword of iffrit.

    • Like 1

  7. Managed to bring in some enemy A.I.(any good advise here?), and you have to defeat the boss to get to the next room with the triangle. also added a flash of color to the enemies when you get a hit in.

     

    Still can't track down why the player direction graphic is getting wonky. Here's the source if anyone wants a good laugh.

     


  8. Ok, After ripping my hair out finally solved a bug (taking damage when passing through a door) also added another key, another door and added two false walls that can be shot open, also up and down directions for the character.

     

     

    I think it's close to functional but for some reason the player direction timing feels off so will focus on that in next update.

    • Like 1

  9. I worked on this a little more. Fixed one door added another that uses a different colored key. Started some work on drawing 4 directions to display character at facing direction that I might use in making holes in playfields using variations on pfline and pfhline. So it might offer door puzzles and secret doors found only by searching the playfields for weak sections.

    Once that gets worked out I want to try some ideas for enemy AI and finally remixing the game with the story mode included

    • Like 2

  10. I wanted to ask anyone who has some ideas how we can better organize our programs. It seems that lots of things we regularly do like drawing players and playfields...missiles, but is there a better order for when in our main loop we should we be checking controller input? when to update music?..ect

     

    It seems like the larger my programs get, the less I have a handle on what the appropriate way to organize it should be. Is there any pointers or helpful

    threads that have discussed this topic? thanks

×
×
  • Create New...