Submission #5602: Noxxa's Uzebox Joyrider in 01:40.07

(Link to video)
BizHawk 2.1.0
Submitted by Noxxa on 7/16/2017 2:20:43 PM
Submission Comments

Uzebox Joyrider in 01:40.07 by Noxxa

Game objectives

  • Emulator used: BizHawk 2.0.1 git interim (syncs on BizHawk 2.1.0)
  • Clear Story Mode

About the system and game

The Uzebox has a wiki, describing what it is:
"The Uzebox is a retro-minimalist homebrew game console. It is based on an AVR 8-bit general purpose microcontroller made by Atmel. The particularity of the system is that it's based on an interrupt driven kernel and has no frame buffer. Functions such as video sync generation, tile rendering and music mixing is done realtime by a background task so games can easily be developed in C. The design goal was to be as simple as possible yet have good enough sound and graphics while leaving enough resources to implement interesting games. Emphasis was put on making it easy and fun to assemble and program for any hobbyists. The final design contains only two chips: an ATmega644 and an AD725 RGB-to-NTSC converter."
The Uzebox wiki also has a page for this game.
Joyrider is a topdown driving game for the Uzebox, in the style of the classic Grand Theft Auto and Driver games. It was created by James Howard (jhhoward) for the Uzebox Coding Competition 2014, where it won 1st place.
Like the classic GTAs and Drivers, it features a city to drive around in, with several things to do; free roaming, doing missions or participating in police chases for instance. The game has a story mode with three missions, and arcade/multiplayer modes with other activities.
This TAS goes through the story mode missions.

Run notes

General driving notes

  • The game is limited to 16 driving angles. Because of this, it's not always possible to make perfect beelines towards the next turn, although I still aim to go for the straightest and shortest lines possible. The car accelerates relatively quickly, making this an efficient method of driving.
  • When an objective building is reached, the car automatically stops, and usually a brief cutscene plays with the player getting out of the car, entering the building, and returning to the car. (Sometimes other characters are involved as well). To save time, it's usually best to part as close to the door as possible, so that less time is spent on the walking cutscenes.
  • Car collisions generally don't do much to car velocity, but they do mess things up just enough that there's a slight deceleration/speed loss; therefore, car collisions are avoided throughout the run.
  • Running over pedestrians or colliding with cars randomly gets you a wanted level. With some luck manipulation, this is pretty easily avoidable.

Mission 1 - Bank Job

  • First objective is to pick up a crew of 3 people to do the bank job with. The parking layout makes it easy to get the car right next to the door; this easily saves up to a second compared to going directly for the marked objective point.
  • Getting a good parking point for the bank was significantly harder, as there is not as much room, and the car also needs to not be turned so much that it can't easily exit the front of the building, and needs to be able to go south fast enough for the next objective.
  • At the safehouse, I drive past the objective point on the right side, in order to get closer to the door. This again saves around a second (possibly even more) compared to parking on the objective point itself. Mission complete!

Mission 2 - Collector

  • The building where the payment must be collected has another annnoyingly placed objective point. I can't really reach the door without going in a full 180 degree spin (which would lose a lot of time for obvious reasons), so I end up driving just south of it and then coming inside from there. This is still a fair distance away from the door, but at least no horizontal walking is required, and the car can still easily get away after this.
  • The next building is similarly laid out like the first, but because I enter from a southwards angle this time it is a lot more viable to go around the objective point in order to park right in front of the door.
  • The second collectee goes to his car and escapes, and has to be chased. This car goes on a predetermined path, and the fastest way to get it to reach its destination is just to let it do its thing and not have anything touch it or get in its way. Since I have nothing else to do, I play around a bit, going in different directions (close to a mission failure by letting the car "escape"), driving in front of the car rather than properly chasing it, or driving in a circle, and so on.
  • When the collectee enters his destination building, an objective point appears. Since I had time to reach here in advance, I set up such that I'm on the very top right point of the objective point, to minimize driving time for the next target and minimize the distance to the door for cutscene speed.
  • Since the next missions relocates the player elsewhere, I didn't need to care about how to leave the car in front of the boss' building; just making sure to reach it and enter the door as fast as possible.

Mission 3 - Street Race

  • A simple mission; just follow directions until a lap is completed, and do so before the green car does.
  • I steer a bit at the beginning to avoid having a car bump into me shortly into the race.
  • Since I still need to advance the "continue" menu item after the mission ends, I don't have any end-of-input shenanigans to do here; just end the race as soon as possible so the continue prompt can be pressed as soon as possible. This brings the game back to the main menu, ending the run.

Final notes

Thanks to natt for screwing around with an UZEM core in BizHawk, resulting in this.
Thanks for watching!

Fog: Judging.
Fog: A poor man's GTA, the run was pretty boring and not really entertaining. The technical qualities are sound, as usual.
Accepting for Vault.
fsvgm777: Processing.
Last Edited by adelikat on 10/23/2023 3:32 PM
Page History Latest diff List referrers