Almost every “my aimbot does nothing” is one of four things, and none of them are the aim. Here is how to tell which one you have.
Undetected by design · Instant delivery · Trained for Fortnite (stylized characters)
The most common support message in this whole scene is some version of: I installed it, I press start, the app says it is running, and my crosshair does not move. It is almost never the aim engine. It is one of four things underneath it, and they all fail the same way — silently.
This page is the checklist we actually use. It applies whether you run NeyraX or something else, because the driver stack underneath every controller-output aimbot is the same.
Every controller-output aimbot sends its aim to a virtual gamepad. That gamepad is a kernel driver — ViGEmBus. If it is not installed, or a Windows update broke it, the engine crashes the moment it tries to create the pad. The app usually still says “running,” because most launchers never check whether the engine survived.
How to tell: the app looks alive but the crosshair never moves, not even a pixel, in any situation. Fix: reinstall as administrator and restart your PC — drivers do not activate until a reboot. NeyraX now checks this at startup and tells you outright instead of failing quietly.
HidHide hides your real controller so the game sees only the virtual one. Here is the trap: it can be installed, switched on, and still be hiding absolutely nothing — because the configuration only picks up a controller that was plugged in at install time, and it never runs again. That state looks identical to a working setup.
How to tell: the aim feels like it is fighting you, or shakes. Two controllers are steering the same camera. Fix: open HidHide, tick your real controller on the Devices tab, enable device hiding, then unplug and replug the controller. Do not tick the virtual “Xbox 360 Controller” — that is the aimbot’s own output and hiding it kills your aim.
One more thing that trips everyone: HidHide has no Start-menu shortcut. It is installed even when Windows search cannot find it. Open it from inside your aim app.
An AI aimbot is a model plus a loop. If the model was trained on realistic shooters and you are in Fortnite, it will detect late, lose targets mid-fight and produce boxes that jump around. That reads as “bad aim” but it is bad sight.
How to tell: the crosshair drifts toward roughly the right area, then gives up — especially at range or mid-build. Fix: use a model trained on the game you actually play. NeyraX ships a Fortnite-trained model and retrains it on new gameplay every release.
Aim tools keep their settings in a config file the engine re-reads while it runs. If that file gets truncated or half-written, most engines fail open: they quietly fall back to code defaults and never tell you. Your calibration is gone, and so is every safety toggle you turned off.
How to tell: it felt right yesterday and feels wrong today, and you changed nothing. Or it starts doing something you never enabled. Fix: recalibrate, and check whether your tool writes its config on every single slider movement — that is a common way to corrupt it. We hit exactly this bug in NeyraX and fixed it; if your tool fires by itself, this is the first thing to suspect.
Detects enemies at 150+ FPS, any distance, any skin — retrained on real matches every update.
Velocity-gated stabilization kills detection jitter before it hits your crosshair.
External only — no injection, no memory reads. The game sees controller input, nothing else.
Flick to a target and the engine finishes the last pixels. Overshoot-free.
Corrections blend into your own stick input. It amplifies your intent, not replaces it.
Sets up the AI engine, drivers, HidHide and your controller automatically. No terminals.
Launch week: 25% off with code NEYRAX25
Almost always the virtual controller driver (ViGEmBus) missing or broken. Reinstall as administrator, restart the PC. Most apps do not check this and just claim they started.
Usually the game is seeing your real controller and the virtual one at the same time — the cloak is installed but not actually hiding your device. Tick your real controller in HidHide, enable hiding, replug it.
That is normal. HidHide installs no Start-menu shortcut. Open it from inside your aim app, or from its folder in Program Files.
Some engines default a triggerbot to ON in code and only switch it off if their settings file loads. If that file is missing or corrupted, it silently fires. Check your settings file exists and is valid — and use a tool that fails safe instead of fail-on.
With NeyraX, no — the model, engine and interface update themselves in the background. You just open the app.