Submission Text Full Submission Page
Here is a TAS of Journey To Silius (NES). It is an improvement of 474 frames (~8 seconds) over the current published run by jlun2 & klmz.

Game objectives

  • Emulator used: FCEUX 2.2.2
  • Aims for fastest time
  • Takes damage to save time
  • Luck manipulation
  • Glitch abuse

Comments

Level 1

Most significant time save in this run is due to a glitch that I found in the level 1 boss fight. If you kill the boss in a specific frame you trigger health and ammo replenishing 256 frames faster than normally and finish the level that much faster. I was quite lucky since this specific frame is only 35 frames away from the most optimal battle I could find thus providing a 221 frames time save. Another significant time save is achieved by using shotgun in levels 1 and 2 instead of handgun saving about 160 frames. (Due to equipping it in level 1 with the cost of 57 frames, the time that shotgun actually saves obviously reflects much more in level 2). (Time saved in level 1 = 239 f)

Level 2

While getting more lag frames with shotgun than handgun, it saves big chunk of time most notably in the mid-level "mini boss" and the end of the level mini boss fights. Switching weapon to homing missile in the boss fight is better, because its slightly faster and its by far the best weapon to use in level 3. (Time saved in level 2 = 156 f)

Level 3

Slightly different strats ends up being mostly just as fast or only tiny bit faster. (Time saved in level 3 = 2 f)

Level 4

A better screen scrolling strategy in one segment saves 20 frames. Better mini boss fight strategy saves 6 frames. (Also 1 frame saved elsewhere, but 2 frames lost by having worse "replenish cycle".) (Time saved in level 4 = 25 f)

Level 5

Shot gun strategy for the final bosses ends up saving lots of time compared to previous homing missile + grenade launcher strat. Time save comes from being able to use shotgun for the ultimate final boss. Luckily the ammo count is perfect for this strat. Final shots have to be delivered with handgun since you would otherwise have to take a hit or you would be too far away to hit with the shotgun well enough. (Time saved in level 5 = 52 f bringing the total amount of time saved in this run to 474 frames.)

Thanks

To previous TASers. Without your effort in the currently published movie, which I greatly used for reference and from which I gained lots of valuable information about some very nice tricks and strats, this run would have certainly turned up to be far away from what it is.

TASVideoAgent
They/Them
Moderator
Joined: 8/3/2004
Posts: 14776
Location: 127.0.0.1
This topic is for the purpose of discussing #5460: Zakem66's NES Journey to Silius in 09:21.82
honorableJay
He/Him
Joined: 8/18/2008
Posts: 104
Location: Albany, NY
https://www.twitch.tv/videos/22646697?t=10m09s There's a glitch with the ship where you can destroy the front on a specific frame to skip the rest of the ship and go straight to the final boss.
Zakem66
He/Him
Player (172)
Joined: 4/25/2014
Posts: 25
Location: Finland
honorableJay wrote:
https://www.twitch.tv/videos/22646697?t=10m09s There's a glitch with the ship where you can destroy the front on a specific frame to skip the rest of the ship and go straight to the final boss.
OMG! Wow. Thats a very nice find. Thanks for letting me know. I'm gonna cancel this and redo the ending. Propably gonna take day or two to test some stuff.
TASVideosGrue
They/Them
Joined: 10/1/2008
Posts: 2728
Location: The dark corners of the TASVideos server
om, nom, nom
Player (150)
Joined: 5/1/2006
Posts: 150
Looks like the trick to the first boss is getting the killing blow while it is moving downward ($4FA == 0xB2) and its y velocity(?) is 243 ($4F5 == 0xF3). Since this game seems to copy everything to temp addresses to do anything with them, those values end up propagating elsewhere and just happen to speed up the transition to the next stage, I guess. The thing with the ship and the final boss probably happens for the same reason, so an input file of that happening might give some clues to getting it on other bosses.
Zakem66
He/Him
Player (172)
Joined: 4/25/2014
Posts: 25
Location: Finland
Scumtron wrote:
Looks like the trick to the first boss is getting the killing blow while it is moving downward ($4FA == 0xB2) and its y velocity(?) is 243 ($45F == 0xF3). Since this game seems to copy everything to temp addresses to do anything with them, those values end up propagating elsewhere and just happen to speed up the transition to the next stage, I guess. The thing with the ship and the final boss probably happens for the same reason, so an input file of that happening might give some clues to getting it on other bosses.
Wow. Thats interesting. I think you might be on to something. I did not put it very accurately in my post, but what I have found is that. There is at least two trigger spots (I have found) in first boss seperated by about 4-5 seconds. The frame that triggers the glitch is "counted" from the point that 2nd phase starts. In other words the copter has been in the exact same position doing the exact same thing when glitch is triggered (that makes your theory (and those memory addresses) very worthwhile to study). If I study the up down movement and the trigger frames of the first and last boss, It should give some answers. If the y position indeed is relevant, then there shouldn't be any possibility to trigger the glitch on level 2-4 bosses I think. Thank you very much for this interesting information.
Player (150)
Joined: 5/1/2006
Posts: 150
I tried and failed to reproduce the trick with ship/final boss. Hard to say which object's properties would trigger it there since, unlike the 1st boss, there are about 4 or 5 of them. And yeah, I actually looked at the other bosses after posting and realized that since they're mostly stationary they wouldn't be likely to make it work.
Zakem66
He/Him
Player (172)
Joined: 4/25/2014
Posts: 25
Location: Finland
The first boss second trigger spot is exactly 200 frames after the first one. And the boss is exactly at the same y position. Finishing blow must be delievered when the boss is at its (visually) lowest point and 11 frames before it starts (visually) ascending. (One cycle = 200 frames) <EDIT> Also the 3rd trigger spot is 200 frames after the second as expected. <EDIT> Time to check the ship now..
Zakem66
He/Him
Player (172)
Joined: 4/25/2014
Posts: 25
Location: Finland
Okay. So I went through the trouble of testing every single frame from the first possible deathblow I managed to do @f#129 (from the beginning of the battle) to the last possible deathblow @f#532 (from the beginning of the battle)(403 tested frames). It turns out like has been suggested elsewhere that the glitch triggers when finishing blow is delivered at the last possible frame. I just wanted to make sure that thats the case so I tested that myself. <EDIT> I'm talking about ship battle just to make sure..<EDIT> I don't think there is need to do more research/testing? (even while not knowing how the glitch actually triggers..)
Player (150)
Joined: 5/1/2006
Posts: 150
Zakem66 wrote:
I don't think there is need to do more research/testing? (even while not knowing how the glitch actually triggers..)
That's up to you. :) I'll go ahead and check out the ship battle now that we know how to trigger it, but I agree that a fuller explanation doesn't seem likely to change much. edit: like you said, killing the bubble on the frame before it moves off screen is all it takes. It'd be nice to have a better explanation, but I don't feel like it's worth the effort here.
Skilled player (1703)
Joined: 9/17/2009
Posts: 4952
Location: ̶C̶a̶n̶a̶d̶a̶ "Kanatah"
Wow nice finds! I haven't checked the input file itself, but still, I'm honestly surprised there's still relatively many improvements possible. Iirc, when I was TASing this, stages 2 and 3 lag reduction was rather tricky, since RNG also needs to be taken account for drops. For instance, from the published run, I could've made it past the first cliff area at stage 2 (the one with the vertically extending enemies) a tiny bit faster, but resulted in worse luck, so I had to abandon it. I'm so glad you managed to soldier on this. :)