Troubleshooting

The app does not open

Wait for the old process to fully exit before starting another. AIM-X is single-instance.
Keep Qt runtime files and support files beside the executable. Copying only the .exe is not a complete installation.
Check that the executable folder is writable and settings.jsonc is valid.
Do not disable system security as a workaround. Obtain a complete package from your trusted distributor.

Attach is locked or unavailable

Confirm your license in the desktop app. Check that your package supports the running game build. Force inject is not authorization for gameplay input on an unverified build.

Duplicate rings or offset overlays

Record your game resolution and Windows display scale.
Check which renderer is confirmed in the desktop app.
Test Overlay and D3D11 hook separately.
Capture the issue without including license keys or local API tokens.

Do not assume this is an aim-calibration issue. Screen-space rendering and gameplay input have different responsibilities.

Missing or stale information

Check the connection and live-scene state. Lobby, death, scene changes, stale telemetry, and unsupported game builds can pause functionality. Empty data is not proof that a feature is broken.

Local API errors

Use loopback addresses, the correct service’s bearer token, and a local non-browser client. See the response-code guide.

A useful support report

Desktop version and package origin.
Windows version, display scale, game resolution, and renderer mode.
What you expected, what happened, and reproducible steps.
A screenshot or short recording with secrets and personal data removed.
Relevant error text and compatibility state.