Jump to content

averagetsbplayer

Members
  • Posts

    1,394
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by averagetsbplayer

  1. I updated this tool to support the FinalBurn Neo (v0.2.97.44) emulator with the original 28-team ROM
  2. Mostly for my own future reference, I think has one not-that-important gap: If a game goes to OT tied at 0-0, we can't distinguish if it went to OT 0-0 or the game's only score happened in the 1st quarter. Edit: I think I was wrong. My main issue was parsing an original game without the hack: - It's tough to tell the difference between a game that was 0-0 going into OT from a game that had it's only score in the first quarter.
  3. There's a bit of magic in here that I'm hoping someone can help me understand. I get in concept how x1C054 points to x1C3C9. - I don't really understand how the CC10 gets us to x1CC20 / $AC10, especially when the pattern is different for the B074 -> x1D084/ $B074. -------------------- Problem #2 (bruddog let me know I was misunderstanding this issue a it). - x1C010 has 56 bytes that represent 28 pointers to "Designs" - Designs aren't just a sequence of pointer "pairs" - These appear to be some instructions (including x04->x1C018->x1C240) - I noticed some that have a value (or two) between x80-x9F that appear to be some modifier before the "Feature" instructions that do the TILE-ROW-COLUMN 3-byte pattern. - So, I for x04->x1C018->x1C240, there's some x82 modifier that is then followed by the xCA x7A with 7-tile instructions starting at x1CA8A - Anyone know if I'm on the right track with this modifier concept? Previous Background I think understanding that will better help me understand Face x04 that looks like it starts at x1C018. - The values/pointer at x1C018 are x30 xA2 which would take us to the Design at x1C240, I believe - though I'm not certain. - The first pair at x1C240 is x82 xCA, and I was going to guess that took us to x1A2DA. But that looks like it has 246 bytes of instructions before an xFE or xFF (at x1A3D0 which looks like just empty space).
  4. @Dizzor Twizzle - Can you try it again? It should work now!
  5. I think I successfully added support for both of the 32-team ROM bases I could find (one from 2014 and one from 2023) for the Everdrive. Anyone using an Everdrive, please let me know if you see weird data/output. I didn't do extensive testing, and there's a decent potential for an error somewhere.
  6. I'm still alive and every now and then doing something with Tecmo. I added support for the 28-team ROM for extracting stats from the Everdrive N8 Pro device. Eventually, I'd like to add support both of the 32-team ROMs.
  7. @Péter Szarka- I haven't yet had a chance to dig into this one, but I'm guessing you might have compression turned on. Check out @bruddog's post on this other thread.
  8. Just buy me a beer some day if we ever meet up 😀
  9. Updates: The tool should now be able to support exporting Single Game statistics from a save state generated with any 32-team ROM when coming from Nestopia 1.39 or Nestopia 1.40 Single-game extractions are still not supported with some 32-team ROMs from Nesticle or Nestopia 1.36
  10. Updates: The tool should now be able to export season stats from save state files (.nst, .ns1, .ns2, etc.) that were generated with a 32-team ROM from Nestopia 1.39 or Nestopia 1.40. Extracting season stats with save states that were generated from 32-team ROMs from Nesticle or Nestopia 1.36 is still not supported. Single-game extractions are not supported with some 32-team ROMs across any of the emulators There are two different 32-team ROM bases/templates that have been used over the years, and the tool only currently supports the one not using MMC5. I'll try to update that when I get a chance.
  11. @graylikethecolor - I'm looking into adding 32-team support. Can you remind me which emulator you were using to create the .sta file?
  12. @graylikethecolor- Just for troubleshooting help, can you let me know which emulator you are using? Edit: I actually just realized that the ROM is a 32-team ROM. And, at this point, the tool doesn't support parsing Season-level data for the 32-team ROM. And, I forgot I never wrapped up that portion of the tool. So, if I get motivated over Thanksgiving, I'll try to knock it out. So, unfortunately, there's not a good answer since it doesn't work
  13. Hey...so...I haven't been on here in a while. I'll try to take a look at this later this week.
  14. In case anyone is interested, I updated my roster viewing tool (http://tecmobowltools.com/TecmoSuperBowl) to support this ROM.
  15. @Jonesy - I sent you a message today. If you can get me the ROM and save state file, I'll try troubleshooting.
  16. @Respectedgen1us Sorry for the delayed response - I haven't been on the message boards a ton lately. Yes, the tool still exists, and it should work with the 32-team ROMs. Let me know if you have any issues. - http://www.tecmobowltools.com/SaveStateExporter - The site was down for a couple days around the end of year and early January, but it's back up and running now.
  17. @macknbyner - The tool should work now and have the offensive lineman in the season stat extraction tool. http://www.tecmobowltools.com/SaveStateExporter
  18. Hey, I can update the tool. I don't expect to bring it down any time soon. I haven't checked the boards in a while, so I just saw your post. I should be able to take a look this weekend.
  19. Dude - Kyle would be thrilled to be in my group. He'd kill me right now. I've played maybe 3 games since Burning Mort.
  20. Closing the loop: I had added these guys to the list at some point.
  21. @bruddog - Thanks for showing that to me! I updated the parser so that it handles that hack. @manyo360 - FYI
  22. @manyo360 Check it out and see how it works. It's somewhat odd in the output, but there's now data for first downs, quarter-by-quarter scoring, and final scores. Overtime is obviously not handled super well. Let me know what you think.
×
×
  • Create New...