If you get disconnected, reconnecting if you don't close vATIS seems to cause VectorAudio to use that as your callsign.
Reproduction steps:
1) Connect to network using preferred client
2) Load vATIS and connect that to network
3) Connect VectorAudio, callsign will become xxxx_ATIS and will not stay connected or seem to figure out the callsign
If you connect VectorAudio then vATIS, but then get disconnected, it can get tedious especially if in high workload situations to go through and disconnect the multiple ATIS connections in vATIS, to then connect VectorAudio, then reconnect vATIS.
If you get disconnected, reconnecting if you don't close vATIS seems to cause VectorAudio to use that as your callsign.
Reproduction steps: 1) Connect to network using preferred client 2) Load vATIS and connect that to network 3) Connect VectorAudio, callsign will become
xxxx_ATIS
and will not stay connected or seem to figure out the callsignIf you connect VectorAudio then vATIS, but then get disconnected, it can get tedious especially if in high workload situations to go through and disconnect the multiple ATIS connections in vATIS, to then connect VectorAudio, then reconnect vATIS.