Skip to content
This repository has been archived by the owner on May 9, 2024. It is now read-only.

Connecting sometimes thinks your callsign is ATIS #63

Closed
dhawton opened this issue Aug 12, 2023 · 2 comments
Closed

Connecting sometimes thinks your callsign is ATIS #63

dhawton opened this issue Aug 12, 2023 · 2 comments
Assignees
@pierr3
Labels
bug Something isn't working

Comments

@dhawton
Copy link

dhawton commented Aug 12, 2023

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.
@pierr3
Copy link
Owner

pierr3 commented Aug 12, 2023

Good catch, I know what the issue is and will fix.

@pierr3 pierr3 self-assigned this Aug 12, 2023
@pierr3 pierr3 added the bug Something isn't working label Aug 12, 2023
pierr3 added a commit that referenced this issue Aug 12, 2023
@pierr3
Addressing #63
d9a55cf
pierr3 added a commit that referenced this issue Aug 25, 2023
@pierr3
Refactor datahandler, #63, bump vcpkg
9855c3e
@pierr3
Copy link
Owner

pierr3 commented Aug 30, 2023

Fixed in 1.4.0!

@pierr3 pierr3 closed this as completed Aug 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pierr3 pierr3

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dhawton @pierr3