> 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/navigation/view-options.md).

# View Options

Configure Game View and apply specific settings for the system

**VIEW OPTIONS** is accessible from the [**Game View**](/navigation/system-view-and-game-view.md#game-view) when pressing **SELECT**.

<div align="left"><figure><img src="https://i.imgur.com/3LAdx3p.png" alt=""><figcaption><p>View Options menu</p></figcaption></figure></div>

This Menu gives access to several options.

### Navigation

* Ability to filter games (by text or other filters)
* Select a random game from the system
* Jump to the game beginning with a specified letter
* Change game sorting

### View Options

* Define the view style (depends on Theme used)
* Customize the Gamelist View
  * Gamelist Style
  * Theme options
  * Gamelist Theme Options
  * Gamelist Options (here you have the option to hide a specific file extension for a system)

### Advanced System Options

* Choose Emulator
* General Settings (Shaders, decoration, Aspect Ratio, Vsync, Controller autoconfiguration...)
* Advanced Settings (Specific settings per core/emulator that are injected to the Emulator by Retrobat)


---

# 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/navigation/view-options.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.