Does it support flight factor 320U?

[demonguy]

I happened to see that, it works on zibo 738 but not on Flight Factor 320. Do you have plan to fix it?

[jarangmandi]

Hi demonguy - can you be a bit more specific about what's not working please?

Many third party aircraft create their own internal variables for management of aircraft systems that is more detailed that X-Plane provides by default. Sometimes that can be worked around, other times it can't!

From experience with the FFA320 though (it's one of the few third-party aircraft I have), the likely solution will be an edit to the 'published.txt' file and the XPUIPC configuration file which provides the mechanism to convert visible X-Plane datarefs to the FSUIPC offsets that BFSGSimCom uses.

In short, I may be able to provide a workaround to get it working. A coded fix will be less likely.

[demonguy]

Well. I've just done some tested:

1. with the latest version of teamspeak 3 and BFGSimCom which i just downloaded today. Nethier zibo 738 nor ff320 can change automatically. When enable detailed information. It shows all 4 frequencies as 0.0

2. with Teamspeak 3.1.6 and BFSGSimCom 0.11.1. It works on my zibo 738. However on ff320, it shows the correct frequencies, but with message "unrecognised radio selected" (I turned off 2nd VHF)

Is there anything else i can provide?

[jarangmandi]

That should be enough to be going on with for now... I'll focus on the first combination above and comment back here when I know what's going on.

[demonguy]

BTW. this is where i downloaded BFSGSimCom https://www.myteamspeak.com/addons/0e1b55d0-f334-4c92-bdc5-e390cb2be4d0

[demonguy]

just menetion, i'm using xplane 14.1 with XPUIPC 2.0.38

[jarangmandi]

Hi - sorry it's taken a while.

You have downloaded the latest version of BFSGSimCom and looks like you're using the same version of X-Plane and XPUIPC as I am, so hopefully this will be easy!

In version 0.13 of the plugin, the code was changed to take advantage of the ability of X-Plane to work with the 8.33 kHz spacing that is becoming more common. Unfortunately the default behaviou of XPUIPC doesn't consider this so a small edit to the XPUIPCOffsets.CFG is required.

Simply paste the following lines to the end of the file, and the COM1 and 2 radios in any X-Plane aircraft should start working again.

#
# Added for XP 8.33Khz processing.
#
Dataref com1_freq_833   sim/cockpit2/radios/actuators/com1_frequency_hz_833 int
Dataref com2_freq_833   sim/cockpit2/radios/actuators/com2_frequency_hz_833 int
Dataref com1_stby_freq_833  sim/cockpit2/radios/actuators/com1_standby_frequency_hz_833 int
Dataref com2_stby_freq_833  sim/cockpit2/radios/actuators/com2_standby_frequency_hz_833 int
Offset  0x05c4  UINT32  3   r   $com1_freq_833 1000 *
Offset  0x05c8  UINT32  3   r   $com2_freq_833 1000 *
Offset  0x05cc  UINT32  3   r   $com1_stby_freq_833 1000 *
Offset  0x05d0  UINT32  3   r   $com2_stby_freq_833 1000 *

Let me know how you get on!

[demonguy]

It works on zibo 738 now. However ff320 still doesn't work. it shows "Unrecognised / More than one radio selected.". However i shut down com2 and com3. it still shows like this.

The problem is, com2 is off. com1 active frequency and standby frequency are all wrong.

BFSGSimCom:Connected to Sim.

Mode: Enabled and locked with root "连飞大厅|122.800", not moving with unmatched freq, not considering station range.

Unrecognised / More than one radio selected.

Com 1 Freq: 118.200 Com 2 Freq: 118.100 Com 1 Stby: 119.950 Com 2 Stby: 118.000

[jarangmandi]

I've tried this on the A320 sim tonight, and you're right in that when the Audio Control Panel (the panel in the bottom left of the pedestal in your picture) is set up the way you have it, the program reports that more than one radio is selected.

I have managed to reliably reproduce the issue that you're seeing - the plugin not picking up the selected frequency, and not responding to changes in the selected radios - and will issue a fix when I've found the time to code it.

The quick workaround is simple - you have two lit knobs on the left of the Audio Control Panel. One for VHF1 and one for VHF2. Make sure that only one of these is lit when you start TeamSpeak. The lit knob is the radio that's selected. Alternatively, change the BFSGSimCom mode to "Semi-Automatic" and place yourself in the root room (122.800 in your photo above) manually. This is the behaviour that I'll try to fix.

Note that in the real aircraft, it is the buttons above the switches that should define which radio is selected for transmit - only one of these can be lit at a time. Unfortunately, the default behaviour of the FFA320 is to populate the data that BFSGSimCom uses from the status of the knobs and not the switches above them, and it'll take a lot more to work out how to get past that.

[demonguy]

That's great. Thanks for your help