Currently the controller is connected when the program is started.
There is no need to having the virtual controller connected outside of having the TAS running and while working with the NavHelper.
For the TAS, disconnecting the controller would also clear stuck inputs that are not cleared when clicking the "Stop TAS" Button.
In the NavHelper, a "Connect/Disconnect controller" button could act as a toggle for showing the "Navigate to target" and "Stop (timed)" segment of the window.
(also, much fewer windows peripheral connection sounds 😁)
Currently the controller is connected when the program is started. There is no need to having the virtual controller connected outside of having the TAS running and while working with the NavHelper. For the TAS, disconnecting the controller would also clear stuck inputs that are not cleared when clicking the "Stop TAS" Button. In the NavHelper, a "Connect/Disconnect controller" button could act as a toggle for showing the "Navigate to target" and "Stop (timed)" segment of the window. (also, much fewer windows peripheral connection sounds 😁)