Troubleshooting and Questions - KuromeSama6/Autosu GitHub Wiki

Why are some Beatmaps unable to be loaded?

These beatmaps may be corrupt, are using an ancient file format, or are made by a user and is not fully validated. Some custom beatmaps made by users may not be able to load due to missing parameters.

If I install a new beatmap, do I have to restart the entire app?

No. Just click on Reload All Beatmaps From File button below the filter input bar, and the beatmap listing should reload with your new beatmap in it. Note that reloading may cause autopilot to malfunction and fail to move the mouse. If this happens, refer to Autopilot is not moving my mouse.

Why is my mouse not moving?

Check the following items in order:

• Autopilot panel - MNAV button is enabled;
• There were no antivirus popups of any kind regarding Autosu!. Some antiviruses (Nortan is known to block Autosu!) may block programmatic mouse movements. If so, add whitelist to Autosu!. You do not need to disable the entire antivirus.
• If non of these options work, restart Autosu! and try again. Mouse and keyboard hooks may fail to load on the first run of Autosu! and will work after restart. This is a known problem waiting to be fixed.

When I press CMD to arm Autopilot!, nothing happens. The indicator below the button does not turn on.

Autopilot just disengaged and you did not suppress the warning. Open the autopilot panel, find a flashing A/P P/RST annunciator and press it once to suppress it.

Autopilot disengages noisily with flashing lights. What does this mean?

It could be one of the following:

• If the MNAV DESYNC annunciator is flashing, this means that the system clock fails to keep up with mouse movement instructions. Mouse movements (positions) in the mouse movement queue (List<Vector2> Autopilot.mouseMoveQueue) should take no more than 1 millisecond to execute. If the queue is not cleared before node judgement time and the key is pressed, it will be forcibly cleared. MNAV DESYNC turns on when control is switched to keyboard and there are more than 60 unexecuted movements left in the queue. This disengages autopilot immediately.
• If the HNAV FAULT annunciator is flashing, this means that the mouse is not at its destination at judgement time. This could mean that the mouse movement queue is not cleared. If there are more than 1 unexecuted movement in the queue, the HNAV FAULT annunciator is turned on. If there are more than 3, autopilot disenagages.
• Otherwise, you have pressed the disengagement key (END) and caused autopilot to disengage.