Hello people! Here is my first ever Tas, this one is a tas of Super Punch-Out!!
Super Punch-Out!! is a boxing game for the Super Nintendo where you have to fight vast opponents to become the Special Circuit champion.
Technical stuff
Emulator: BizHawk 2.10
Emulator settings changed: Controller, B = Z, A = X, Y = A, X = S
Checksum: 3604c855790f37db567e9b425252625045f86697 (sha1, hex lower case)
Other stuff:
No warps or passwords, No glitches (as far as I know :P), A few hits, No death, No save and restart
Aims: Fastest possible, done by exploiting the opponent's weaknesses
Information used for help: KoachKrab127's Super Punch Out tutorial (https://www.youtube.com/watch?v=ZqrSO5qUKQ0&list=PLzJ3rxOw8cbhKG-pRbuSxx45xAzjf0xVg)
Suggestion for publication image: A screenshot of Super Macho Man while he's about to do the multiple spin punches
DrD2k9: Claiming for judging.
DrD2k9: Welcome to TASVideos, TheOnlyOne!
We're always glad to have new members showing an interest in our hobby.
Our site strives to show off some of the best of what Tool Assistance in gaming has to offer; typically (but not always) from a speed optimization standpoint. Even when there is an additional goal besides simply going for speed, like Maximum Score; such runs are usually still expected to meet the stated goal as optimally as possible.
It appears you may have misunderstood the submission process and/or movie rules before submitting your run.
While your run is a generally good play, it is far from optimal when compared to our current publicaiton of this game.
Our rules require that a new submission must meet or beat known records (which is the the current publication for this case). Since you submtitted a run that does not beat the current publication, I'm guessing one of the three following situations is the case:
1) You didn't realize that your run didn't beat our current publication
2) You didn't realize that your run needed to beat our current publication in order to be accepted (perhaps you were thinking we worked like a leaderboard similar to speedrun.com?)
3) You didn't realize that the current publications existed before submitting your own run.
1) You didn't realize that your run didn't beat our current publication
2) You didn't realize that your run needed to beat our current publication in order to be accepted (perhaps you were thinking we worked like a leaderboard similar to speedrun.com?)
3) You didn't realize that the current publications existed before submitting your own run.
I don't want to discourage you when it comes to TASing, but we aren't able to publish a submission that doesn't beat the current publication. Thus, I must reject this run for reasons of optimization.
There are many in the community that would love to help give pointers and suggestions on how to improve your skills. This will allow you to create higher quality and more highly optimized TASes in the future. Please reach out to other members via the forums or via Discord for such help (I believe you've already joined the Discord server) .
For starters, I can offer a few points for ways to improve your TASing:
- Use other available tools besides just using savestates
- TAStudio: BizHawk contains this tool which is an input roll feature that allows you to specify which buttons are pressed on which specific frames. This allows for very precise timing of button presses for the most optimal play.
- This submission appears to be a recording of human play that used savestates to back up and retry certain portions of the game. It lacks the precision that is possible when using the TAStudio tool.
- End your movie on the last input necessary to get to the credits/endgame.
- This submission has A-button presses beyond where they are necessary. The last actual frame of input needed to get to the credits in your run is frame #86773 (the total #of frames for the movie would then be 86774 for a time of approximately 24 minutes)
- In conjunction with the previous point, don't have any empty frames of input at the end of your movie.
- Due to the way our site parses input files, blank inputs at the end of a run will artficially increase the displayed time of the run. In this case, the posted time of 27:45.92 is incorrect due to the extra blank frames. This submission contains 13,254 blank frames at the end of the run.
I hope these suggestions encourage you to continue TASing in the future. You are also welcome to use userfiles to store your runs that aren't being officially submitted for judgement.
Once again, welcome! We look forward to see what TASes you can produce as your skills improve!