-
Notifications
You must be signed in to change notification settings - Fork 11
Unable to transmit when connected to an _1_ position #109
Comments
Thank you for the report, it’s not the only report i’ve had on something
similar, I will look into it.
…On Fri, 29 Mar 2024 at 12:27, Neil Enns ***@***.***> wrote:
To reproduce:
1. Have someone already connected to a position, e.g. PDX_TWR, in CRC
2. Connect to the same position in CRC with a plan to relieve the
other controller
3. Activate your session in CRC, you'll be connected as PDX_1_TWR
4. Connect in VectorAudio
Result: You'll connect, but your audio will never transmit out to pilots
even though the TX indicator will light up
Expected result: Audio transmits fine
It appears to be specific to having _1_ in the callsign. If you wait to
connect in CRC until after the other controller disconnects (so you connect
as PDX_TWR) everything works fine
—
Reply to this email directly, view it on GitHub
<#109>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN7UK4RJDJZFUGBTYSTPC3Y2WJAPAVCNFSM6AAAAABFOUK5AGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYTKNRVGUZTKNA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I've had success fixing this by Forcing a refresh of the audio station in VectorAudio. |
How do you do that? |
Click on the box with station name and select “Force refresh” |
I had no idea that menu was there. Thanks! |
The "Force refresh" method unfortunately doesn't work for me. To work around the issue I do this:
|
When this situation occurs, just manually add your station, for example |
This was fixed in TrackAudio, please head over to that repo for this |
To reproduce:
PDX_TWR
, in CRCPDX_1_TWR
Result: You'll connect, but your audio will never transmit out to pilots even though the
TX
indicator will light upExpected result: Audio transmits fine
It appears to be specific to having
_1_
in the callsign. If you wait to connect in CRC until after the other controller disconnects (so you connect asPDX_TWR
) everything works fineThe text was updated successfully, but these errors were encountered: