> 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/tutorials/know-issues-and-fixes.md).

# Know issues & fixes

This section is constantly updated with official fixes provided by the Team for specific issues raised by users in our official support channels.

{% hint style="danger" %}
These fixes are only compatible with the latest version of RetroBat, it might brake old versions.
{% endhint %}

## Clean es\_input file

If your controller settings become messed-up and you need a clean start, here is a `es_input.cfg` file that you can copy in your `retrobat\emulationstation\.emulationstation` folder.

It contains only standard keyboard settings, you will have to perform again your controller configuration.

{% file src="/files/HxxSWarLahr7SHkkraUz" %}

## Graphical issues in RetroBat interface

If you own a GPU that is old and not compatible with latest OpenGL versions, it is possible that some rendering effects will not work and glitch or totally crash RetroBat.

To fix this issue, it is possible to force RetroBat interface to use OpenGL 2.1 compatible renderer.

Open the **retrobat.ini** file that is found in the root folder of your RetroBat installation and set the following value to 1:

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

Save the file and run RetroBat.

This setting is also available from BatGui:

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


---

# 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/tutorials/know-issues-and-fixes.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.