Skip to content

Commit

Permalink
Merge branch 'main' into neilenns/kSetStationStatus
Browse files Browse the repository at this point in the history
  • Loading branch information
neilenns committed May 27, 2024
2 parents 3d47f14 + 9d807ff commit 73debeb
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 6 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,9 +54,9 @@ If you opt-in, you can opt-out at any time in the settings. You will need to res

### What is XC and XCA?

When you left click XC on a frequency that you are listening to, and if you are logged in as ATC, all the transceivers of that frequency will be cross-coupled. This means that all transmissions received by a transceiver in that list will also be re-emitted by all other transceivers. This allows for pilots in different parts of your airspace to hear eachother, since they may be using a different transceiver. In general, you should be using XC every time you control.
When you rigth click XCA on a frequency that you are listening to, and if you are logged in as ATC, all the transceivers of that frequency will be cross-coupled. This means that all transmissions received by a transceiver in that list will also be re-emitted by all other transceivers. This allows for pilots in different parts of your airspace to hear eachother, since they may be using a different transceiver. In general, you should be using XC every time you control.

When you right click XC, you activate "cross-couple across". This allows you to cross-couple across frequencies, meaning you can join multiple sets of transceivers regardless of frequency.
When you left click XCA, you activate "cross-couple across". This is the same as clicking "XC" in AFV for Windows, and allows you to cross-couple across frequencies, meaning you can join multiple sets of transceivers regardless of frequency.
Pay attention, however, as you may cause overlap of radio by enabling this. For example, if you XCA one frequency that has a transceiver near the border of a neighboring vAcc with another that is at the other end of your sector, far away from that border with your neighboring vAcc, you will suddenly extend coverage of that second frequency to the border with your neighboor.
This feature is mostly useful for CTR positions, when regrouping large sectors together.

Expand Down
2 changes: 1 addition & 1 deletion backend/CMakeLists.txt
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ add_library(trackaudio-afv SHARED
include(FetchContent)
include(ExternalProject)

set(afv_native_VERSION 1.28.0.12)
set(afv_native_VERSION 1.31.0)
set(afv_native_ARCHITECTURE "universal")

if (WIN32)
Expand Down
6 changes: 3 additions & 3 deletions src/app/components/radio/radio.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -231,11 +231,11 @@ const Radio: React.FC<RadioProps> = ({ radio }) => {
radio.crossCoupleAcross && "btn-warning"
)}
style={{ width: "45%", height: "100%", marginTop: "4%" }}
onClick={clickXc}
onContextMenu={clickCrossCoupleAcross}
onClick={clickCrossCoupleAcross}
onContextMenu={clickXc}
disabled={!isATC}
>
{radio.crossCoupleAcross ? "XCA" : "XC"}
{radio.xc ? "XC" : "XCA"}
</button>
<button
className={clsx(
Expand Down

0 comments on commit 73debeb

Please sign in to comment.