> 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/arcade/atomiswave.md).

# Atomiswave

Sammy Corporation

<div align="left"><figure><picture><source srcset="https://raw.githubusercontent.com/fabricecaruso/es-theme-carbon/91d85c7849cc550b0cac4e75cb8e0923d3b61b5e/art/logos/atomiswave-w.svg" media="(prefers-color-scheme: dark)"><img src="https://raw.githubusercontent.com/fabricecaruso/es-theme-carbon/52ff37c9e265587d006945a2ba695b5a962b3a3d/art/logos/atomiswave.svg" alt=""></picture><figcaption></figcaption></figure></div>

Arcade - Released: 2003

{% embed url="<https://en.wikipedia.org/wiki/Atomiswave>" %}

## Information

<table data-header-hidden><thead><tr><th width="224"></th><th></th></tr></thead><tbody><tr><td><strong>Emulators</strong></td><td><ul><li>Libretro: flycast</li><li>flycast</li><li>demul</li></ul></td></tr><tr><td><strong>File folder</strong></td><td><span data-gb-custom-inline data-tag="emoji" data-code="1f4c2">📂</span> roms \ <span data-gb-custom-inline data-tag="emoji" data-code="1f4c2">📂</span> atomiswave</td></tr><tr><td><strong>File extension</strong></td><td>.bin .lst .zip .7z</td></tr></tbody></table>

## System Features

<table><thead><tr><th width="256">Retroachievements</th><th width="243">Netplay</th><th>Controller autoconfig</th></tr></thead><tbody><tr><td>lr-flycast: YES<br>Flycast: YES<br>Demul: NO</td><td>NO</td><td>lr-flycast: YES<br>Flycast: YES<br>Demul: YES</td></tr></tbody></table>

## Bios Information

<table><thead><tr><th width="160.55555555555557">bios file</th><th width="155">Folder</th><th>md5</th></tr></thead><tbody><tr><td>awbios.zip</td><td><code>\bios\dc</code></td><td>0ec5ae5b5a5c4959fa8b43fcf8687f7c</td></tr></tbody></table>

{% hint style="info" %}
For Flycast standalone, BIOS file must be placed in `emulators\flycast\data` folder.
{% endhint %}

## Controls

{% hint style="danger" %}
In construction : default RetroArch mapping.
{% endhint %}

## Specific system information

### Service Menu

Some games have a per-game menu for accessing the machine's advanced configuration such as its dip switches, service mode and diagnostic input.

To access the service menu for ATOMISWAVE games, you need first to enable the Service Mode from the RetroBat advanced menu (set it to YES):

<div align="left"><figure><img src="https://i.imgur.com/ztsYbF4.png" alt=""><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="https://i.imgur.com/FcFsHjG.png" alt=""><figcaption></figcaption></figure></div>

Once done, you will be able access the per-game Service Menu by pressing L3 + R3 buttons on the controller.


---

# 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/arcade/atomiswave.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.