Submission Text Full Submission Page
Super Pitfall is a platforming game well known for glitchiness and overall poor programming.

Game objectives

  • Emulator used: FCEUX 2.2.2
  • Beats the game as fast as possible
  • Abuses programming errors

Comments

This game is pretty poorly programmed, as anyone who has tried to play the game casually can attest.
'Wall Clip': This glitch occurs because a particular memory address ($00D5) is reused for multiple purposes in a frame. One of those purposes is for collision detection. Normally, this byte fails a check that prevents the player from moving forward when walking against a wall. However, it turns out that $00D5 is also changed at an interrupt of some sort. If the interrupt timing is just right, the value will be modified and not changed back before the collision detection check. When this happens the character moves one step into the wall. This is quite random, and I have found no way to consistently make it happen. Only a brute force search could really find the best case as far as I could tell. But it happens often enough to make it a time saver.
This run features several new clips, allowing slow deaths to be avoided.

Other comments

This is my first attempt at using automated re-recording to make a run, and I must say I am pretty happy with the results. This run probably contains more re-records then all my other runs combined, simply because of the blind brute forcing I did to make the clips as fast as possible.
There are a couple of other possible clips as illustrated by Arc, but I have not managed to make them save time over the current ones. Of course, I only tested a small fraction of the incredible number of potential combinations, so maybe if enough cpu time is devoted to the problem more improvements are still possible.
There is also a glitch (presented at a recent AGDQ but known for several years), that warps to the ending screen much faster, however it turns out the true ending state is not obtained this way, since it doesn't start the second world, and therefore not included in this submission.


Joined: 2/25/2006
Posts: 407
Alyosha wrote:
shooting (and the shooting animation) make the clips go much faster, by bout a factor of 2 as far as I can tell, so the shots are definitely needed. I will test that route, interesting idea. @jlun2: good question, I have never tested it, I guess I will throw Harry against a wall for a while and see what happens. In other news, I just successfully clipped through the 3 walls to get to the girl and saved over 6 seconds! Look like there is still more to this game yet!
Good, the less music available to listen to, the better.
Ryzen 3700X, ASUS Crosshair VIII Hero (WiFi) Motherboard, 32GB 3600MHz RAM, MSI Geforce 1070Ti 8GB, Windows 10 Pro x64 http://tasvideos.org/Nach/FranpaAlert.html
Active player (264)
Joined: 8/14/2014
Posts: 188
Location: North Kilttown
I love how through new tech you can eliminate "uses death to save time" as one of the objectives and can add "major glitch abuse".
Somewhat damaged.
Arc
Editor, Experienced player (826)
Joined: 3/8/2004
Posts: 534
Location: Arizona
New discovery: the spade is not necessary. You should be able to save maybe 7-8 seconds by clipping through this wall.
Alyosha
He/Him
Editor, Emulator Coder, Expert player (3821)
Joined: 11/30/2014
Posts: 2829
Location: US
Good thinking! I should have thought of that. Ok I am sending this to gruefood, time to start from scratch with some fresh thinking.
TASVideosGrue
They/Them
Joined: 10/1/2008
Posts: 2785
Location: The dark corners of the TASVideos server
om, nom, nom... blech, salty!