Troubleshooting

AutoPTT isn’t pressing my PTT key

If you’re using AutoPTT with games/apps that are running as admin, then AutoPTT needs to be run as admin, as well.

It’s also worth noting that if you’re running a game as admin and AutoPTT as admin while using AutoPTT to speak through another app like Discord, then (currently) that app also needs to be run as admin. (There might be a way to fix this part in AutoPTT; I need to look into it.)

It is also possible that the game you’re playing requires any input to come from a physical device, ignoring the simulated input generated by AutoPTT. Such games are rare, but you can check whether Virtual Input is supported in your game from this list.

You can also get around this limitation by installing the FakerInput driver and then setting Input Mode in AutoPTT to FakerInput.

AutoPTT Sidekick is also an option. It is basically the same thing as FakerInput but it requires physical hardware (a cheap microcontroller) and some work on your part to flash it, whereas FakerInput is just a simple driver install.

Automatic profile switching is not working

If it’s not a typo in your trigger(s), then it’s likely that the trigger program is running as admin and AutoPTT is not. Fix this by running AutoPTT as admin.

FakerInput is not detected

Are you sure you’ve installed FakerInput?

AutoPTT Sidekick is not detected

Try running AutoPTT as admin, there may be a problem with missing permissions otherwise.

I can’t flash the Sidekick

If you see an error like the following

Error finding build artifacts: binary file not found in itsy-bitsy.hex

make sure you’re running the arduino-cli upload command in the same directory where the hex file is. To change the directory, you can do cd "some\other\directory" or cd /d "F:\directory\on\another\drive"

Other problems?

Get in touch.