This is a version of Sonic the Hedgehog 2 with Sonic & Knuckles locked on it. The title character is replaced by his rival, Knuckles. The levels remain unchanged. There is more than just an appearance change to this game. Knuckles' abilities remain intact. If you haven't seen Sonic the Hedgehog 2 completed before, you may wish to do so before seeing what a character with gliding and wall climbing can accomplish. The submission is an improvement of 5.9 seconds in-game time.

Game objectives

  • Emulator used: Gens version 11a
  • Aims for fastest in-game time, then fastest real time
  • Abuses programming errors
  • Takes damage to save time
  • Manipulates luck

About The Movie

This submission consists mostly of minor improvements which came from better positioning and more optimal movement. There are some route changes and a few new techniques are used. This movie initially started out as an individual level run, showing an improved route for Mystic Cave 2 that was also viable for RTA's. From there, WST suggested applying Kiske's monitor trick to Emerald Hill 1 and afterward, recommended improving the current TAS in whole. Thanks goes to Kiske, Tee-N-Tee, Aglar, and WST for making the first published TAS. They did a lot of work in routing the run and pulling off several maneuvers that required precise positions and speeds that otherwise may not have been included in this submission (Aquatic Ruin 1 had a jump over the pool with the revolving platforms that was notably difficult to execute, even with a known speed and position that worked).

Table of Times (minutes:seconds::frames)

ActNew TimeOld TimeFrames SavedTotal Frames
Emerald Hill 10:14::110:14::281717
Emerald Hill 20:33::250:33::32724
Chemical Plant 10:14::460:14::47125
Chemical Plant 20:31::540:32::041035
Aquatic Ruin 10:12::400:12::521247
Aquatic Ruin 20:28::270:28::27047
Casino Night 10:15::400:15::40047
Casino Night 20:32::050:32::09451
Hill Top 10:23::360:23::562071
Hill Top 20:42::030:42::5956127
Mystic Cave 10:24::030:24::2017144
Mystic Cave 20:28::510:30::2190234
Oil Ocean 10:16::520:16::564238
Oil Ocean 20:28::590:29::2122260
Metropolis 10:28::320:29::0432292
Metropolis 20:12::370:12::4811303
Metropolis 30:46::490:47::1728331
Sky Chase2:05::572:05::581332
Wing Fortress1:20::471:21::0821353
Death Egg0:40::270:40::281354
Total11:22::4111:28::35354

General Information Relevant To The Submission

The following information is not new to speedruns of this game, rather, it is here for convenience.
  • The game has a hidden in-game timer that counts the frames. It does not increment during lag frames or while the game is paused.
  • When performing a jump, Knuckles does not move for one frame so jumping is limited to when it is faster overall and this restriction does make a difference throughout the run.
  • On horizontal ground, Knuckles will lose speed when rolling, while holding forward when running will maintain speed. When traveling down slopes, Knuckles accelerates faster while rolling than running. Transitioning from rolling to running is done by jumping or falling off the ground.
  • Bounce height can be controlled by holding either A, B, or C which will keep a higher vertical speed until it falls below 4 pixels per frame. Releasing any of those buttons will immediately set the vertical speed to 4 pixels per frame if it was above that value.
  • Knuckles will lose horizontal speed if the vertical speed is upward and less than 4 pixels per frame. This is avoided when possible by jumping from slopes that give Knuckles a downward vertical speed or by bumping a ceiling.
  • Spindash release speed is controlled by how many times the buttons A, B, or C are pressed and how long the spindash is held before being released. The first button press sets the held spindash speed at 8 pixels per frame. Subsequent button presses raise the speed by 1 pixel per frame and each frame the spindash is held lowers the speed by 1/32 of the held speed value. The range for spindash speed is bounded to a minimum 8 pixels per frame and a maximum of 12 pixels per frame and the release speed only occurs in increments of 1/2 pixel per frame. Thus, it takes 6 button presses to release a maximum speed spindash.
  • Sprite ejection occurs when Knuckles is inside a sprite and is colliding with one of its four sides. This pushes Knuckles out in the direction of the side that is being collided with. This is generally used to get inside terrain. In the run, this is most commonly done by gliding onto a wall with a monitor in a corner without breaking it, and then falling from the wall.
  • Zips occur when Knuckles is inside solid terrain. The game ejects Knuckles at speeds up to 32 pixels per frame in the opposite direction that Knuckles is traveling. This is commonly useful for performing a level wrap but is also good for just going fast.
  • Level wraps are an effective way to get to the end of a level quickly. The left edge of every level has an invisible wall that is 16 pixels wide. Knuckles can pass through this boundary by having sufficient speed to avoid collision with this wall. This underflows the value for horizontal position and the game then caps the now large value to a position at the end of the level. In levels with a capsule, the maximum position is significantly past the capsule and the height of the floor there does not correspond with the floor at the boss fight. Because the boss fight forces Knuckles to be within the horizontal limits of the camera when the camera locks there, Knuckles can jump before warping to the boss fight, starting the boss fight in mid air.
  • Camera speed is capped at 16 pixels per frame. Traveling faster than this will cause Knuckles to get ahead of the camera. The horizontal position of the camera is important as it determines when sprites (such as the sign post) load and can be manipulated, such as spindashing before performing a level wrap, which moves the camera to the right and delays it from following Knuckles to the left. Knuckles generally does not interact with sprites that are out of view of the camera.
  • Landing from a glide occurs differently between terrain and sprites. On terrain, Knuckles will stay in a ducking position for 15 frames and is unable to walk or spindash. On sprites, Knuckles either transitions into walking or running with horizontal speed, or transitions into standing with no horizontal speed. Sprites provide a significant advantage in that a spindash can be performed without waiting.

Resources

Game Resources has useful RAM addresses and additional information.

Stage By Stage Comments

Emerald Hill 1

Here, a technique found by Kiske was implemented where Knuckles can catch some air when rolling through a monitor which allows Knuckles to transition from rolling to running without losing any speed. This is done by hitting the left most pixel of the monitor with sufficient speed such that the next frame, Knuckles would be past the monitor. An additional frame was saved by spindashing from a more forward position on the angled yellow spring.

Emerald Hill 2

A few frames were saved by getting a faster horizontal speed when jumping over the spikes before the loops and saved some more time by using fewer jumps to gain enough speed to get ahead of the camera.

Chemical Plant 1

Saved 1 frame by turning around at an earlier position. The time spent braking was longer but was compensated by less time traveling to the turn around spot. A level wrap is used as the published run did.

Chemical Plant 2

Saved a few frames by landing on one of the revolving platforms which allowed for spindashing sooner. Also saved time with better positioning for the slope jumps which yielded more speed. Specifically, there are positions that get a better change in slope for jumping from and then the loops have slopes that are a less direct path so these are avoided to make small corner cuts.

Aquatic Ruin 1

Saved 12 frames by jumping into the ceiling of the first log rather than jumping on top and stopping for a spindash. The same zip as the published run was used, with some small changes in positioning.

Aquatic Ruin 2

This is the first level where no in-game time improvements were found. The wait is necessary for the swinging platform to get to a useful position and a level wrap is performed, like the published run. The boss has two timers that it waits for before loading and this occurs right before the boss fight so the game is paused for those two timers to save in-game time without losing any real time. Hitting the boss as it reaches the right edge of travel causes it to skip the explosion scene.

Casino Night 1

The only level with no improvements of any kind. A spindash prior to zipping for the level wrap delays the camera sufficiently to be further right upon level wrapping compared to not spindashing.

Casino Night 2

Saved 4 frames by landing on the top platform earlier. Sprite ejection is used to get inside the terrain and after some maneuvering, a zip is used to level wrap.

Hill Top 1

The route change in this level uses a higher path which was more direct and allowed for stopping on a sprite for the spindash before the high jump. The zip past the lava zone works as it does because a spindash before the zip causes a delay in the camera following Knuckles, allowing Knuckles to get far ahead enough that the giant wall sprite does not load until Knuckles is past it.

Hill Top 2

This level had many improvements. The improvements in the first half can be summarized by better braking, faster wall climbing, and better positioning that allowed for faster running speeds. The second cave section was improved by falling to the variable-height sprite rather than gliding, and skipping the first yellow spring near the exit. The boss fight was improved by not jumping prior to reaching the loading zone and hitting the boss on the first available frame.

Mystic Cave 1

Time savings in this level came from various improvements as well. Two jumps to switch to running were omitted, a faster approach to the wall with hidden spikes was used, better positioning was used on top of the rotating boxes, and a 5-tap spindash was quicker than a 6-tap spindash for approaching the second gate. The last 2 frame savings came from some manipulation of the last 2 crushers. The second to last crusher was loaded 1 frame earlier by omitting a jump and the last crusher was loaded later by waiting to load it. This put the left crusher at the desired height to jump earlier and the right crusher was not in the way for that jump.

Mystic Cave 2

The level wrap was achieved sooner by initiating a zip around the same area that the previous run was ejected upward. The difference was delaying the glide to grab the wall below the one tile opening between the two mostly solid blocks (the blocks are stacked vertically). From there Knuckles could climb onto the lower block and walk into the opening to get the zip. Knuckles is taller than one tile and collides with the ceiling after a few pixels of travel.
Image of the terrain
-
|XX|  Represents an all-way solid tile (16x16 pixels)
-
                                  -
                                  |XX|XX|
Previous destination of glide --> -
                                     |XX|
                                  -
New destination of glide -> |XX|XX|
                                  -
                                  |XX|XX|
                                  -

Oil Ocean 1

The time savings in this level came from a more optimal entrance into the oil. Faster speeds can be achieved upon jumping from the third U-shaped platform but the speeds are insufficient to get far enough ahead to perform several of the jumps that maintain speed.

Oil Ocean 2

One frame was saved by entering the oil at an earlier point. The rest of the improvements were from better braking. The end of the level, just as the published run, warps Knuckles upward the same distance that the kill plane moves.

Metropolis 1

This run performed the crusher clip earlier by falling in a location that loaded it sooner and therefore moved down sooner. A faster method was used to go up between the walls covered in yellow bumpers. A shorter jump saved time in gliding through the second cage. After clipping through the wall by the invincibility monitor, this run was 65 frames ahead of the published run. Unfortunately, the nearby spikes are controlled by a level-based timer which put a spike in the way of the route. As a result, 40 of those frames were lost from waiting for it to move out of the way. More time was saved after that point by falling past the switch controlled gate faster and by running up the steep slope at the end longer before jumping.

Metropolis 2

Saved 10 frames by rolling over the switch rather than jumping over it. The same zip and level wrap are used.

Metropolis 3

It turns out that clipping through the wall by the ring monitor was faster than the spring because it does not unload the crusher used to go to the zip location. The crusher is a camera timer-based object so keeping it loaded earlier meant it would move down earlier. An additional 2 frames were saved with a faster boss fight.

Sky Chase

By this point, a tool assisted speedrun of this level is trivial, however, 1 frame was saved because the previous run did not have the plane low enough to maintain sufficient speed on the last jump to get the fastest time (missing the required horizontal position to end the level by 1 pixel). In this run, Knuckles hits the kill plane and the end of the level on the same frame. This completes the level and Knuckles does not lose a life.

Wing Fortress

This run saved time by not avoiding the rings near the beginning of the level and squeezed 2 more frames out by jumping later to trigger the ending. This works because it gets the camera to the required vertical position sooner by spending more time in the air while still ahead of the camera. The camera moves at 6 pixels per frame to catch up to Knuckles when on the ground. The camera moves at 16 pixels per frame while catching up to Knuckles in the air and then at the same rate when caught up, which is still faster than 6 pixels per frame.
The trick used here and in the published run is performed by standing on a sprite that subsequently unloads. This gives Knuckles the property of maintaining the slope of the last terrain landed on. This also allows Knuckles to keep the same vertical position when gliding onto a floor, which is a few pixels below the top of the floor. Without this trick, the game would move Knuckles to the correct height on the next frame. These properties allow Knuckles to zip from many locations and run in the air.

Death Egg

One frame was saved in the final boss battle. This was made possible by getting a higher bounce from the third hit. It turns out that Knuckles' vertical speed was greater than 4 pixels per frame which meant that the height could be controlled by holding A, B, or C (In this case it was 1 frame). Amazingly, having to hit the boss one frame earlier in its cycle for the rest of the battle made copying the moves in the previous run not possible. With some fairly precise positioning, it was barely possible to maintain the one frame lead throughout the fight.

Real Time Savings

With runs of this game competing for fastest in-game time and differences in real time not being comparable for reasons that will be explained, this section of text would not exist. However, the improvements were significant (for the most part) and the input file is faster by a very small margin so the efforts to avoid a longer input file are discussed below.

Capsules And The Capsule Animals

Shortly after hitting a capsule top, 8 animals will spawn and a capsule timer starts counting down from 179 at a rate of 1 unit per frame until it reaches a value of 1. The timer does not increment on paused frames. On the next frame, the timer changes to 180 which is when the game checks for the presence of animals. When this check sees zero animals, the value changes to 0 and the game proceeds to bringing in the bonus tallies.
When an animal spawns, it starts counting down a timer which triggers the animal to jump. The 8 initial animals have unique timers that range from 98 to 154 in increments of 8. All future animals start with a timer of 12.
Animals will only spawn when the lowest 3 bits of the power-on timer are 0. If the game is paused on this frame, the animal will not spawn. If an animal spawn occurs the frame before the capsule timer changes to 180, the newly spawned animal will be present for the first frame of the check for animals and will unload the next frame. This event will delay the bonus tally one frame and has a 1 in 8 chance of occurring.
The primary method of saving time here is by deleting animal spawns for those animals that would remain on screen longer than the initial set of animals. The game loads several animals that jump later than the initial animals and are usually deleted unless they jumped to the right and left the screen early enough to not delay scrolling the screen to clear the animals that jumped to the left. In levels where the camera could not be scrolled upward, the capsule is generally too far to the left to manipulate animals to jump right, although this is still sometimes faster when manipulating the later animals to jump and is usually combined with deleting animal spawns.
The capsule animals can be manipulated before breaking the capsule by advancing the RNG seed that controls the animals type and horizontal travel speed before breaking the capsule. This occurs by destroying badniks (spawns an animal), deleting or adding boss explosions (explosions spawn on the same frames that animals spawn), and allowing bubbles to spawn in Aquatic Ruin. The boss explosions also use a timer that starts at 179, similar to the capsule timer, and does not increment on paused frames. Because the boss explosion timer does not start on a multiple of 8, two identical runs of a level with different power-on timer values may end with a different RNG seed. The direction they jump can also be manipulated. The direction is determined when they land by the fourth lowest bit in the power-on timer which changes every 16 frames.
No instances in this run were found where adding animals was faster.
Objects are dynamically loaded, so the location of useful RAM addresses change between the levels. These objects will load at addresses from $B400 up to $CFC0 and occupy $40 bytes. The object with the capsule timer can be identified by finding the object with the byte offset $00 set to $3E and the byte offset $25 set to $02. The timer can be found at the byte offset $1F. Capsule animal jump timers are located at bytes offset $37. The other addresses used were the long at $F636 (RNG seed) and the byte at $FE0F (Power-on timer, partial)
Due to in-game time being prioritized over real time and the way capsule animals work, comparing time spent during the capsule animal release may not always be a fair comparison of optimization during those parts.

Time Bonus

Finishing a level in less than 30 seconds yields a time bonus of 50000. Finishing a level from 30 to 44 seconds yields a time bonus of 10000. Bonus values increment at a rate of 100 points per frame. This makes finishing a level in 0:29::59 399 frames slower than 0:30::00. The next fastest time would finish the level in 0:23::19 and is the primary reason why speedruns of this game aim for fastest in-game time.
No other instances were relevant in this run but this happens at every transition to a lower time bonus. If the ring bonus is larger than the time bonus, then that becomes the limiting factor for fastest real time.

Lag

Lag is minimized, usually with seemingly random changes in movement.

Real Time Table Of Times (frames saved)

ActReal Time
Minus
In Game Time
In Game Time
(From 1st Table)
Real Time
(Sum of Previous
Columns)
Total
Emerald Hill 10171717
Emerald Hill 2371027
Chemical Plant 101128
Chemical Plant 245105583
Aquatic Ruin 11121396
Aquatic Ruin 2404100
Casino Night 1000100
Casino Night 2044104
Hill Top 1-12019123
Hill Top 2-7356-17106
Mystic Cave 101717123
Mystic Cave 2-39190-301-178
Oil Ocean 1044-174
Oil Ocean 2562278-96
Metropolis 103232-64
Metropolis 221113-51
Metropolis 332831-20
Sky Chase011-19
Wing Fortress021212
Death Egg0113
Total-3513543
The stage by stage comments below generally refer times savings to the "Real Time Minus In Game Time" column which is where lag, capsule animal manipulation, and bonus tallies are accounted for.

Emerald Hill 2

Pausing to delete or delay an animal spawn was unnecessary, saving 3 frames. This was also the only instance where animals were cleared from the screen by looking up and an animal spawned as the capsule timer expired.

Chemical Plant 2

4 frames of lag were saved by going through the levels lowest loop slower. This required a careful selection of inputs to get the speed and positions that would not get lag and still be fast enough to jump to the top route. The rest of the savings came from animal manipulation (deleted 5 animal spawns).

Aquatic Ruin 1

1 lag frame was saved by using a better selection of movement while ahead of the camera.

Aquatic Ruin 2

Using the same inputs as the published run resulted in an unfavorable animal spawn that required pausing for one frame to delete the spawn. To prevent this, a badnik was destroyed before the level wrap which provided animal spawns that required no pauses.

Hill Top 1

1 extra frame of lag was generated from taking damage with more rings which are unavoidable in the faster route.

Hill Top 2

The published run was able to look up and scroll the animals off of the camera which came at the cost of some in-game time. Being unable to perform that maneuver, 3 pauses were used to delete 2 explosions to advance the RNG seed and 5 animal spawns were deleted, limiting the net loss to 17 frames.

Mystic Cave 2

All of the non-in-game time lost here was caused by getting a larger time bonus. One animal spawn had to be deleted to prevent an animal from remaining on screen late.

Oil Ocean 2

Saved 56 frames from animal manipulation (13 paused frames to deleted 3 animal spawns and manipulate jump direction).

Metropolis 2

Saved 2 frames of lag by controlling the speed and position on the way to the lava platform.

Metropolis 3

Saved 2 frames of lag by rolling on the first sprite rather than running. 1 frame was saved by not getting the last frame animal spawn that the published run had.

Suggested screen shots: 36487, 22066, 53910, other.

GoddessMaria: Judging..
GoddessMaria: Hello Zurggriff and welcome to TASVideos! I must say that this is quite an amazing and impressive work you've done. Not often do newcomers come in with their first ever TAS and beat an already solid published movie, so congrats! In regards to the matter of what constitutes as an improvements... Sonic runs have always aimed for In-Game Time (IGT), not Real-Time, and this submission is no exception. The submission is indeed very well done on a technical scale, the entertainment value is really good, and the audience response was very positive overall. Therefore...
I'm accepting this to Moons as an improvement to the previous movie.
feos: Finally I can pub something.

TASVideoAgent
They/Them
Moderator
Joined: 8/3/2004
Posts: 14858
Location: 127.0.0.1
This topic is for the purpose of discussing #5373: Zurggriff's Genesis Sonic the Hedgehog 2 in 17:41.85
Patashu
He/Him
Joined: 10/2/2005
Posts: 4014
Typo: The submission is a 3 frame improvement over the published run (5.9 seconds in-game time). -> 354 frames The submission text was very nice to read! I'll have to watch this TAS later.
My Chiptune music, made in Famitracker: http://soundcloud.com/patashu My twitch. I stream mostly shmups & rhythm games http://twitch.tv/patashu My youtube, again shmups and rhythm games and misc stuff: http://youtube.com/user/patashu
Experienced player (601)
Joined: 10/23/2004
Posts: 706
I also thought it was a typo but the later table (Real Time Table Of Times (frames saved)) seems to confirm that it's only 3 frames saved. I'm still confused by what's going on in that table though.
Current Project: - Mario Kart 64
BigBoct
He/Him
Editor, Former player
Joined: 8/9/2007
Posts: 1692
Location: Tiffin/Republic, OH
The level comments explain it; most of the real-time saved throughout the run is lost to a 50k time bonus tickdown in Mystic Cave 2.
Previous Name: boct1584
Editor, Experienced player (559)
Joined: 10/22/2016
Posts: 581
Location: Argentina
Nice improvements easy yes for me, now just left the Ring-Attack :P
You can see more TASes on my youtube channel
Joined: 12/7/2016
Posts: 33
Something I dont understand. Why at marks close of 30 seconds are optimized to less than 30 seconds? It is faster to add a score of 10,000 than one of 50,000. Mysctic Cave Zone 2 is a case.
Some Zamasu's quotes: - When I was invited to this place, I thought you would teach me about justice. However, does the justice of the gods not only pass by to observe? - Every time I am attacked, I enjoy my immortality.
GoddessMaria
She/Her
Reviewer, Experienced player (849)
Joined: 5/29/2009
Posts: 514
Location: Hell...
Temp encode (added to Submission Text as well): Link to video
Current projects: failing at life
Patashu
He/Him
Joined: 10/2/2005
Posts: 4014
Zamasu wrote:
Something I dont understand. Why at marks close of 30 seconds are optimized to less than 30 seconds? It is faster to add a score of 10,000 than one of 50,000. Mysctic Cave Zone 2 is a case.
It is considered less interesting to optimize for real time than for in-game time, because once you are optimizing for real time, there is no point in trying to make stages faster than 30 seconds but slower than 23 seconds faster for in-game time (as it is slower real-time than just waiting until 30 seconds is hit then taking the sign). As a result, all speedruns and TASes of Genesis Sonic games are timed by in-game time, not real time. The submission notes go into further detail, ctrl+f for 'Real Time Savings'.
My Chiptune music, made in Famitracker: http://soundcloud.com/patashu My twitch. I stream mostly shmups & rhythm games http://twitch.tv/patashu My youtube, again shmups and rhythm games and misc stuff: http://youtube.com/user/patashu
Post subject: Submission Edit
Active player (437)
Joined: 11/16/2016
Posts: 34
The first paragraph was changed to distinguish in-game time from real time. The column labels in the second table have been changed for clarification. The first completed revision of this movie file was 5 real time frames slower than the published movie so information explaining why the movie file should obsolete the published movie while having a longer input file seemed appropriate.
Spikestuff
They/Them
Editor, Publisher, Expert player (2284)
Joined: 10/12/2011
Posts: 6336
Location: The land down under.
Also to point out one of the objectives in the submission it mentions that it Aims for fastest in-game time. Which when you look into it, it's mainly dominated by Sonic TASes.
WebNations/Sabih wrote:
+fsvgm777 never censoring anything.
Disables Comments and Ratings for the YouTube account. Something better for yourself and also others.
WST
She/Her
Active player (442)
Joined: 10/6/2011
Posts: 1690
Location: RU · ID · AM
* Beats Tee-N-Tee on Death Egg zone * I was waiting for this to be submitted. It was a great pleasure to watch this. Easy yes vote, of course. Now do the same on Sonic 2 itself ^_^_^
S3&A [Amy amy%] improvement (with Evil_3D & kaan55) — currently in SPZ2 my TAS channel · If I ever come into your dream, I’ll be riding an eggship :)
Editor, Experienced player (559)
Joined: 10/22/2016
Posts: 581
Location: Argentina
A new run without horizontal underflow will be interesting, specially in CNZ and MTZ, and don't touch the oil rule in OOZ :P
You can see more TASes on my youtube channel
GoddessMaria
She/Her
Reviewer, Experienced player (849)
Joined: 5/29/2009
Posts: 514
Location: Hell...
If there is anymore thoughts or comments for this submission, please say so now.
Current projects: failing at life
WST
She/Her
Active player (442)
Joined: 10/6/2011
Posts: 1690
Location: RU · ID · AM
GoddessMaria wrote:
If there is anymore thoughts or comments for this submission, please say so now.
I am deeply impressed by how well it’s done. Usually when I see a Sonic submission, I post info on possible improvements (example, another one, one more), but this particular run is done at an exceptionally high level, absolutely beyond my abilities and understanding. I know only 2 people whose runs cause similar feelings when watching them frame by frame — they are Aglar and Tee-N-Tee. This run is just like it’s done by one of them.
S3&A [Amy amy%] improvement (with Evil_3D & kaan55) — currently in SPZ2 my TAS channel · If I ever come into your dream, I’ll be riding an eggship :)
Wobmiar
She/Her
Player (75)
Joined: 10/20/2015
Posts: 171
I have a (maybe) stupid question, but I remembered reading the rules, is a 3 frames improvement in a 63629 frame run can actually be accepted? I know we are considering the frame precision in a TAS, but is it really enough to be considered an improvement? Over, maybe, the published movie, who did most of the job this submission is submitting? Well, if it's the same autor, I think it's ok, but, well, if it's not, would it be accepted? (think of this as a general question, not only for this specific TAS)
I like colors
Samsara
She/They
Senior Judge, Site Admin, Expert player (2120)
Joined: 11/13/2006
Posts: 2792
Location: Northern California
1. This is technically a 6 second improvement in in-game time, which is what nearly all Sonic TASes aim for. It's only pushed down to 3 frames because of a much longer bonus screen countdown in one stage. 2. One-frame improvements have been accepted in the past: [1330] NES Super Mario Bros. "warps" by klmz in 04:57.33 - Previous published run [1715] NES Super Mario Bros. "warps" by HappyLee in 04:57.31 - Current published run, only 1 frame faster What matters when judging an improvement is that there is at least some form of improvement in the gameplay, whether it's 1 frame or 10000 frames, and that the rest of the gameplay is at the very least of an equal level of tech quality to the previous run. I.E, you can't use a trick that saves 40 seconds, lose 35 seconds of that due to extremely sloppy play, and then submit it as a 5 second improvement. Any time lost in an improvement run, even if it means the improvement is "slower", has to be completely unavoidable. In this case, it's justified, because there's an unavoidable time loss (a longer score counter) directly tied to a gameplay improvement. Other cases where it's justified include more accurate lag/loading emulation (see roughly half of Alyosha's published NES runs) or the introduction of a mandatory BIOS screen (see most PSX improvements after BizHawk introduced the PSX core), or, heck, why not both: [1518] PSX Umihara Kawase Shun by Mukki in 02:10.23 - Original run [2962] PSX Umihara Kawase Shun by Samsara in 02:18.75 - Current published run: 12 seconds faster in-game time, but 8 seconds slower in real time due to the BIOS screen and more accurate loading Hopefully this makes sense.
TASvideos Admin and acting Senior Judge 💙 | Cohost
warmCabin wrote:
You shouldn't need a degree in computer science to get into this hobby.
Wobmiar
She/Her
Player (75)
Joined: 10/20/2015
Posts: 171
Well, technically, most of the work on the improvement... Comes from the precedent authors, no? If I take someone's run, find a 3 frame improvement, place it, and submit, I'm doubting I can really take the credit for the run (again, talking in general, not for this run in particular, I know (and see) the work done on this run) Anyway, thanks for the info :)
I like colors
WST
She/Her
Active player (442)
Joined: 10/6/2011
Posts: 1690
Location: RU · ID · AM
Wobmiar wrote:
Well, technically, most of the work on the improvement... Comes from the precedent authors, no? If I take someone's run, find a 3 frame improvement, place it, and submit, I'm doubting I can really take the credit for the run (again, talking in general, not for this run in particular, I know (and see) the work done on this run) Anyway, thanks for the info :)
Did you read Samsara’s message? Every single stage is redone, no Kiske’s or my input survived. This is a milestone run — a monumental work, which you are treating as a dirty try, at least these words look like that
Wobmiar wrote:
If I take someone's run, find a 3 frame improvement
S3&A [Amy amy%] improvement (with Evil_3D & kaan55) — currently in SPZ2 my TAS channel · If I ever come into your dream, I’ll be riding an eggship :)
Wobmiar
She/Her
Player (75)
Joined: 10/20/2015
Posts: 171
Well, I also said
Wobmiar wrote:
(again, talking in general, not for this run in particular, I know (and see) the work done on this run)
I was talking purely theorically, not exactly on this run. I think this run is a monumental work too, don't create words I didn't say please.
Samsara wrote:
some form of improvement in the gameplay, whether it's 1 frame or 10000 frames
If I understand well, then, if PURELY THEORICALLY I find someone's TAS and find a 1 frame improvement, this frame being a good frame save (when you talk about improvement in gameplay, let's assume this frame is an improvement), but everything else is the same... It's ok? Not that I want to do that or that I accuse any work here to be that. BTW voted yes. Impressive work here :)
I like colors
Joined: 5/9/2005
Posts: 748
I'll emphasise again too that, how Sonic runs are timed, this is a 354 frame improvement. NOT a 3 frame one. Whilst I'm posting, obvious yes vote. Great work Zurggriff, you should be very proud of this run.
Player (36)
Joined: 9/11/2004
Posts: 2623
Wobmiar wrote:
If I understand well, then, if PURELY THEORICALLY I find someone's TAS and find a 1 frame improvement, this frame being a good frame save (when you talk about improvement in gameplay, let's assume this frame is an improvement), but everything else is the same... It's ok? Not that I want to do that or that I accuse any work here to be that.
Yes. If it contains an improvement that turns a 10000 frame movie into a 9999 frame movie, provided the quality of the gameplay is similar, then that improvement should be accepted. For instance, SMB1. This movie contains 17840 frames. This movie contains 17839 frames. If the input is mostly the same, list the other user as a co-author. If you want to be a good guy, just let him/her know about the improvement. He/She might already know about it and might be saving it for a bigger improvement.
Build a man a fire, warm him for a day, Set a man on fire, warm him for the rest of his life.
Spikestuff
They/Them
Editor, Publisher, Expert player (2284)
Joined: 10/12/2011
Posts: 6336
Location: The land down under.
Just a point to point out. If you remove the blank input from the SMB TASes. klmz's is faster by a frame. But both inputs end before touching the Axe, so the input is extended. And just to repoint my point from earlier:
Spikestuff wrote:
Also to point out one of the objectives in the submission it mentions that it Aims for fastest in-game time. Which when you look into it, it's mainly dominated by Sonic TASes.
Which means it's a 354 frame improvement in terms of ingame time not the 3 frames of realtime. It's not that hard to understand.
WebNations/Sabih wrote:
+fsvgm777 never censoring anything.
Disables Comments and Ratings for the YouTube account. Something better for yourself and also others.
marzojr
He/Him
Experienced player (748)
Joined: 9/29/2008
Posts: 964
Location: 🇫🇷 France
Marzo Junior
Joined: 6/6/2004
Posts: 223
Is this the first Sonic 2 submission (with any character) that actually partakes in running up the score during Sky Chase Zone?
Post subject: Sky Chase Zone
Active player (437)
Joined: 11/16/2016
Posts: 34
None of the previous publications of Sonic 2 maximized the score in Sky Chase Zone; I did not check all of the rejected submissions. The high score in Sky Chase Zone is not a TAS only achievement and this score has been matched by several people in real time. Of the ideas I had for going through this stage, high score happened to be my choice. I did note that it had not been in a publication before. Regarding real time versus in-game time, I thought the second bullet in the Objectives clarified the priority but I see how the opening paragraph could cause confusion so I changed it. The real time by itself never mattered. However, when the work in progress that looked like it would never overcome the losses from the Mystic Cave 2 bonus came so close to matching the publication, I was amused that the submitted movie file managed to be just 3 frames faster.