All known issues will be posted here - be sure to report all bugs and detailed feedback to the correct community channels. Always remember to make sure your Zen is updated to the very latest versions of Beta Firmware and Zen Studio Software.

As of today, the latest versions are:

You will find all current known fixes and workarounds for the above known issues (if and when available), including the most common issues reported to the community and Cronus Support Center.

This error only happens when using a PS5 DualSense controller connect to A1 by USB. It does not affect the DualSense when paired to Zen by Bluetooth.

Workaround: Press the MUTE button on the PS5 DualSense Controller and it will stop the lights flashing. This will be fixed in the next firmware release.

Here's a perfect example of a bug report from our APPROVED BETA TESTERS group, courtesy of awesome Community member and approved Beta Tester, xplota 👍

Correct. This is what happens when you have connected your DualSense controller directly to Cronus Zen A1, connect the Zen directly to the PlayStation 5 without correctly setting up PS4 Speciality Mode or not using it at all, or not enabling PS remote Play. It will seem like it's working for a few minutes, but the controller will 100% disconnect, or any scripts of GamePacks you load will become super laggy and unresponsive.

In a nutshell, you need to follow the correct instructions for PS4 }Speciality or PS Remote Play, both of which bypass this level of security when setup correctly. Everything you need for PS5 begins on this page: Step 3 - Choose Your System > PlayStation 5

Correct. This is what happens when you have connected your DualSense or DualShock 4 controller directly to Cronus Zen A1, and then connected the Zen directly to the PlayStation 5 and try to play PS5 games without using the PS4 Speciality or PS Remote Play methods. This direct to PS5 configuration only works with PS4 games, and many of them may not work at all if you have any memory slots enabled with a GamePack or script.

If you do not correctly setup either of the available PS5 connection methods, you can except the following failed results:

• DualSense controller connected to A1 (with any GamePack or script loaded) will seem to work fine in the PS5 menu, but once you load a PS4 or PS5 game, the outputs will corrupt after a few seconds or minutes and eventually disconnect.
• DualSense controller connected to A1 (no GamePacks or scripts loaded) will seem to work fine after loading either PS4 or PS5 games, but it will fail the security handshake after 8-10 minutes and disconnect.
• DualShock 4 controller connected to A1 (with any GamePack or script loaded) will seem to work fine in the PS5 menu, but once you load a PS4 game the outputs will corrupt after a few seconds or minutes and eventually disconnect. The controller may not work in any PS5 games at all.
• DualShock 4 controller connected to A1 (no GamePacks or scripts loaded) will seem to work fine after loading a PS4 game, but it will fail the security handshake after 8-10 minutes and disconnect. The controller may not work in any PS5 games at all.

This is why there are special methods specific only to the PlayStation which are designed to bypass these security checks, so you can use any compatible controller or mouse and keyboard you like, with any MODs you like, for as long as you like, without any annoying disconnects.

If you experience lag with the official PS Remote Play app, try Chiaki PS Remote Play , a very popular PS Remote Play alternative that is fast and easy to setup. Many community members have also offered the following tips for lag free PS5 gaming:

1. Your console and PS Remote device should both be on the same wired network.
2. If you are using a modern USB-C mobile device, use a USB-C GIGABIT ethernet adapter.
3. Upload speed should be at least 5Mbps - but the higher the better.
4. Ping/Latency is super important. Anything below 20ms is good. Bad ping = 💀
5. Try another device - PS Remote Play may not work well for you on a Mac, but Android Chiaki may be the ticket.

If you have already upgraded your Xbox One controller to 5.13.3143.0 and above, it no longer supports Bluetooth. If it is an Elite S2 it also no longer supports GPC constants for the paddles. If you wish to use your Xbox controller wirelessly with the latest controller firmware, you can still use an Xbox Wireless Adapter.

Xbox Bluetooth model controllers are:

• Xbox One 1708
• Xbox Elite S2 1797
• Xbox Series X/S 1914 (No Zen Bluetooth Support)

If you want to keep Bluetooth support, or keep paddle GPC constants for the Elite S2 1797 controller, DO NOT update the controller's firmware past 4.8.1923.0, or if you have already updated, revert the firmware back to a previous version using your Xbox console. You can find the Revert Xbox Firmware 👈 instructions here.

While Zen supports wired headsets in multiple configurations including crossover, you should know that audio is heavy on CPU cycles.

This isn't a problem if you do not use GamePacks or scripts, but if you are using a powerful GamePack or script, audio may affect its performance by causing the controller to disconnect or introduce lag.

When reporting bugs or need help with a problem, it is important that you first check the known issues above to see if any of the workarounds or solutions work for you.

You should also visit the Troubleshooting section of this guide, where we guide you through the main troubleshooting steps - usually most problems are resolved pretty quickly.

If you have followed the Troubleshooting guide and still have a bug to report or problem you need help with, it's important to include the following information so we can replicate your issue:

And finally, a detailed description of your problem so that it can be replicated. Try not to include details that are not important to your problem. Be as specific as you can because if we're unable to replicate, we're unable to help.