Tool-assisted game movies
When human skills are just not enough

Submission #6148: jmosx36's SNES Top Gear in 1:27:34.66

Console: Super NES
Game name: Top Gear
Game version: USA
ROM filename: Top Gear (USA).sfc
Emulator: Snes9x 1.55
Movie length: 1:27:34.66
FrameCount: 315799
Re-record count: 8950
Author's real name: Juan Manuel
Author's nickname: jmosx36
Submitter: jmosx36
Submitted at: 2018-11-12 02:35:18
Text last edited at: 2018-12-24 22:22:47
Text last edited by: Stovent
Download: Download (25809 bytes)
Status: published
Click to view the actual publication
Submission instructions
Discuss this submission (also rating / voting)
List all submissions by this submitter
List pages on this site that refer to this submission
View submission text history
Back to the submission list
Author's comments and explanations:
Temp edited encode

The game

Top Gear is a racing video game for the Super NES, published by Kemco and developed by Gremlin Graphics in 1992. The objective of the game is to become the fastest driver in the world by racing other drivers across several nations. The franchise is unrelated to the TV series of the same name.
It marks the first game in the Top Gear racing game franchise, and it is one of the first racing games to be released on the Super NES. This game and its next two sequels were created by the same developers as the similar Lotus series of games released earlier on the Commodore Amiga and Sega Mega Drive systems.
The game became very popular in Brazil. It inspired Brazilian company Aquiris Game Studio to create Horizon Chase, whose soundtrack was scored by Top Gear composer Barry Leitch.

Info from Wikipedia

Explanation of the run cup by cup


In the planning of the run, i had the idea of start with only 1 player route at San Francisco, but in the middle of the run i re-considered to start the 1 player route in Los Angeles, but it was too late

South America

In Rio, i used one nitro from the player 2 "every" lap, not in a row like other tracks
In Machu Picchu, I understood that speed is lost more slowly if only the accelerator is released, and that means that player 2 is equally efficient on this track
I not reached the 400Km/h in Chichen Itza, and it was in this track when i started to torment an AI with the other player, that is noisy
I had two routes for Rain Forest, I needed to empty the fuel tank and was not possible if i use the nitros from the player 2 to push tpe player 1


Literally i had to remake the entire cup 4 times because a bad route selection
In hiroshima, i decided to push the player 1 with a lot of impulse in the pits
In yokohama i lost 3-4 frames because some of the opponents started in different order (of my last run), and it's not pushed me at the same time
In this video i had a problem in kyoto (bad luck), i had to use a nitro one lap earlier than my planned route to avoid an opponent


Munich looks slowly because i had to use the player 2 because i needed the player 1 to Cologne


Really nothing so interesting to post


Nice, France was difficult for the short space between the car and the obstacle. See the screenshots


In florence i had a problem to empty the fuel tank, if i wait for the player 2 to push him i will not reach to empty the fuel tank before the player 2 finishes the race

United Kingdom

I got 4:42.75 on London The fastest time ever The song did not reach to cover the whole track, I had to use another fill song
I had the same problem of the fuel tank in sheffield and loch ness

Track location My old run Sum of time This run Sum of time
Las vegas 00:50,8 0:00:50,85 00:50,8 0:00:50,76
Los Angeles 01:35,2 0:02:26,05 01:32,4 0:02:23,17
New York 01:35,9 0:04:01,93 01:35,7 0:03:58,88
San Francisco 02:53,3 0:06:55,21 02:46,6 0:06:45,53
Rio 03:55,1 0:10:50,34 03:36,3 0:10:21,79
Machu Picchu 01:35,7 0:12:26,09 01:33,8 0:11:55,55
Chichen Itza 02:42,5 0:15:08,59 02:39,1 0:14:34,63
Rain Forest 01:52,9 0:17:01,45 01:42,6 0:16:17,21
Tokyo 03:58,5 0:20:59,95 03:51,2 0:20:08,41
Hiroshima 02:53,6 0:23:53,58 02:43,7 0:22:52,09
Yokohama 01:26,2 0:25:19,76 01:21,5 0:24:13,59
Kyoto 04:07,7 0:29:27,42 03:47,7 0:28:01,29
Munich 04:25,8 0:33:53,18 04:09,7 0:29:45,59
Cologne 01:58,6 0:37:03,09 01:44,3 0:33:55,34
Black Forest 03:09,9 0:39:01,74 03:05,6 0:37:00,94
Frankfurt 04:12,7 0:43:14,44 03:51,9 0:40:52,82
Stockholm 01:35,4 0:44:49,87 01:28,2 0:42:21,03
Copenhagen 01:40,4 0:46:30,27 01:33,0 0:43:54,04
Helsinki 01:24,8 0:47:55,02 01:18,6 0:45:12,65
Oslo 01:36,2 0:49:31,22 01:33,1 0:46:45,78
Paris 01:56,1 0:51:27,30 01:41,8 0:48:27,56
Nice 03:41,6 0:55:08,88 03:29,7 0:51:57,22
Bordeaux 03:29,0 0:58:37,86 03:13,8 0:55:11,03
Monaco 01:53,1 1:00:30,97 01:47,1 0:56:58,08
Pisa 01:46,0 1:02:16,97 01:38,8 0:58:36,86
Rome 03:37,2 1:05:54,20 03:24,6 1:02:01,51
Sicily 01:55,0 1:07:49,25 01:40,2 1:03:41,74
Florence 01:36,6 1:09:25,80 01:27,7 1:05:09,47
London 04:58,4 1:14:24,20 04:42,8 1:09:52,22
Sheffield 01:25,6 1:15:49,75 01:19,0 1:11:11,25
Loch Ness 01:40,6 1:17:30,30 01:35,3 1:12:46,53

I didn't count the time of the final race because was slowed down by the input end

Some Screenshots

my english is terrible

feos: Upon another review, I finally decided to accept this movie. Things that look suspicious don't lead to easy improvements due to significant complexity of routing. Even if some of those places have actual flaws, and tightening them up could lead to significant improvements (possibly), implementing those improvements won't be easy, as I said. This movie is already so much better than the previous attempt, and it beats my test times.

Yet, even though this time it's way more varied and intense, it's still way too long and monotonous to keep the average viewer entertained the whole time. Accepting to Vault.

Stovent: Processing...

Similar submissions (by title and categories where applicable):