Cronus Zen Output Protocol Settings Explained
Choose the correct Cronus Zen Output Protocol for Xbox, PlayStation, Nintendo Switch and PC, and fix a controller the console will not recognise.
Output Protocol controls the controller identity and input format sent from the Zen to the console or PC. Choose it for the receiving system, not simply for the controller in your hands.
Input controller and output controller are different
A crossover setup can accept a PlayStation controller while sending Xbox-format input to an Xbox console. The source buttons are translated into the selected output format. Selecting PlayStation output just because you are holding a DualSense would be the wrong choice in that example.
Protocol selection also does not supply authentication. A console may still require its supported authentication controller or the correct PS5 connection method.
Where to change Output Protocol
Connect the Zen to your configuration computer using PROG and open the compatible Zen Studio interface.
- Open the Device panel or device settings and locate Emulator Output Protocol.
- Note the existing selection before changing it. Labels can differ slightly between Studio versions.
- Select the protocol for the system connected to the rear CONSOLE/PC port.
- Apply or save the change if the interface asks. Allow any device restart to finish, then reopen the panel to confirm the setting was retained.
Platform reference
These are the protocol labels used by the official setup references. PS5 needs its dedicated connection procedure; there is no universal dropdown change that replaces it.
| Platform | Protocol or setup to use | Common mistake |
|---|---|---|
| Xbox Series X|S | Xbox One X/S, also written Xbox One X|S | Looking for a separate Series-only option or selecting the playing controller’s brand. |
| Xbox One / One S / One X | Xbox One X/S | Using Xbox 360 output because both are Xbox controllers. |
| Nintendo Switch | Nintendo Switch | Omitting Pro Controller Wired Communication in the console settings. |
| PlayStation 4 | PlayStation 4/5 in interfaces using that combined label | Assuming the combined label completes PS5 authentication as well. |
| PlayStation 5 | Follow the selected PS5 / Zen Link Native Mode procedure | Changing only the protocol while leaving console communication or Link setup incomplete. |
| PC — most Xbox-style gamepad games | Xbox-compatible / XInput output, commonly Xbox 360 in classic Studio | Selecting a format the game does not support. |
| PC — another supported controller interface | The mode required by the application; PC/Mobile where its instructions specify it | Treating PC/Mobile as a universal fix for every Windows game. |
When Auto is useful
If your interface offers Auto, it allows automatic selection for supported connections. Leave a working Auto configuration alone unless your console’s setup instructions require a specific mode.
Choose a manual protocol when detection is wrong, when testing a connection, or when the platform guide explicitly specifies one. Auto does not remove the need for authentication, a data cable or compatible hardware.
PS5 depends on the connection method
For Zen Link Native Mode, prepare Link and the console together, including Use USB Cable on PS5. Older Remote Play instructions and current Native Mode instructions are not interchangeable.
Follow Zen Link setup and troubleshooting for that method. Avoid enabling unrelated speciality or Remote Play options from an older guide unless they apply to your actual setup.
PC games and crossover controllers
Check whether the game supports Xbox/XInput input, PlayStation input or another controller interface. Start with the game’s documented controller support, then test the selected Zen output in Windows before opening the game.
If Windows sees one controller but the game sees two, check Steam Input or other remapping software before changing the Zen again. Keep only the translation layers your game needs for the test. A protocol change may also alter button prompts without changing the physical controller.
Symptoms of the wrong output setup
These symptoms can also be caused by a cable or authentication fault. Use Device Monitor to distinguish them.
| Symptom | Check first | Then test |
|---|---|---|
| Controller detected by Zen, ignored by console | Protocol and AUTH device | Console menu with no active script. |
| Works in Windows, ignored by one game | Gamepad format expected by that game | In-game controller selection and remapping software. |
| Wrong button prompts | Selected output identity | Whether the controls themselves are actually incorrect. |
| Switch receives no input | Nintendo Switch output and wired communication setting | Powered dock and console cable. |
| PS5 disconnects despite PlayStation output | Complete PS5 connection method | Link status, USB communication and controller connection. |
Save, reconnect and test
Confirm one configuration before adding mods or wireless devices.
- Reopen device settings and check the selected output protocol.
- Select the idle slot and verify buttons in Device Monitor.
- Disconnect PROG when configuration is complete, then reconnect the normal console or gaming-PC wiring.
- Test navigation, confirm/cancel, both sticks and triggers. Only then select your script slot.
Protocol reference
The official USB setup table confirms the Xbox, PlayStation 4 and Switch labels. The Device panel reference explains output identity and authentication behaviour in the classic interface.
FAQ
That is the Xbox-family output label used in the documented setup. It is not restricted to the older Xbox One X and One S consoles.
No. It changes how the Zen presents controller output to the receiving system.
Yes, if the console or game does not accept the output. Confirm normal controls with no script active before troubleshooting individual mods.