1 / 18
Before installing Kurex AI you should bring your system into a clean state. The points below are not recommendations, they are requirements, and every single one has already caused dozens of support tickets.
Really close all games and anti-cheats before the setup. Right after the installation: reboot before opening Kurex for the first time.
In the background Kurex AI uses CUDA, DirectX and the Visual C++ Runtime. All three must be set up cleanly before the actual installation.
Download the installer directly from Nvidia. Pick Windows 10 or Windows 11 as the target, matching your system. An express install is foolproof.
The official Microsoft package. The important parts are older D3D libraries that many games and capture pipelines still need.
Install the current x64 version. Add x86 if needed. Without this runtime typical DLLs like vcruntime140.dll or msvcp140.dll are missing.
Direct download links for all three components are available in the customer area on our Discord after purchase. That way you can be sure to install the right version.
For the inference engine Kurex AI needs a few extra CUDA libraries that don't ship with the toolkit by default. They are provided as a ZIP and must land in exactly the right place.
Grab the CUDA files archive from the Discord customer area.
Important: don't just open it, actually extract it.
Use this path as the extraction target:
At the end, all .dll files must sit directly inside the bin folder, not in an extra subfolder named after the archive.
If Kurex later fails with "opencv_world*.dll not found" or similar DLL errors, this step almost always wasn't done cleanly.
To keep things tidy you create a dedicated folder for the Kurex loader, all required files and your configurations.
From the customer Discord you get the base package, an additional update file and one extra file.
Grab the Kurex DLL package and keep the .dll files ready — they go into the same Kurex folder as the loader and the other setup files.
Name it e.g. Kurex and copy all base files and DLLs into it.
You can delete hidapi.dll if you are not using an Arduino with Hidra firmware, otherwise leave it.
Inside your Kurex folder, create another folder with the exact name configs. Saved setups will live there later.
Kurex AI works with all common external input devices. Which one you pick depends on your game, your budget and whether you plan a 1-PC, 2-PC or console setup. Pick your setup below and jump straight to the matching guide.
Expand the hardware that fits your setup. Inside you see when it makes sense, what you need and which chapter you continue with. The detailed instructions remain in the sections below.
Dual-PC setups where Kurex AI runs on a separate PC and input is passed over the network.
Single-PC setups where you want a simple external mouse pipe-through.
Setups where you want to separate multiple USB paths cleanly but still switch between PC and console.
Advanced dual-PC setups where game PC, Kurex PC and video signal should be as isolated as possible.
Console setups where mouse/keyboard and a controller share XIM Matrix or Zen.
2-PC and console setups where Kurex AI processes the game image through an external card.
The Kmbox Net is connected via Ethernet and is the most reliable choice for many users. In a 2-PC setup you plug one LAN cable into your gaming PC and the other into the Kurex PC, and you run the setup on the Kurex PC.
Download the matching Kmbox Net driver and extract the archive.
Start WCHUSBNIC.exe as administrator and click Install.
Open the Windows network settings. A new adapter now shows up.
Right-click the new adapter → Properties → select Internet Protocol Version 4 (TCP/IPv4) → Properties. Enter these values:
| Field | Value |
|---|---|
| IP address | 192.168.2.100 |
| Subnet mask | 255.255.255.0 |
| Default gateway | (leave empty) |
Download the Kmbox Net Manufacturer Tool, extract the archive and start KmboxNetTool.exe as administrator. If the window shows lots of question marks, no problem, that's normal.
Set the IP to 192.168.2.188. Port and UUID are printed on your Kmbox display.
Click the big Connect button (green arrow). Once the connection is up, continue with your mouse data.
For the Kmbox to pipe your mouse through, you need its VID and PID. Find them in Windows under Control Panel → Devices and Printers: right-click your mouse → Properties → Hardware → Details → "Hardware IDs".
Type VID and PID into the tool, then click the [VID/PID??] button to apply them.
Connect your mouse to the Kmbox, it should work exactly as before.
You can delete the downloaded Kmbox setup files afterwards, they aren't needed anymore.
If your cursor behaves normally and the loader shows the Kmbox in green, the hardware setup is complete.
The classic Arduino setup with a USB host shield is cheap and fully sufficient for 1-PC use. Requirement: your Arduino is already flashed with an HID firmware (e.g. Hidra).
Use a data cable, not a pure charging cable, otherwise the board won't be recognized correctly.
From now on the mouse runs on the host shield instead of the PC. Leave it plugged in permanently.
Start Kurex and choose Arduino as input. If you use Hidra firmware, also click the keyboard icon and pick Hidra there.
Single PC: Hidra firmware. Dual PC with Arduino: prefer Xenmouse or a comparable firmware made for 2-PC setups.
The Makcu is wired slightly differently depending on the setup. For a pure 1-PC setup it's enough to connect the Makcu and the serial USB ports to your main PC.
In the loader pick Makcu as input afterwards. Detailed diagrams and updates are in the makxd.com Discord.
The M-Kit is the no-compromise variant: complete separation between game PC and Kurex PC, ideally combined with a DMA card (e.g. Phoenix) and a capture card.
There are two ways to get the capture card image into Kurex:
If you want to use Kurex AI on console, you need an XIM Matrix or a Zen, plus a compatible controller that stays connected.
In the Kurex loader you then pick the input matching your concrete hardware (e.g. Makcu).
A capture card makes sure your game image gets from the gaming or console system to the Kurex PC with minimal delay. Look for a card with low latency and support for NV12/YUY2.
Download Kurex AI Loader.exe and save it to your Kurex working folder from step 04 (next to your other setup files).
Always run the loader as administrator. Otherwise permissions for capture and input components are missing.
Once you are logged in to the Kurex loader, three main selectors are available. They define how Kurex "reads" your game and how your input is passed on.
| Game | Recommended model |
|---|---|
| Valorant & other games with player outlines | OUTLINE-1 |
| Fortnite, CS2 | BR-1 |
| Apex Legends | BR-APX |
| Call of Duty | BR-COD |
| All other games | Universal |
The other models work in most cases too, feel free to test which one runs most stably for you.
| Runtime | When to use |
|---|---|
Nvidia FP16 | Modern Nvidia GPUs (RTX 30/40/50 series etc.). |
Nvidia FP32 | Older Nvidia cards where FP16 is unstable. |
AMD | AMD GPUs. |
Alternative | Weak GPU or pure CPU setup. |
Once all three fields are set, click Start.
Click the settings icon in the loader and first carry over your in-game mouse and sensitivity values. Then it's worth testing in a quiet environment, ideally in a training map or range.
If the tracking looks calm and predictable, your setup is ready to play. If problems remain, the next chapter takes over.
Before you open a ticket: 90 % of all cases can be solved with the steps below. If your question isn't answered here, feel free to reach out in the support channel.
Your hardware changed since the last login. Contact support on Discord for an HWID reset. Note: a reset is only available every three days.
Your Windows system time is wrong. Open Settings → Time & Language → Date & Time and turn on automatic sync. Then trigger a manual sync once.
Briefly connect via VPN (e.g. Proton VPN) and try the login again. Once you are logged in, you can disable the VPN.
ipconfig /flushdns.The CUDA files were not extracted into the right folder. Go back to step 03 and make sure all DLLs sit directly inside the CUDA\v12.8\bin folder. For other DLL errors: cleanly reinstall Visual C++ and DirectX from step 02.
MYPC).In a dual-PC setup with Arduino: try Kmbox B+ as the connection mode. In single PC: switch the Hidra setting in the loader to Basic. If aim doesn't respond after start, hit the Reconnect button in the Information tab.
In the Nvidia graphics settings, disable the Background Application FPS limiter.
If your issue isn't listed, open a ticket on Discord, with a screenshot or short video most edge cases are solved in minutes.
These commands help bring an unhealthy Windows back into shape. Always run CMD as administrator.
In the Nvidia Control Panel you can deliberately remove latency. For Kurex and your game set Low Latency Mode to Ultra, Power Management to Maximum Performance and disable VSync both globally and in the game profile.
Via msconfig → Boot → Advanced options you can set the number of CPU cores used to the maximum your CPU supports. This especially helps with sudden FPS drops and stabilizes the AI pipeline latency.
Change one thing at a time and test. That way you immediately notice which step really helps, and which doesn't.
Here are all download, tool and tutorial links that were in the PDF. The important ones are explained in the matching chapters; this list is a complete overview for quick access.
Once you have completed this guide cleanly, Kurex AI runs stably. On updates it's worth quickly reviewing sections 02, 03 and 12.