> 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/mouse-and-keyboard/native-vs-emulation.md).

# Native vs Emulation

Understanding the difference between native mouse and keyboard support and mouse and keyboard emulation is essential for knowing how your inputs are handled in-game.

***

### <i class="fa-arrow-right-arrow-left">:arrow-right-arrow-left:</i> The difference <a href="#difference" id="difference"></a>

**Native** means the game accepts mouse and keyboard input directly. Your input goes straight from the mouse and keyboard into the PC or console.

**Emulation** means your mouse and keyboard are translated into controller inputs. Your input goes into the Cronus Zen™ first, and from there into the PC or console.

***

### <i class="fa-circle-question">:circle-question:</i> Why emulation is needed <a href="#why" id="why"></a>

Most console games do not support native mouse and keyboard input. Emulation gets around this by making the console see your mouse and keyboard as a standard controller.

***

### <i class="fa-scale-balanced">:scale-balanced:</i> Which one to use <a href="#comparison" id="comparison"></a>

<table data-search="false"><thead><tr><th></th><th align="center">Native</th><th align="center">Emulation</th></tr></thead><tbody><tr><td>Aim assist</td><td align="center"><mark style="color:red;"><strong>No</strong></mark></td><td align="center"><mark style="color:green;"><strong>Yes</strong></mark></td></tr><tr><td>Works in any game</td><td align="center"><mark style="color:red;"><strong>No</strong></mark> — select titles only</td><td align="center"><mark style="color:green;"><strong>Yes</strong></mark></td></tr><tr><td>M.O.D. and script support</td><td align="center"><mark style="color:red;"><strong>No</strong></mark></td><td align="center"><mark style="color:green;"><strong>Yes</strong></mark></td></tr><tr><td>Sensitivity, smoothing, deadzone tuning</td><td align="center"><mark style="color:red;"><strong>No</strong></mark></td><td align="center"><mark style="color:green;"><strong>Yes</strong></mark></td></tr><tr><td>Custom key mapping</td><td align="center"><mark style="color:red;"><strong>No</strong></mark></td><td align="center"><mark style="color:green;"><strong>Yes</strong></mark></td></tr><tr><td>Raw, unconverted input</td><td align="center"><mark style="color:green;"><strong>Yes</strong></mark></td><td align="center"><mark style="color:red;"><strong>No</strong></mark></td></tr><tr><td>Setup required</td><td align="center"><mark style="color:green;"><strong>None</strong></mark></td><td align="center">Zen Studio, profile import, and tuning</td></tr></tbody></table>

#### Native <a href="#native" id="native"></a>

Input goes directly to the game, with nothing to set up. But games treat you as a PC player, so there is no aim assist, only select titles support it, and scripts cannot be used.

#### Emulation <a href="#emulation" id="emulation"></a>

Works in every game, keeps controller aim assist, and supports scripts, custom mapping, and detailed tuning. The trade-off is that your input is converted rather than raw, and it takes an initial setup in Zen Studio.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.cronuszen.com/mouse-and-keyboard/native-vs-emulation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.