Yeah, it was nice when I discovered that "submit run" button :D
Thanks, and you may indeed ask. I used Mesen. As per the link in the rules, it is considered one of the preferred emulators, hopefully that is still the case.
I actually DQ'd my own previous run of 8:46 since I was using a save state to jump back to the front of the game and subsequently learned that's not allowed. Now I always just use the reset and no save states while streaming/recording. They're indispensable for practicing so I figure that's fine.
For frame counting, I'm using this method: https://mattbraddock.com/yt-frame-timer/
Hopefully that's sufficiently accurate. I'll download a stream and upload it to youtube without modification (when Twitch's highlight functionality works, anyway) and that seems close enough. I haven't been in a fraction of a second situation yet. I'd love to know if there is a better way to do it, though.
Also, I could be overthinking this a bit :D
There are 6^6, or 46,656 possible row configurations from 111111 to 666666 and everything in between. I am assuming all of these combos can happen during the course of the game.
I have observed that there have been no repeats in looking at about 100 such rows. That is to be expected as my sample is pretty small. I was expecting that if I got one row repeating, every other row would repeat.
From doing some TAS on this game, there seems to be a dice row seeding algorithm that, as far as I can tell, is based on whatever dice are visible, or possibly just the top-most row. For example, if I let the dice fall on me without removing rows, the rows will consistently be the same. If I rewind and remove, say, one row, the remaining hidden rows will be different. I believe the CPU's drop area is governed by the same rules. As far as I can tell, the human's actions don't affect the dice rows that fall for the CPU and vice-versa.
I would say that it would be next to impossible for an average human brain to be able to do real-time calculations to predict the next rows, but I am guessing someone could figure out the next hidden row given the top-most row. Just a guess there.
My TAS took about 8 minutes and change. This suggest that there is a significant RNG component, or I'm not great at TASes, or some of both. I reckon I maximized the rows I got and the CPU did seem to get a good number of five-lines.
The current WR appears to be a combination of good RNG and even better execution.
Here's what I would say:
Run begins when selecting 3 Set and ends at the beginning of the sweep animation that shows the final score of the final round (e.g. 2-0). And of course, the usual caveats, no turbo buttons/messing with emulation speed, no state saves, etc.
It appears that the dice the players are "holding" disappear on the beginning of the sweep. That's a pretty solid indicator.
Some rules would be good. Maybe describe the run as a three-set tournament. It might be good to have a five and seven as well. And of course to describe the start and end events, just for verbosity.
Ok, sub 9 on the board. I know there is a lot of time to save, but my thumbs and/or my controller are having a hard time. I tried a game that takes a lot of precision, Adventures of Lolo, and I found that my 8bitdo usb controller is pretty sloppy, or I just don't know how to use a d-pad, not sure which. I think it's a combination of both. Any recommendations on hardware? I'm thinking an actual NES and actual original controllers might be good, although that takes a bit of an investment. I have the cartridge, though.
Good to know. I didn't know there could be a fourth place image until I saw this game.
Ahh, there is a big button that says "submit a run". How about I go that route :D
You know, it would probably help if I read the rules before setting up my timer. I was four seconds and change into the timer when I selected the second team, so it should be 9:48.
Ok, here's a link:
I'm not exactly sure what the process is to submit a speedrun, so hopefully this'll do. I was using GeForce Experience to record and then I used Lightworks free version to crop and trim and whatever. I have 9:52 on the timer. If anything is amiss, feel free to bring down the ax, it's basically a learning experience at this point. Thanks. I'm pretty sure I can do better than this time without a great deal of time/effort. Just setting a benchmark at this point.
I put speedrun in quotes because I'm not that fast with it. Anyway, I got 10:22.99 with my cheesy timer (unrecorded). I'll probably do a few streams just so it's recorded. My goal for now is just sub 10 minutes. Having watched a few runs that are actually fast, I think I have a good handle on what to do. I don't have the motivation nor the time to be a serious speed runner.
I actually think this game makes for a pretty interesting speed run. It has built-in suspense with running around and all the near-misses from tacklers, getting that onside kick back, etc.
If a turnover in downs lead to a safety, I wonder if that would save time. It might be a tall order, though.
Looks like the current record isn't using CDs so I guess that answers that question. spec, I was wondering why you went through the Halls of the Draracle rather than going straight to the Huline jungle. Seems like a bit of time could be saved. Maybe you would end up skipping some essential experience? Or maybe you need those ivory chips later?
I watched the whole run and I see that you need those ivory chips, mystery solved.
I was considering speed running this game. Just wondering about some of the conditions: Is it ok to use the GOG version? Finding the CDs would be a challenge and I don't even have a CD/DVD player on my computer.
Thanks!
I think I'll do that. Thanks!
Oh, ok. Thanks for indulging this new user.
On this run
https://www.speedrun.com/portal/run/y6526r6z
There is an asterisk by the time but no corresponding note. Is this the right place to post about such things or is there a better way to let a mod know? Thanks.