At the time that £e Nécroyeur submitted his TAS, I had completed this one, but was having trouble writing the submission text. Upon viewing the run, I found that we'd had different goal priorities; £e Nécroyeur had real time then score, where I had game time, score, real time.
It's my belief that for this game, real time doesn't make sense as a goal, primarily because of the post-fight score tally. The bonus points at the end are based on the time remaining, creating a Sonic-type situation where finishing a fight slower is faster overall.
£e Nécroyeur's submission explains things well (apart from a few off-by-one errors), so I'll instead be focusing on the differences between the runs here.
DIP Switch Settings
As in the other TAS, the difficulty is set to hardest. However, the coinage has been left at its default setting of 1 credit/coin. As the other submission notes, manipulation potential for Texas Mac 1's "Ready" timer is very limited without losing frames. But there is one type of input that is read between entering the name and starting the ready timer: the coin slot, which is ignored if free play is enabled.
...Unfortunately it turns out it was actually slower. <_<
Rematches are also lowered to 3, not that it matters.
Loop 1
Texas Mac (2.12)
Identical to £e Nécroyeur's submission.
Kabuki (5.28)
Identical to £e Nécroyeur's submission. Both this fight and the later rounds gave me a lot of trouble trying to find the fastest strat, and everything else I tried failed.
Annoyingly, Kabuki ALSO can give power on unblocked attacks on some arm positions, just like Texas Mac, but they're too far out of the way. One of them requires taking damage, which ultimately takes too long. The other is right before Kabuki is pinned, but is completely useless because he's programmed to always counterattack at that position.
High score is the secondary goal, and so the moneybag is caught in this and all other rounds.
Any resemblance to other fighters is entirely coincidental.
Mask X (8.03)
Identical to £e Nécroyeur's submission.
Alice & Ape III (2.60)
Identical to £e Nécroyeur's submission.
Frank Jr. (7.25)
This is the first place where the strats differ. Since in-game time is the primary goal for this TAS, the best thing to do in this and all other rounds is to manipulate a WAIT attack. The fire breath takes less in-game time to recover from, but is only available when Frank's arm reaches its lowest position.
Loops 2-4
Texas Mac (1.33,1.60,1.60)
Next.
Mask X (12.20,12.24,12.24)
The extra frame in loops 3 and 4 comes from Mask X's headbutt, which has a tighter dodge window.
Also, identical to £e Nécroyeur's submission.
Alice & Ape III (11.51,11.51,4.31)
The only fight after loop 1 that actually has a faster time in lower rounds. The culprit here was, to my surprise, this game actually has AI changes at certain times in the fight. In this case, the damage done by a double power attack in the starting position decreases from 64 to 48 once the clock hits 3 seconds. In loops 2 and 3, even tool-assisted button mashing isn't enough to beat this time limit, but in loop 4 the clock speed actually decreases, allowing an immediate win.
Again, in-game time changes the strategy here. On the first set of exclamation marks I stop short of getting all 10 and instead do a single power attack. At the resulting arm level, Ape III is guaranteed to counterattack instead of being guaranteed to just sit there and do nothing, giving the fight an extra clock stop phase.
Frank Jr. (6.40, 8.00, 8.85)
In addition to the reliance on WAIT attack clock stops the start of the fight is different. An immediate first press is of minimal help because it gives so few exclamation marks. The resulting choice between waiting for Frank to recover or pressing immediately and taking damage costs too much time. Instead I wait until the first press gives no exclamation marks, allowing an immediate second press.
Kabuki (15.10,15.10,15.10)
The end of input is delayed to gain an additional 500 points before Kabuki's arm is pinned. Otherwise these fights are identical to £e Nécroyeur's submission.
In the final rematch the window to counter Kabuki's final press is only 1 frame.
feos: This submission is quite tricky. Here's a list of problems to resolve, as usual.
Tier. Looking at the percentage alone (77% support), one might think this movie was well received. Votes are somewhat minimal though, just 9. Now let's count the votes in actual posts, where people use to provide their take in a reliable way. 2 "yes" votes and 1 "meh". Doesn't look like people really got excited by this run. Lack of feedback is also a proof that it's not that entertaining to the audience.
And the gameplay kinda proves that: even though it has insane frame windows that can only be handles on a TAS level, and crazy point calculation system that can also only be routed precisely in a TAS, this boils down to optimization problems. And the impression from this gameplay is that it looks simplistic: you just have to pin the opponent's hand, that's all. Some comic take is there, but it doesn't change how narrow the range of actions is. And this game also loops the opponents for a few times, so once you see the first loop, you've basically seen all the gameplay has to offer entertainment-wise. Vault.
Maximum score. Some suggest that this might be considered a full completion type of goal in this game, since you can not collect an infinite amount of points. Indeed you can't, the levels have a time limit. But even though the count can not be infinite, or capped in a way similar to 999,999, where it either stops in some games or overflows in others, there's no designed limit where you could say "I collected all the points this game has to offer".
There's no fullness here, no count that would be equal to 100%. The score that gets calculated in such absurdly esoteric ways that it makes it impossible to prove that the score achieved in a given run is indeed maximal. The possibilities to test are endless, and even though it would require an overkilling amount of resources to do an exhaustive search, it would still be only "maxing out the score", not full completion. And therefore, it is an unvaultable goal.
In-game time. The argument given pro this goal is that in this game we deal with "a Sonic-type situation where finishing a fight slower is faster overall", and that it's "stomping opponents flat faster" than the other run. Both are false.
Sonic-type situation means that the player has to reach the end of the level as fast as possible, regardless of how many points the game will give, and ignoring the time the score tally will take. That allows the players to have a fair optimization competition, because the in-game time reflects the completion speed perfectly, and the real time fails at that due to the score tally. The level is still being completed faster and faster.
In this game, as the author admitted, ignoring the score tally doesn't give as much benefit, just a few frames, that can be easily lost if you wait too much. But what's more important, all the opponents that are different in this run are in fact defeated slower than in the run this one competes with.
IGT
Frames
First Frank Jr. fight:
£e Nécroyeur
10:80
1142
McHazard
7:25
1282
Second Ape 3 fight
£e Nécroyeur
19:96
773
McHazard
11:51
778
Second Frank Jr. fight
£e Nécroyeur
15:16
933
McHazard
6:40
1198
Third Ape 3 fight
£ Nécroyeur
19:96
773
McHazard
11:51
778
Third Frank Jr. fight
£e Nécroyeur
18:95
933
McHazard
8:00
1198
Fourth Frank Jr. fight
£e Nécroyeur
20:96
933
McHazard
8:85
1206
The in-game time is only shorter because the author explicitly manipulates it to be shorter: he makes the opponent do the attacks that take more real time but freeze in in-game timer. It's not the score tally that makes this run longer, but the completion of the rounds that is slower.
Rejecting, with no foreseeable way to make a full completion run for this game.
To what extent does that hold true? Wouldn't there be a score where this balances out between time saved in fight and time wasted in points? I don't think I ever encountered a game (yet) where using most of the time allocated ends up being faster, but hey, I never played this one, so idk?
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
Wouldn't that defeat the purpose of optimization competition?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
I'm still tracking down the last few details of how the score calculation works, but it looks like the answer is going to be "not as much as I'd thought". The clock stops from getting power and Frank telling you to WAIT cost a lot more real time, as do the differences in score countdowns between two different strats. If you try to do the same strat slower, you'll only get a couple frames out of it, and you'll lose them again if you delay too much.
Oh, and there's one more thing I forgot to add to the submission. While working on one of the later Kabuki fights I'd found that I'd gotten a slower time for no apparent reason. Turned out it was something really weird. I'd used a full button press for luck manipulation... and when you're in the tap button phase, you tap the button, and there are no more exclamation marks or dollar signs, the game adds a tenth of a second to the timer.
EDIT: Alright so scoring works like this. The remaining time is rounded up to the next tenth of a second. Then, every two frames the bonus goes up by 400 points. When there's one second or less uncounted, this changes to 40 points every 2 frames. This is skipped entirely if the timer runs all the way to 1 minute, saving another 4 frames on top of that.
So yeah, not much to work with there. Without a strat change, any delay that takes the game time past xx.90 seconds is wasted, and that's only useful if the clock is fast enough and the .1 second penalties start early enough.
That's another thing I looked at; hitting the button too much doesn't immediately start adding time. There's a counter at D071 that determines how many extra times you can press the button. It's only when that counter goes down to 0 that pressing the button again adds the tenth of a second.
Anyone got an encode for this? I want to watch it but I have no idea how to get this fork of MAME set up... or even where to get it in the first place.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Yeah I did eventually find it myself on the site. I understand that it's an interim thing until proper re-recording is implemented in the mainline MAME codebase, but until then, maybe a link should be added in the Preferred emulators tab on the Emulators page?
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
It's not a preferred emulator, so it obviously can't be added there. It's a test thing that people are supposed to use at their own risk (not so risky honestly).
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
I've been working on a comparison script for 4.5 hours straight. And when it was ready for for inserting the values, I got a sudden overflow that cleared the file.
It even utilized an external plugin to allow avisynth do a for loop.
And it happened right before I decided to go to sleep. So that I could forget what was in the script. How fucking cute.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Joined: 10/12/2011
Posts: 6438
Location: The land down under.
This vs #5476: £e_Nécroyeur's Arcade Arm Wrestling in 07:43.37
Ok. Just to throw my thoughts in.
In terms of everything that I prefer, I like the other.
In terms of the tradeoffs you provide it all.
That being written I'm going to give it the perspective of Ice Climber.
Where more. Doesn't always mean more entertaining (imo).
Meh Vote.
This one for publication.
Since McHazard states he's focused on ingame time as well:
Disables Comments and Ratings for the YouTube account.Something better for yourself and also others.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.