Mouse and keyboard on console through the Cronus Zen: setup and honest limits
Cronus Zen mouse and keyboard setup: scripts off, controller on A1, keyboard on A2, mouse on A3, then tune a game profile in Zen Studio Live's M&K panel.
To use a mouse and keyboard on console through the Cronus Zen, turn scripts off, plug the controller into A1, the keyboard into A2 and the mouse into A3, then import and tune a game profile in the Mouse & Keyboard Settings panel. Cronus calls this emulation: the Zen presents the mouse and keyboard to the console as a controller. It works. It is also the feature people are most disappointed by, because they expect PC aiming and get something different. This article sets it up, explains each setting, gives a tuning order, and says what the translation does so you tune it with the right expectations.
What the translation actually does
Cronus's own test shows the mapping: in the Device Monitor, moving the mouse changes the right-stick values (RX/RY) and W, A, S, D change the left-stick values (LX/LY). The console only understands controller reports, so that conversion is the whole story.
| On the mouse or keyboard | What the console receives | Consequence |
|---|---|---|
| Slow mouse movement | Small right-stick deflection | The game's deadzone may swallow it; that is what deadzone compensation lifts it over |
| Fast flick | Stick fully over | The game's maximum turn rate decides how far you turn, not your DPI |
| Mouse still | Stick centred | The game treats it like a resting thumb |
| WASD | Left-stick values | Walk speed comes from the M&K settings, not from how hard you press |
| A key mapped to a face button | That button | Same as a pad press |
The game still applies its own stick response and aim assist. Cronus lists controller aim assist as the first advantage of emulation. Native mouse and keyboard, in the few games that support it, is treated like a PC player without aim assist, and Cronus says it cannot use GamePacks or scripts. Tune in the Zen: Cronus lists sensitivity, smoothing and deadzone tuning, and custom key mapping, among what emulation lets you adjust.
What you need
| Item | Detail |
|---|---|
| Console | Cronus lists PS5 (with Zen Link or the bypass), Xbox Series X/S, Xbox One, PS4 and Switch as supported M&K platforms |
| Controller | On A1, per Cronus's connection order. On Xbox and PS4 it is also the console's AUTH controller; The authentication controller |
| Keyboard | On A2 |
| Mouse | On A3. Cronus says most standard USB devices work even if they are not on its tested lists, and its mice list includes wireless models; its older guide says Bluetooth is not supported |
| Zen Studio Live | The Mouse & Keyboard Settings panel |
| Game profile | Cronus's M&K guide covers importing game-specific profiles; start from one |
| Second set or MK switch | Cronus says you need one or the other to keep using the PC |
Cronus's current guide documents the Mouse & Keyboard Settings panel in Zen Studio Live, the browser-based version of Zen Studio. A profile is a .zmk file, saved to the Zen with Finalize, Save to Device, and Cronus says only one .zmk file can be stored on the Zen at a time. Its connect-and-configure steps still name Zen Studio's Device tab and Tools, Device Monitor.
The settings and what each one does
Cronus documents the panel as six profiles, a Mapping area, Aim Settings (Sensitivity, X/Y Ratio, Boost, Smoothness, Invert Y-Axis), a Translator section (the game deadzone X and Y, deadzone shape and Analog Stickize) and a ballistic curve editor.
| Setting | What it changes | Symptom when wrong |
|---|---|---|
| Game deadzone X and Y (deadzone compensation) | Compensates for the game's own deadzone so the smallest mouse movement already registers | Too low: small movements do nothing. Too high: the crosshair twitches at rest |
| Deadzone shape | The geometry of the deadzone, to match the shape the game uses; Zen Studio Live 1.0.9 named the third shape V-Bias | Diagonals feel faster or slower than straight lines |
| Sensitivity | How far the reticle moves for a given mouse movement | Too low: cannot turn. Too high: overshoots every target |
| X/Y Ratio | Vertical sensitivity relative to horizontal; 1.00 makes them equal | Vertical aim too fast or too slow |
| Ballistic curve | Mouse input against reticle output, plotted from 0 to 10k; a straight diagonal is linear. Firmware 2.3.0 added a high-resolution curve | Fine tracking feels either sluggish or jumpy |
| Boost | Raises the output sent to the stick, so small mouse movements give a stronger reticle movement | Small movements feel weak (too low) or jumpy (too high) |
| Smoothness | Averages consecutive mouse samples to reduce jitter; higher feels steadier but responds more slowly | Jitter (too low) or a floating, delayed feel (too high) |
| Invert Y-Axis | Flips vertical | Obvious |
| Analog Stickize | Scales the simulated stick output, per Cronus | |
| Profiles (six) | HIP, ADS and AUX 1 to 4; Cronus says the AUX profiles are activated with an assigned key or mouse button | The wrong profile makes keys do the wrong thing |
Mapping has four tabs: Primary, Secondary, Movement and Controller. Movement holds the WASD bindings, a walk key with a Walk Scale slider, and Analog Sim, which turns WASD's on-off input into a gradual, stick-like output. Cronus's older guide adds that a mapping can combine controller inputs with mouse or keyboard input.
Step by step
- Scripts off. Press the Zen's right blue memory slot button until the Collective Minds logo shows on the OLED. Cronus's setup starts here so no GamePack or script is active.
- Connect. Controller on A1, keyboard on A2, mouse on A3, and the PROG cable from the Zen to your PC.
- Zen Studio. Open the Device tab and look under Connected Devices. The mouse and keyboard should appear; Cronus says a question mark icon still works, it only means Zen Studio has no icon for that device.
- Device Monitor. Tools, Device Monitor. Move the mouse and watch RX/RY change; press W, A, S, D and watch LX/LY change; try the spacebar and other mapped keys.
- Import the profile for your game (a .zmk file) in Mouse & Keyboard Settings, or start from Defaults. Save it with Finalize, Save to Device.
- Tune in this order. Deadzone compensation until the smallest mouse nudge moves the crosshair. Then sensitivity until a 180 feels right. Then the curve for fine tracking. Then boost, sparingly. Then smoothness only if there is visible jitter.
- Test in a range, not a match. Track a moving target, flick between two targets, strafe with WASD. Return to step 6 for whichever felt wrong.
The honest limits
| Expectation | Reality |
|---|---|
| PC-style raw aim | Cronus's own trade-off for emulation: your input is converted rather than raw |
| DPI sets turn distance | The game's maximum stick turn rate caps every flick; sensitivity past that point adds nothing |
| Invisible to the game | The input pattern is what anti-cheat looks at; a mouse translated into a stick produces movement a thumb cannot. Is the Cronus Zen detectable? applies, and the publishers with published positions name mouse-and-keyboard adapters explicitly |
| Normal matchmaking | Some games change matchmaking or aim assist for mouse and keyboard players; that is game-side and outside the Zen's control |
| Less lag than a pad | Wired M&K is steady, which is what matters; Input lag |
Combining with a script
Cronus's native-versus-emulation table lists M.O.D. and script support under emulation; its older guide names GamePacks, scripts, anti-recoil and rapid fire. Its setup still starts with scripts off, so get the M&K profile right first, then add the script and test the two together. A script that writes the right stick acts on the same stick the mouse is driving; if aim feels wrong only with the script on, ask the script's author whether it is written for M&K. Script slots and memory explains how slots work.
When it does not work at all
| Symptom | Cause | Fix |
|---|---|---|
| Keyboard or mouse missing from Connected Devices | Cable, or a device the Zen does not detect | Wired USB device direct into the Zen; Cronus's supported-devices list; not detected |
| Device shows with a question mark | No icon in Zen Studio | Nothing; Cronus says it still works |
| E3 error code after connecting a mouse | An unsupported mouse, per Cronus's older guide; its current troubleshooting page reads E3 codes as corrupted or missing firmware | Unplug the mouse and replug the USB cable; if the code stays, bootloader recovery |
| Mouse settings disturbed with a keyboard connected | Some keyboards register a second device that the Zen reads as a mouse, per Cronus's keyboard list | Add that device to the Ignore List |
| RX/RY do not move in the Device Monitor | Mouse not read | Reconnect it on A3; try another mouse |
| Devices detected, mouse does nothing in game | A script slot or the wrong layout is active | Select the profile's slot and layout |
| Mouse moves only on big movements | Deadzone compensation too low | Raise it |
| Everything works in the Device Monitor, not in the game | Game-side controller settings, or the wrong layout | Check the game's input settings; return to the first layout |
Frequently asked
- Does mouse and keyboard through the Zen feel like PC?
- No. Cronus calls it emulation: the mouse and keyboard are translated into controller inputs, so the game applies its own stick handling and aim assist. It feels like a very precise controller, not a mouse.
- Do I need a second mouse and keyboard?
- Cronus says so, or an MK switch. Once connected to the Zen they work as a controller and no longer control the PC unless you switch them back manually.
- Which port does each device go in?
- Cronus's connection order is controller on A1, keyboard on A2 and mouse on A3, with the PROG cable to the PC for setup.
- Why does my mouse feel floaty or laggy?
- Usually the M&K settings: deadzone compensation, the ballistic curve or smoothing. Start from the game's profile and tune in Zen Studio Live. Cronus's older supported-mice list also notes PMW3360-sensor mice are reported to smooth above 2000 DPI.
- What DPI should I set the mouse to?
- Cronus gives no single figure. Its older supported-mice list says PMW3360-sensor mice are reported to smooth above 2000 DPI and suggests trying lower values. Pick a moderate setting, leave it, and tune in the Zen.
- Can I run an anti-recoil script and mouse and keyboard at once?
- Cronus's native-versus-emulation table lists M.O.D. and script support under emulation, and its older guide names anti-recoil among them. A script that writes the right stick acts on the stick the mouse drives, so test the two together.
Something on this page wrong or out of date? Report a correction