> For the complete documentation index, see [llms.txt](https://docs.openbrush.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrush.app/release-history/v2.1-hotfix.md).

# v2.1 Hotfix

2.1 is a bugfixes only release. We're looking forward to bringing new features to Open Brush soon!

### Fixes:

1. *Enable WMR default controller profile.*
2. Fix saving after deleting a layer.
3. *Fix swapping camera modes when using a Vive controller.*
4. Smoother scrolling on Vive controller touchpads.
5. Fix advanced tools panel overlapping other panels.

### Known Issues:

1. *Sometimes Open Brush fails to launch depending on the specific combinations of user's HMD, controller Type, and OpenXR runtime. We're working on methods to smooth over and resolve these issues, apologies if you're experiencing them! Please get in touch with us so we can help debug your setup.*
2. Can't swap controller handedness by tapping together.

The following issues are pending a bug being fixed in Unity, which we found and reported.

1. *Controller issues with HP Reverb G2.*
2. Difficult to dismiss panels by throwing them away.
3. Deadzone on WMR controller thumbsticks is too sensitive.


---

# 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://docs.openbrush.app/release-history/v2.1-hotfix.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.