Let’s find what’s not working.

Start from Downloads, using your own license key. An old download link or an older copy of aimos may no longer work.

1. Open Downloads and enter the key from your purchase email. Use the buttons shown for that license: 1PC and 2PC are separate products.
2. If the page says the download is being prepared, let it finish. Avoid clicking the download button repeatedly.
3. For an update message, close the old copy and download again from the website. Use the new download with the same key. Don’t use a file sent by another customer.
4. If the download is marked unavailable or you’re asked to wait, try again later. Save the exact message if it continues.

If it still doesn’t work: Send the download message and whether it happens before or after entering your key. Don’t post the key itself.

The message matters here. A paused license, an expired license and a device change need different actions.

1. Copy the key again from your purchase email, without extra spaces. Check you opened the correct 1PC or 2PC download.
2. If the license is paused, open My account and use Resume if it is available. An admin pause or a ban needs support; downloading again will not remove it.
3. If it says expired, check the license in My account. If you bought recently and the information looks wrong, contact support with your purchase receipt privately.
4. If it says already in use, close aimos on the previous computer and wait a short time before trying again. For a changed PC or an HWID message, use the device-reset option in My account if available, or ask support.

If it still doesn’t work: Send the exact message and say whether you recently changed your PC, reinstalled Windows or switched between 1PC Color and AI.

Don’t turn off your antivirus or firewall to get past a warning. First check where the file came from and what Windows is reporting.

1. Make sure you downloaded from aimos.pro/downloads, not a message, mirror or another person’s file.
2. Read the exact warning. A browser download warning and a detection in Windows Security are not the same thing.
3. If Windows Security removed the file, open Protection history and note the detection name. Don’t add broad exclusions or restore a file you’re unsure about.
4. Send support a screenshot of the warning before continuing. Hide your key and personal details.

If it still doesn’t work: Include whether the warning appeared in your browser, when opening the file, or inside Windows Security.

The 2PC settings page comes from the aimos window running on PC2. It won’t open if that window has closed, or the PCs cannot reach each other.

1. On PC2, check aimos is still running. Copy the current address shown after “Open this URL on PC1”. The address can change after a network change or restart.
2. On PC1, enter the full address in the browser address bar, including http:// and :777. Don’t use localhost or 127.0.0.1 on PC1; those refer to PC1 itself.
3. Connect both PCs to the same trusted home network. Avoid a guest Wi-Fi network, which can separate devices. Check whether a VPN is preventing local-network access.
4. On PC2, try http://127.0.0.1:777. If it opens there but not on PC1, check Windows Firewall allows aimos on your trusted Private network. Leave the firewall on and don’t open router ports.

If it still doesn’t work: Tell support whether the page opens on PC2, and whether the browser says connection refused or connection timed out.

Check normal desktop movement first. The PC2 connection and the mouse connection are separate, so one can work while the other does not.

1. Close aimos and check that moving the mouse moves the cursor on PC1. If not, test the mouse directly on PC1, then recheck the MAKCU wiring.
2. For the MAKCU shown in our guide, the left port goes to PC1, middle to PC2 and right to the mouse. Compare your unit with the guide; don’t guess if its layout differs.
3. Use USB data cables, connect directly to the PCs and close other software that may be using MAKCU. Reconnect and open aimos on PC2.
4. Read the MAKCU status in the panel. “MAKCU detected on PC2” with a mouse warning is not the same as “MAKCU connected”. Follow the message shown.

If it still doesn’t work: Send the MAKCU status and a photo showing all three cables. Say whether normal desktop movement works with aimos closed.

The screen-sharing menu appears after DistroAV and its NDI requirement are installed for your copy of OBS.

1. Close OBS on PC1, install DistroAV and NDI Runtime using the links in the setup guide, then reopen OBS.
2. Check Tools for DistroAV NDI Settings. If you have more than one OBS installation, make sure you opened the one where you installed DistroAV.
3. If OBS reports a missing NDI Runtime or an incompatible plugin, use the DistroAV installation guide for the versions it requires. Restart OBS after making the change.

If it still doesn’t work: Send the OBS version and the exact message. You don’t need to reinstall your mouse or board for a missing OBS menu.

Check both ends: OBS needs to share the screen on PC1, and aimos needs OBS selected on PC2.

1. On PC1, open OBS and confirm its preview shows your gaming screen. Open Tools → DistroAV NDI Settings and enable Main Output. Keep OBS open.
2. In the aimos panel, open OBS / Video Capture and select OBS. It stays on the source you select; it won’t switch to OBS just because you opened OBS.
3. Leave OBS source name empty if there is only one source. If you entered a name earlier, check it still matches the source you want.
4. Keep both PCs on the same trusted network, preferably using Ethernet. Check local-network access if using a VPN or guest Wi-Fi. If Windows Firewall prompts, allow the required apps on your trusted Private network; don’t disable the firewall.

If it still doesn’t work: Send the OBS preview, Main Output setting and the connection message from aimos. These show whether the picture stops at PC1 or before reaching PC2.

A connected source can still contain the wrong picture. Check what OBS or the capture card is actually sending.

1. For OBS: check Display Capture uses your gaming monitor. Make the source visible and check no other source covers it. The preview should show the whole display, without borders or stretching.
2. Keep your Windows display, game and OBS resolutions consistent. Recheck the preview after changing the game resolution or connecting another monitor.
3. For a capture card: PC1 goes to HDMI IN, and the card’s USB goes to PC2. Select Video Capture in aimos. Check the card supports the selected signal, and close other apps using it.
4. The FOV illustration in Aim or Magnet is not a live picture. Use OBS / Video Capture to check the actual source and connection status.

If it still doesn’t work: Send the OBS preview or capture-card model, plus the resolution and source name shown in aimos. Avoid changing Aim settings until the shared picture is correct.

Small details are easier to lose when the shared picture is reduced or stretched. A choppy picture can also make otherwise smooth movement feel inconsistent.

1. For a Full HD setup, check OBS Base and Output are both 1920 × 1080 and the source fills the canvas without stretching. Don’t lower the output resolution as your first fix.
2. Use wired Ethernet for both PCs if possible. Check that the cables and network ports support a gigabit connection, and pause large local transfers while testing.
3. If 120 FPS stutters, try 60 FPS with the same resolution. Check OBS → View → Stats for rendering lag. Close unnecessary heavy apps and compare again.
4. In aimos, check the actual source resolution and frame rate. Power Saver can reduce activity while idle; test with a feature active before treating a lower idle number as a fault.

If it still doesn’t work: Send OBS Video settings, the source resolution and frame rate in aimos, and whether you use Wi-Fi or Ethernet. For a capture card, include its model and USB connection.

A working mouse connection is only one part of the check. Confirm the picture, activation button and feature settings before changing several values at once.

1. Check normal mouse movement first. On 2PC, also check that your chosen video source and MAKCU are connected.
2. Enable only the feature you’re testing, save the changes and hold its assigned activation button. On 2PC, use a button on the mouse connected to MAKCU; PC1 keyboard keys do not activate it.
3. Check the target is inside that feature’s FOV. Aim, Magnet and Trigger can have different areas and activation settings.
4. For 1PC Color or 2PC, check the in-game enemy outline color matches your color settings. This color check is not a setup step for 1PC AI.
5. If Trigger or Magnet moves but does not shoot, check its activation and firing conditions in a practice area. Movement toward a target alone does not mean a shot should fire.

If it still doesn’t work: Say which feature fails, which button you hold, and whether movement, firing or both are missing. Send that feature’s settings and a short clip if possible.

First check that normal desktop movement works. Then compare one setting at a time in the same practice area.

1. Save your current configuration before changing it. Check the settings for the feature you are actually using: Aim and Magnet have their own Smooth values.
2. Lower Smooth values are faster. Increase Smooth gradually for a softer response; don’t assume the same number feels identical across different products.
3. If it consistently sits too low, check Bone Offset against the default or a saved configuration that worked. An offset changes where the aim settles; it does not repair an incorrect picture or a mouse-connection problem.
4. On 2PC, check the shared image is sharp, correctly sized and current, especially for distant targets. If the target is lost or jumps between positions, send a clip rather than compensating with extreme settings.

If it still doesn’t work: Include Aim or Magnet, Smooth X/Y, Bone Offset, FOV and whether it happens at close range, far away or both. Keep the same mouse DPI while comparing.

A page losing connection does not, by itself, tell us why aimos stopped. First check whether the app is still open on the computer running it.

1. For 2PC, check PC2. Closing the aimos window stops the app; the settings page on PC1 cannot keep it running.
2. If the app is still open, refresh the panel using the current address. If only the video stopped, check OBS or the capture card instead.
3. If the app has closed unexpectedly, note the time and what you were doing, then reopen it once. Keep any message that appears. Don’t repeatedly relaunch it if it keeps closing.
4. Tell support if it happened after changing a setting, reconnecting hardware or losing the video. If Windows error history is unavailable, you can still send these details; support can guide you through the next check.

If it still doesn’t work: Send the approximate time, 1PC or 2PC, and the last action before the problem. For 2PC, say OBS or capture card. A repeatable sequence is more useful than guessing a memory leak.

Use the same license and product when checking saved settings. A failed save or a different product can explain why the values don’t match.

1. Check you signed in with the same license and opened the same product: 1PC Color, 1PC AI or 2PC. Don’t expect their settings to be interchangeable.
2. Make one small change, click Save if the panel has a Save button, and wait for confirmation. If it shows an error, keep the page open, check the running PC has internet access, and retry after the connection returns.
3. Use Configs for your saved configurations. Read what an export code includes; a shared code may contain only some settings, not your entire setup.
4. On a different PC, check the mouse and video connections again. Restoring a configuration doesn’t connect the hardware or select a screen for you.

If it still doesn’t work: Send the save message and the specific setting that changed. Don’t post a license key or a full private configuration publicly.