Baron Turbo Coms issue
-
Support is looking into potential workarounds for this, but it was previously determined with the King Air and Caravan that this is a bug in the vPilot VATSIM client, specifically. There are plenty of discussions about this on the official forums, since it affects many 3rd party aircraft. Here is what was published in the King Air's changelog a few months ago:
"For those flying with online ATC, especially with VPilot, there is a bug in the application that requires the audio for ALL radios to be receiving to successfully monitor COM 1 & COM 2."
-
Support is looking into potential workarounds for this, but it was previously determined with the King Air and Caravan that this is a bug in the vPilot VATSIM client, specifically. There are plenty of discussions about this on the official forums, since it affects many 3rd party aircraft. Here is what was published in the King Air's changelog a few months ago:
"For those flying with online ATC, especially with VPilot, there is a bug in the application that requires the audio for ALL radios to be receiving to successfully monitor COM 1 & COM 2."
@voice-of-reason
Please talk to the devs before you dismiss this issue. It works with Fenix, FBW, PMDG, Milviz, HJet, 414, the default Baron aircraft, and others. It does not work in Just Flight Arrow or the Just Flight Baron. I have seen other posts that have addressed this problem. How can it be a Vatsim issue when other developers and the default aircraft have figured it out. From the default aircraft to the steam gauge update, Just Flight has changed something that has broken this option. I respectfully request that you investigate and address, not just dismiss this issue. -
@voice-of-reason
Please talk to the devs before you dismiss this issue. It works with Fenix, FBW, PMDG, Milviz, HJet, 414, the default Baron aircraft, and others. It does not work in Just Flight Arrow or the Just Flight Baron. I have seen other posts that have addressed this problem. How can it be a Vatsim issue when other developers and the default aircraft have figured it out. From the default aircraft to the steam gauge update, Just Flight has changed something that has broken this option. I respectfully request that you investigate and address, not just dismiss this issue.@lawman Would never dismiss it or any other problem people are encountering. The post from the baron developer was his initial thoughts and suggestion. Just Flight have nothing to do with the coding side of the Baron. We do though with the arrow of course and it's odd that the issue crops up with both as you say. The best thing for you to do is get this officially logged via a ticket with our support team. That way our support team can liaise direct with you and the whole thing is then easier to manage and hopefully get to the bottom of.
Hope that helps @Lawman and hope we can help get any issue sorted for you.
-
@voice-of-reason
Please talk to the devs before you dismiss this issue. It works with Fenix, FBW, PMDG, Milviz, HJet, 414, the default Baron aircraft, and others. It does not work in Just Flight Arrow or the Just Flight Baron. I have seen other posts that have addressed this problem. How can it be a Vatsim issue when other developers and the default aircraft have figured it out. From the default aircraft to the steam gauge update, Just Flight has changed something that has broken this option. I respectfully request that you investigate and address, not just dismiss this issue.@lawman Further on this from the developer for you...
I just researched this issue and discovered the cause. There is a bug with VATSIM clients that are using old variables for COM receiving from the FSX era. They require the "COM RECEIVE ALL" variable to be true to receive COM2 audio, even when the aircraft has more than two radios. I just tested the variables, and turning on COM3 with COM2 should work on VATSIM. If you would like a quick solution that will automatically enable COM3 whenever COM1 and COM2 are selected, paste the following into the AnalogBaron.xml (or AnalogBonanza.xml) before "<!-- Tip Tank Pumps -->". This file is located at: [YourCommunityFolder]\bksq-aircraft-analogbaron\SimObjects\Airplanes\bksq-aircraft-analogbaron\model.base\
<!-- VATSIM COM 1 and 2 Monitoring Backwards Compatibility -->
<UseTemplate Name="ASOBO_GT_Update">
<FREQUENCY>1</FREQUENCY>
<UPDATE_CODE>
(A:COM RECEIVE EX1:1, bool) (A:COM RECEIVE EX1:2, bool) and if{ 1 (>K:COM_RECEIVE_ALL_SET) }
</UPDATE_CODE>
</UseTemplate>I will research the problem further and see if there is a more elegant workaround for aircraft that support modern radio variables.
-
@lawman Further on this from the developer for you...
I just researched this issue and discovered the cause. There is a bug with VATSIM clients that are using old variables for COM receiving from the FSX era. They require the "COM RECEIVE ALL" variable to be true to receive COM2 audio, even when the aircraft has more than two radios. I just tested the variables, and turning on COM3 with COM2 should work on VATSIM. If you would like a quick solution that will automatically enable COM3 whenever COM1 and COM2 are selected, paste the following into the AnalogBaron.xml (or AnalogBonanza.xml) before "<!-- Tip Tank Pumps -->". This file is located at: [YourCommunityFolder]\bksq-aircraft-analogbaron\SimObjects\Airplanes\bksq-aircraft-analogbaron\model.base\
<!-- VATSIM COM 1 and 2 Monitoring Backwards Compatibility -->
<UseTemplate Name="ASOBO_GT_Update">
<FREQUENCY>1</FREQUENCY>
<UPDATE_CODE>
(A:COM RECEIVE EX1:1, bool) (A:COM RECEIVE EX1:2, bool) and if{ 1 (>K:COM_RECEIVE_ALL_SET) }
</UPDATE_CODE>
</UseTemplate>I will research the problem further and see if there is a more elegant workaround for aircraft that support modern radio variables.
@voice-of-reason said in Baron Turbo Coms issue:
If you would like a quick solution that will automatically enable COM3 whenever COM1 and COM2 are selected, paste the following into the AnalogBaron.xml
Hi,
I tried this hotfix, but I still can't it monitor COM2 when COM1 is active. It doesn't work as "BOTH" radio recive from other default aircrafts.
Any other sugestion for quick fix?