Jump to content

adamantyr

+AtariAge Subscriber
  • Posts

    1,891
  • Joined

  • Last visited

Everything posted by adamantyr

  1. Nice! I am packing up collectors editions to mail right now in fact
  2. You can find notes on how to update your saved game on the version notes page: http://quixotic.adamantyr.com/roa-version-notes.htm In this case, you just replace a couple files in your current game folder and you don't need to do anything else. Or, if you just extract the new version into a new folder, just copy the SAV, SG0, SG1, SG2, and SG3 files over to the Data folder and you can resume play with your current save.
  3. Did an interview with the Lost Sectors!
  4. Also successfully reprogrammed one with the latest build! It helps when you realize you need to pull the sticker off the EPROM...
  5. Carts came and they work... you rock Jim! Sadly I will likely have to erase and reprogram as we will be a few builds ahead...
  6. Well if you can use a disk manager program and view the file contents on the disk just fine, it may be a SAMS issue indeed. The loader program loads the contents of the PRG file into memory pages swapping them out in the upper 24K block. When finished it sets to the start module and launches. If for some reason your SAMS card failed to do page swaps it would just overwrite the same memory over and over and fail to start.
  7. How are you getting files onto the tipi, are you using the wifi option? I'm confused why TI99Dir was needed at all. A freeze in Loading suggests its either having issues accessing the PRG file or the SAMS card isn't right. You have a standard 1MB card?
  8. Also, a review of the game in German! https://cgboard.raysworld.ch/showthread.php?tid=26912
  9. Are you able to catalog the drive, see the files there? Matthew Splett may be able to assist further. I know the game works with TiPi, it's even the optimal setup for it, so this sounds like more a TiPi configuration issue to solve.
  10. The Librum Asmusr only has combat spells. So there is no cast option in travel mode. Ammunition should not have an examine option, this will be fixed in an upcoming build. For game crashes, I need specific examples. Two testers played through the game with no significant crashes. What enemies, how many, at what point did the game crash?
  11. Ah there it is. Yeah, every turn it was re-asserting a player was disabled, and wiping out the unit value present on the map. That created a situation where attempting to attack the monster made you just move over them instead. I will have a fix in the next build shortly.
  12. My apologies, Astharot, but I am having trouble understanding what the problem is and what configuration you are using.
  13. Okay good, that gives me something to work with on a repro. One question, was a monster on top of you when the character was revived, and he appeared in a different square?
  14. Ah, I had a similar report elsewhere... did any of your characters get disabled and healed during battle? I need to probably start trying to repro that one... *sigh* It seems to be an edge case, it doesn't happen that frequently.
  15. You can find details here on setting up Classic99 for a custom ROM: http://quixotic.adamantyr.com/roa-running.htm Also, you can load the game via other cartridges. You'll need to extract LOAD, ROA, and RPG from the ROA-GAME.dsk file under Disks using TI99Dir, as I didn't provide those in the Data directory, and place them in the same folder.
  16. I tested it, it looks like it's working fine. There was another app-related issue that if you forget to change the disk configuration it automatically thinks all the files are on DSK1. I've updated the SAV image on the disk images to a more reasonable DSK2 and DSK3 for world disks, respectively, since anyone using the disk images is probably going to be doing something with multiple drives.
  17. Tested and it works! One other thing, Vorticon. You'll need to do disk configuration prior to starting a new game. The default SAV file is set to expect everything on DSK1.
  18. LOAD and SAVE are constrained to the size of VDP, and only work on a single file in one swoop.
  19. It's not that unusual. And it's necessary because the data is not structured in a record format, it is highly variable in size so it tracks by sector location, sector offset, and # of sectors. It is in fact a file copy of sorts; at the start of a new game it has to make pristine copies of the original mob files back over top the saved game files for use. Saving your game later has to output the entire file as it loads one whole file into active SAMS for easier access and also not forcing you to save your game every time you change maps, which would be awkward.
  20. Character data is stored in a PROGRAM file, which is saved under a different DSR program. So that's being preserved. What is not being preserved is mob data which is stored in SG0-SG3 files.
  21. My guess is that it's not. You're probably playing on the same files as your prior game.
  22. Yep, operation not supported on this disk type.
  23. You may want to bring up the debugger then and see what it's saying as it attempts to create an adventure. It does a disk file by sector operation and both loads in all the contents from MB0 to MB3, then writes them to SG0 to SG3, respectively.
  24. Are you per chance using disk images? I think Classic99 still doesn't support disk images for write operations.
  25. Yeah, I know right where in code it was, I was setting the external video bit. Interesting! I guess I never tried creating a new party on hardware or I'd have noticed. Fortunately it's not a game-breaker. I've got one other bug which isn't a game-breaker fixed for the next one, I'm just waiting for feedback/input before a new release. Adam
×
×
  • Create New...