Cronus Zen Mouse & Keyboard Settings: Complete Configuration Guide
Configure Cronus Zen mouse and keyboard profiles, button mappings, HIP and ADS sensitivity, deadzones and ballistic curves, then save and test your setup.
Start with a simple profile and change one setting at a time. Keep a backup of each working configuration so you can compare changes without losing the setup that already feels comfortable.
How mouse and keyboard emulation works
With native mouse input, the game reads a mouse directly. With Zen controller emulation, mouse movement becomes right-stick input and keyboard movement becomes left-stick input. The game still applies its controller deadzone, response curve and maximum turning speed.
This means a faster mouse swipe will not always produce a faster turn once the simulated stick reaches its limit. Match the in-game controller settings to the profile before trying to fix that behaviour with very high mouse sensitivity.
Connect the devices
Select the idle Zen slot before configuring. Use USB devices or supported manufacturer receivers, and keep another mouse available to operate your computer if needed.
| Port | Connection |
|---|---|
| A1 | Required controller for the console setup; follow the dedicated arrangement if using Zen Link. |
| A2 | Keyboard. |
| A3 | Mouse. |
| PROG | Configuration computer running Zen Studio Live. |
| CONSOLE/PC | The console or PC receiving gameplay input. |
Open Mouse & Keyboard Settings
Connect through PROG and allow the browser to access the Zen.
- Open Zen Studio Live in a supported browser and check that the mouse and keyboard are detected.
- Open Mouse & Keyboard Settings. In the current panel, mappings and aiming controls are separate working areas.
- Select the appropriate controller button labels for editing. Changing the displayed icons does not replace the device’s Output Protocol setting.
- Test input in Device Monitor: mouse movement should change RX/RY, and movement keys should change LX/LY.
Import, export and organise .zmk profiles
A .zmk file contains the mouse and keyboard configuration. Use Import to load a compatible profile and Export to keep a copy on your computer. Name it for the game, mouse DPI and in-game settings so you know what it was tuned for.
A downloaded profile is a starting point, not a universal preset. Check its bindings and record the required controller sensitivity and deadzone in the In-Game Settings notes. One .zmk file can be stored on the Zen at a time, so export your current file before replacing it.
HIP, ADS and AUX profiles
These are configurations inside the mouse-and-keyboard profile, not separate script slots.
| Profile | Purpose | Useful first check |
|---|---|---|
| HIP | Normal aiming and movement | Make walking, looking and turning work here first. |
| ADS | Aiming-down-sights configuration | Confirm its activation matches the game’s aim button and hold/toggle behaviour. |
| AUX 1–4 | Additional configurations activated by assigned inputs | Use for a vehicle, inventory or another distinct control state; verify the return to HIP. |
Map buttons and movement keys
Choose bindings that match the game’s controller layout. A keyboard key should trigger the intended controller action, not just a familiar icon.
- Assign primary actions such as fire, aim, jump, crouch, reload and interact.
- Use secondary bindings only where you intentionally want another key to perform the same action.
- In Movement, assign W/A/S/D or your preferred keys to the left-stick directions.
- Assign a Walk key and lower Walk Scale if you want reduced movement while holding it.
- Check diagonal movement and release behaviour. Clear accidental duplicate bindings before tuning aim.
Analog Sim and movement acceleration
Keyboard switches are digital: a key is pressed or released. Analog Sim makes the simulated stick change more gradually instead of immediately jumping to its movement value.
Test starts, stops and changes of direction. Use enough simulation for the response you want without making movement feel slow to begin or slow to stop. Tune this separately from mouse aim settings.
Set sensitivity and X/Y ratio
Choose a fixed mouse DPI and keep the in-game controller settings unchanged while testing. Adjust HIP sensitivity until a comfortable mouse movement produces the turn you expect, then tune ADS with small aiming corrections.
X/Y Ratio changes vertical response relative to horizontal response. Start at 1.00 for equal scaling. If you need a different vertical feel, change the ratio slightly and retest diagonal movement. It is not a substitute for matching the game’s deadzone.
Boost and Smoothness
Boost increases the stick output produced by small mouse movements. Too much can make the first movement jump past a small target, so test it only after the baseline deadzone and sensitivity are working.
Smoothness reduces jitter by averaging movement samples. More smoothing can feel steadier but also less immediate. Start low, compare tracking a moving target with making a fast correction, and keep the lowest amount that solves the visible jitter.
Deadzone X, Deadzone Y and Deadzone Shape
The game ignores stick movement inside its deadzone. The translator’s X and Y deadzone settings compensate so small mouse movements can reach the game. Adjust them gradually: a dead feeling near the centre suggests insufficient compensation, while sudden jumps suggest too much.
Deadzone Shape should match the geometry expected by the game or its documented profile. Test horizontal, vertical and diagonal motion rather than judging only a fast turn. Changing the game’s own deadzone later means you should retest the translator.
Analog Stickize and ballistic curves
Analog Stickize scales the simulated stick output. Keep it at the profile’s baseline while establishing sensitivity and deadzone, then test small changes if needed. It cannot remove the game’s maximum controller turn speed.
A linear ballistic curve applies an even input-to-output relationship. A custom curve can soften low-speed movement and increase output later in the range. Begin with linear, move only a few points at a time and compare the result with the saved baseline. Avoid large jumps between neighbouring points that make aim change abruptly.
Example starting approaches by game type
These are tuning examples, not tested universal values. Keep the game’s own input limits and your mouse DPI in mind.
| Game type | Starting approach | Test before saving |
|---|---|---|
| Fast arena shooter | Linear curve, low smoothing and responsive HIP; tune ADS separately | Quick turns followed by a small correction without overshoot. |
| Tactical shooter | Comfortable HIP, slower ADS feel, equal X/Y ratio to start | Small horizontal and diagonal corrections while aiming. |
| Third-person action | Simple HIP profile and clear interact/menu bindings | Camera movement while walking and using context-sensitive actions. |
| Game with vehicles | Working HIP/ADS first, then an AUX profile for vehicle controls | Entering, controlling and exiting the vehicle without leaving AUX active. |
Save to the Zen and test in game
Exporting a file is a backup action; saving to the device applies the configuration to the Zen.
- Export a named .zmk backup of the configuration you want to keep.
- Use Finalize → Save to Device in the current panel and wait for completion.
- Reconnect the normal gameplay setup and test with no active script first.
- Check movement, aim, fire, ADS activation and each AUX return path in a practice area.
- Add your script only after the basic profile works, then retest for overlapping remaps or stick adjustments.
Common configuration problems
Return to a saved baseline before changing several controls at once.
| Problem | Likely check | Next step |
|---|---|---|
| Mouse or keyboard missing | Device support, cable or USB receiver | Test a basic wired device and check detection before tuning. |
| Tiny movement does nothing | Game deadzone versus translator compensation | Tune X/Y deadzones gradually. |
| Aim jumps on first movement | Too much Boost or deadzone compensation | Reduce one setting and compare with baseline. |
| Aim feels delayed | High smoothing or movement simulation | Reduce the relevant setting and retest. |
| Fast swipes stop increasing turn speed | Game’s controller turn-speed limit | Use a controlled swipe and check the profile’s in-game settings. |
| Changes disappear after reconnect | File exported but not saved to Zen | Use the device-save control and confirm after reconnecting. |
Panel reference and compatible devices
The official Mouse and Keyboard panel reference shows the current controls. If input is missing, check supported devices and the connection and Device Monitor checks before importing another profile.
FAQ
Use supported wired USB devices or their compatible USB receivers. Do not assume generic Bluetooth mouse and keyboard pairing works through the Zen.
The current panel stores one .zmk file on the device at a time. Keep exported files on your computer and use HIP, ADS and AUX configurations inside the active file.
Mouse DPI, game sensitivity, deadzone, response curve and controller turn-speed limits all affect the result. Match the required setup before comparing profile values.
Start with linear. Keep a custom curve only if it improves a specific movement test without making another part of aiming less predictable.
