> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/changelogs/archive/changelog-22.md).

# Changelog (22)

{% hint style="info" %}
Newest first. See also Changelog [2026](/changelogs/changelog-26.md), [2025](/changelogs/archive/changelog-25.md), [2024](/changelogs/archive/changelog-24.md) and [2023](/changelogs/archive/changelog-23.md).
{% endhint %}

### <i class="fa-microchip">:microchip:</i> Cronus Zen™ firmware <a href="#firmware" id="firmware"></a>

<details open>

<summary><strong>v2.1.0 Beta.43</strong> — November 10, 2022</summary>

**Fixed**

* Xbox® Wireless Adapter bug

</details>

<details>

<summary><strong>v2.1.0 Beta.41</strong> — November 2, 2022</summary>

**Fixed**

* Back button issue

</details>

<details>

<summary><strong>v2.1.0 Beta.35</strong> — July 12, 2022</summary>

**Added**

* `get_ipolar(POLAR, RADIUS/ANGLE)`

**Fixed**

* `get_polar`
* Police lights bug
* Bug in `stickize` for analog indexes
* Various minor fixes

</details>

<details>

<summary><strong>v2.1.0 Beta.22</strong> — May 2, 2022</summary>

**Added**

* Support for PS5® DualSense™ volume control
* `GPC_OP_SWITCH` in the interpreter
* Bluetooth® Clear function — see the Device tab in Zen Studio

**Fixed**

* Elite Series 2 paddles mapped with the Xbox® now work with the new controller firmware
* PS5® DualSense™ mic in crossover
* A PS5® DualSense™ in A2/A3 with no headset would not pull audio from a DualShock®4 v2 in A1 with a headset
* A DualShock®4 over Bluetooth® always switching the Switch emulator to audio mode even with no headset
* Build & Run issue
* `GPC_OP_GPOLAR` now works correctly
* `GPC_OP_GRUMBLE` now works correctly

**Improved**

* Boosted Xbox® One audio volume to DualShock®4 and DualSense™ controllers

{% hint style="warning" %}
With the new Elite Series 2 controller firmware, GPC scripts can no longer control the paddles independently. To keep using GPC scripting for the paddles, revert the Elite Series 2 controller firmware to 4.8.1908.0.
{% endhint %}

</details>

<details>

<summary><strong>v2.1.0 Beta.16</strong> — February 25, 2022</summary>

**Changed**

* GPC errors no longer display `E2XXX` error codes. You are now returned to slot 0, where the error message is displayed. The Zen no longer crashes, and you can continue playing without resetting

**Fixed**

* Xbox® One Share button spamming when using mouse and keyboard

**Improved**

* General stability

</details>

<details>

<summary><strong>v2.1.0 Beta.6</strong> — February 11, 2022</summary>

**Added**

* `ResetDevice` command
* Navcon and Joy-Con Left activation for the mouse and keyboard config

**Fixed**

* `random(min, max)` now also works when called as `random(max, min)`
* Joy-Con Left not working with mouse and keyboard over Bluetooth®
* `brtime` being capped to `INT16_MAX`

**Improved**

* Stability

</details>

<details>

<summary><strong>v2.1.0 Beta.1</strong> — February 7, 2022</summary>

**Added**

* Official PS Remote Play support (PS5® and PS4®)
* New 32-bit GPC interpreter
* Support for the PowerA Fusion Pro 2 Xbox Series X|S® controller
* Support for the PowerA Spectra Xbox Series X|S® controller
* Support for the Razer Wolverine V2 Xbox Series X|S® controller
* Path to rumble on Nintendo Switch® controllers from the interpreter
* Toggle to activate mouse and keyboard profiles
* PS5® DualSense™ adaptive triggers support with official PS Remote Play
* Xbox® One Share button is now blocked for a non-1914 controller

**Fixed**

* Several Xbox® One controller issues
* DualShock®4 audio is now supported over Bluetooth®
* Xbox® One audio on Nintendo Switch®

**Improved**

* Support for 2-channel mics on the PS4®
* Mouse and keyboard detection

</details>


---

# 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://guide.cronuszen.com/changelogs/archive/changelog-22.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.