SkyAim ProDocs

Aimbot not locking

Work through the list from the top. Nine times out of ten the cause is in the first four items.

Updated Nov 15, 20262 min read
  1. Mouse test moves the cursor?

    Aimbot section → Mouse test. No movement means a hardware or port problem: the MAKCU output cable must go to the game PC and the control port to the radar PC. Fix this before anything else; see MAKCU setup or KMBOX Net.

  2. Is the aimbot enabled?

    The Device aimbot switch at the top of the section must be on, and if you bound Toggle aimbot to a key, the status line must not read Aimbot: off. Press the key once.

  3. Is the aim button right?

    The Aim button must be a button the MAKCU reports (Mouse 4 / Mouse 5 are the usual). Hold it and watch the console for MAKCU hw btn.

  4. Is a target allowed?

    Under Targets, the type you are aiming at must be ticked. Teammates are never targeted. Inside the Aim radius and within Max distance? Turn on Show aim radius on ESP to see the circle.

  5. Is the bone visible?

    With Head selected, a target whose head is hidden but chest is inside the FOV is not admitted; the chest fallback applies only to the selected target. Try Chest once to confirm the rest of the chain works.

  6. Is the data fresh?

    A lock is released when the target's bone data is stale. If the radar frame rate is low or the status shows waits, the DMA link is the limit; close other DMA tools and lower the overlay frame rate.

  7. Is it locking but missing?

    Run Calibration (this PC), make sure Use the game's sensitivity settings is on or the hip / ADS values match the game, and adjust Head aim height (default 0.12). Prediction needs a loaded firearm in hand.

  8. Is it locking the wrong thing?

    Change Target selection (closest to crosshair versus closest player), lower Max distance and raise Smoothing a little; a very low smoothing can overshoot and release.

✓
Compare with a known-good profile

Create a new profile, apply the starting values from the Device aimbot page and test on AI scavs at Factory. If that works, the difference is in your main profile; if it does not, the problem is hardware or calibration.

Still stuck?

Check the FAQ and the launcher message list first. If that does not solve it, send the publisher your newest file from output\Logs (or launcher-update.log for launcher problems).

Open the FAQ