FAQ & error fixes
Start here when something does not work. Each answer says what the symptom means and the one thing to try first.
Launcher and license#
“License unavailable, expired, or assigned to another device.” The key is wrong, has expired, was revoked, or is bound to a different PC. Keys bind to the first PC that signs in; ask the publisher for a hardware reset if you changed machines. Full list of messages: Launcher messages.
“Connection error” or “SSL connection could not be established.” The server address is wrong, the server is down, or its certificate is not trusted on your PC. Re-check the address under Connection settings. Never install a certificate or disable checks to get past this; tell the publisher.
“Bundle integrity check failed.” The download did not match the publisher's signature. Nothing was launched. Try again; if it repeats, the server copy is being updated or your connection alters traffic (proxy, antivirus HTTPS scanning).
The launcher closes at once. Very old launchers (1.0) still need .NET 9. Ask the publisher for the current launcher ZIP: it includes its own .NET. Run the current launcher from a folder you own (not Program Files), with all its files together.
Radar#
No map after the raid loads. Click Restart radar. If it never appears on this PC, delete mmap.txt (a copied one from another PC does not work) and start again. First start after that takes a few minutes.
Markers are offset on one map. Map setup for that map. On every map at once: restart the radar and check the game was not just updated.
Extracts missing after a transit. Wait up to two minutes; the radar retries by itself.
Wrong floor shown on Interchange, Labs or Icebreaker. Layers switch by your height; stairs and ladders take a moment. If it stays wrong, note the map and the Y height from the map label and send it with your log.
Players show no level or K/D. Profile lookups are off or have no API key (Radar → Player data source).
Loot and filters#
Loot list is empty. Check Show loot and the Hide below value in Loot; a high threshold hides everything early in a wipe.
No filter groups. Import the bundled presets.
Prices look wrong. Switch Price source between Flea market and Trader; flea prices do not exist for items that cannot be listed.
ESP overlay#
The overlay opens on the wrong monitor. ESP → Overlay display, and Radar → Game monitor. Both must point at the fuser's monitor.
Boxes are next to players, not on them. Radar → Game resolution must equal the game's real resolution. Windows display scaling is handled; a wrong resolution is not.
Solid block instead of an overlay. Radar → Theme → Overlay background was changed; reset it.
“No collision mesh”. The map package for the visible check has not been downloaded. See Line of sight.
Aimbot#
“Makcu device not found”. The CH343 control port is not on the radar PC, the driver is missing, or another program holds the COM port. Unplug, replug, choose the port by hand.
“Device did not return expected signature”. Wrong firmware or the wrong port (a different USB-serial adapter). The device must answer km.MAKCU or a km.* variant.
“KMBox NET response timed out”. The radar PC cannot reach the box: same LAN, correct IP/port/MAC, firewall exception for SkyAim Pro.
Connected, but it never locks. Work through Aimbot not locking.
Quest tracker#
The page is empty or old. Stay at the main menu for a minute so the profile is read, then Ctrl F5 in the browser. After an app update the browser may still cache the previous page.
Item pictures are missing. They come from tarkov.dev and the wiki; the page needs internet for pictures only.
Settings and profiles#
Settings reset after a session. Settings live in %APPDATA%\SkyAimPro. Check that folder is not cleaned by a tweaking tool and that the launcher was left open until the app had fully exited.
I want my setup on a second PC. Copy %APPDATA%\SkyAimPro only. Never mmap.txt, Symbols or Logs.
Reporting a problem#
Send the newest skyaim-debug-*.log from output\Logs (launcher problems: launcher-update.log), the map, the time it happened, and a screenshot if it is visual. Do not send your license key in the report; the publisher can see it.
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).