> For the complete documentation index, see [llms.txt](https://8bitmods.gitbook.io/manuals/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://8bitmods.gitbook.io/manuals/bitlink-dc-adapter/using-the-adapter/wheel-and-air-mouse.md).

# Wheel mode and Air mouse

Both features use the adapter's motion sensor. Turning one on turns the other off. They work in 2.4G and wired modes.

## Wheel mode

Tilt the controller like a steering wheel to steer with the analog stick.

Hold **D-pad Down + Start** for 1 second to turn it on or off. The VMU screen shows **WHEEL ON** or **WHEEL OFF**.

## Air mouse

Point the controller at the screen to move a Dreamcast mouse cursor. Hold **D-pad Right + Start** for 1 second to turn it on or off. The VMU screen shows **VIEW ON** or **VIEW OFF**.

| Control                  | Mouse                                |
| ------------------------ | ------------------------------------ |
| A                        | Left button                          |
| B                        | Right button                         |
| X                        | Middle button                        |
| Y, held                  | Freezes the cursor so you can re-aim |
| Analog stick up and down | Scroll wheel                         |

While Air mouse is on, the Dreamcast sees a mouse instead of a controller, so the VMU and rumble are not available. Some games only look for a mouse in port A.

## Changing the combos

Connect to the BitLink DC Dongle's WebUI and open **Mapping > Dreamcast > Combo presses**. You can turn each combo off, choose other buttons, and set the hold time.


---

# 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://8bitmods.gitbook.io/manuals/bitlink-dc-adapter/using-the-adapter/wheel-and-air-mouse.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.