> For the complete documentation index, see [llms.txt](https://wiki.retrobat.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.retrobat.org/systems-and-emulators/supported-game-systems/others/cannonball.md).

# Cannonball

OutRun port

<div align="left"><figure><img src="https://990680527-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FexdzL60ZuqPLldz2AYta%2Fuploads%2FpYKQntCzKqT4afwqbZ6S%2Fimage.png?alt=media&amp;token=691e54e5-49cb-4498-bcee-92b0da74308a" alt="" width="563"><figcaption></figcaption></figure></div>

## Overview

**OutRun** (Sega, 1986) is an arcade racing game: a Ferrari, a passenger and branching roads to the finish line.

RetroBat runs it with the **Cannonball** libretro core, an engine that recreates the arcade game: high resolution, widescreen, 60 frames per second.

The game ROM is not provided: you need the OutRun ROM (revision B) from the MAME romset.

{% embed url="<https://docs.libretro.com/library/cannonball/>" %}

## At a glance

<table><thead><tr><th width="246.5"></th><th></th></tr></thead><tbody><tr><td><strong>Games folder</strong></td><td><code>roms\cannonball</code></td></tr><tr><td><strong>Extensions</strong></td><td>.game</td></tr><tr><td><strong>Default emulator</strong></td><td>libretro: cannonball</td></tr><tr><td><strong>BIOS</strong></td><td>None (OutRun ROM to provide)</td></tr><tr><td><strong>Controller setup</strong></td><td>Automatic</td></tr><tr><td><strong>Save states</strong></td><td>No</td></tr><tr><td><strong>RetroAchievements</strong></td><td>No</td></tr><tr><td><strong>Netplay</strong></td><td>No</td></tr><tr><td><strong>Light guns</strong></td><td>—</td></tr><tr><td><strong>Wheels</strong></td><td>—</td></tr><tr><td><strong>Optional BIOS</strong></td><td>—</td></tr></tbody></table>

## Which game format?

Extract `outrun.zip` (OutRun revision B, MAME romset) to `roms\cannonball`, then create an empty `CannonBall.game` file in the same folder:

<div align="left"><figure><img src="https://990680527-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FexdzL60ZuqPLldz2AYta%2Fuploads%2FV6KAsrPH9mSQi85dORAG%2Fimage.png?alt=media&amp;token=a357c612-8463-40f6-92da-088ce07f7056" alt=""><figcaption></figcaption></figure></div>

## Controls

### Automatic configuration

<table><thead><tr><th width="229">RetroBat controller</th><th>Action</th></tr></thead><tbody><tr><td>D-pad, left stick</td><td>Steer</td></tr><tr><td>SOUTH</td><td>Accelerate</td></tr><tr><td>WEST</td><td>Brake</td></tr><tr><td>R2 / L2</td><td>Analog accelerator / brake</td></tr><tr><td>EAST / NORTH</td><td>Gear up / down (<strong>GEARS MODE</strong> on MANUAL 2 BUTTONS)</td></tr><tr><td>L1</td><td>Change view</td></tr><tr><td>R1</td><td>Back to menu</td></tr><tr><td>SELECT</td><td>Coin</td></tr><tr><td>START</td><td>Start</td></tr></tbody></table>

**CONTROLS > GEARS MODE**: AUTOMATIC (default), MANUAL, MANUAL CABINET or MANUAL 2 BUTTONS.

### Hotkeys

RetroArch hotkeys. See the [**Hotkeys**](https://wiki.retrobat.org/navigation/hotkeys.md) page.

## Folders

<table><thead><tr><th width="252.75">Content</th><th>Folder</th></tr></thead><tbody><tr><td>ROM and launch file</td><td><code>roms\cannonball</code></td></tr></tbody></table>

## Options

**VIDEO > HIGH RESOLUTION** and **WIDESCREEN** (enabled by default), **CONTROLS > ANALOG CONTROLS**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.retrobat.org/systems-and-emulators/supported-game-systems/others/cannonball.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
