Problems with P3dV3.4, LINDA, and Aerosoft Airbus

[Petraeus 147]

The Aerosoft Airbus controls have stopped working for me in P3DV3.4 - other aircraft like the PMDG and Majestic still work. Any theories?

 

The assignments in LINDA are the same as before, but now there's no response when I turn a knob or press a button. FSUIPC can see the buttons and knobs as before.

 

When I touch a (VRInsight Combo I) knob or button or switch, the LINDA UI highlights it, and I can reassign the control, but nothing happens in the plane.

 

I have reinstalled P3DV3.4, LINDA, the Airbus, and the Aerosoft Airbus (module 4.3) v2 

[OldFlyboy 30]

Same here, only worse:  LINDA has stopped working completely in P3D 3.4 It recognizes the plane but no buttons or levers work with it. All settings checked OK. What to try?

[gboz 157]

I had trouble until I updated FSUICP to 4957b.

 

gb.

[Petraeus 147]

I'm using 4.9.5.7

[Petraeus 147]

I've gone back to version 3, and it now works again. It seems that version 4 does not like the Combo I.

[DT506 9]

I found i had the same problem but with the PMDG 777. It was Linda not loading the correct module. Always loaded the default aircraft. If i force the correct module and reload the lua everything is fine.

[Petraeus 147]

Which module, and how did you force it?

 

[b1akcr0w 0]

Hi all,

 

I think I might be having the same problem.

Linda 2.83

P3d 3.4.9.18400 (installed in c:\lockheed martin\Prepard3d\)

FSUIPC 4.957

FCU Combo

 

Symptoms:

When I start P3d, the panel does flicker. But there seems to be no interaction between the panel and the aircraft.

In FSUIPC, the Buttons panel does register some input from the panel.

Looking at the Linda console, it does give me a red LUA error, cannot load the module .../FSX Default/config-mcp2a.lua

also 504: '<name>' expected near '}'

 

fWIW, I also can't seem to get the VRInsight keymapper to work with FSUIPC either. The default module works in SerialFP2, but none of the mapped keys seem to er... map

 

Any help, advice or suggestions gratefully received.

I should say I'm having the same issue whether I load the Aerosoft A320, or a default Aircraft, 

[ScotFlieger 280]

Hi all,

 

I think I might be having the same problem.

Linda 2.83

P3d 3.4.9.18400 (installed in c:\lockheed martin\Prepard3d\)

FSUIPC 4.957

FCU Combo

 

Symptoms:

When I start P3d, the panel does flicker. But there seems to be no interaction between the panel and the aircraft.

In FSUIPC, the Buttons panel does register some input from the panel.

Looking at the Linda console, it does give me a red LUA error, cannot load the module .../FSX Default/config-mcp2a.lua

also 504: '<name>' expected near '}'

 

fWIW, I also can't seem to get the VRInsight keymapper to work with FSUIPC either. The default module works in SerialFP2, but none of the mapped keys seem to er... map

 

Any help, advice or suggestions gratefully received.

I should say I'm having the same issue whether I load the Aerosoft A320, or a default Aircraft, 

 

 

First of all, none of the VRI software should be used with LINDA (except for the USB drivers). LINDA operates directly with FSUIPC4 to read the VRI knobs and buttons.

 

The error is occurring when the FCU configuration file is being loaded.  Please open the /modules/linda-cfg/aircrafts/fsx default/config-mcp2a.lua file in the LINDA editor and locate block RADIOS = { containing line 504. Copy and paste the 10 lines of the block here in the thread.

[b1akcr0w 0]

-- ############################################### --

-- ## ARADIOS block mode1

-- ############################################### --

 

-- RADIOS block buttons and switches

RADIOS = {

["COM ."] = Default_COM_select ,

["NAV ."] = Default_NAV_select ,

["ADF ."] = Default_ADF_select ,

["DME ."] = Default_DME_select ,

["TRAN."] = Default_XPND_select ,

["TFR ."] = Default_RADIOS_swap ,

["STBY."] = Default_RADIOS_mode ,

["LAMP."] = {LAMP.},

 

["COM1 Select"] = empty ,

["COM2 Select"] = empty ,

["COM1 Swap"] = empty ,

["COM2 Swap"] = empty ,

["COMs Mode"] = Radios_COM_AUDIO_toggle ,

 

["NAV1 Select"] = empty ,

["NAV2 Select"] = empty ,

["NAV1 Swap"] = empty ,

["NAV2 Swap"] = empty ,

["NAVs Mode"] = Radios_NAV_AUDIO_toggle ,

 

["ADF1 Select"] = empty ,

["ADF2 Select"] = empty ,

["ADFs Mode"] = Radios_ADF_AUDIO_toggle ,

 

["DME1 Select"] = empty ,

["DME2 Select"] = empty ,

["DMEs Mode"] = Radios_DME_AUDIO_toggle ,

 

["XPND Select"] = empty ,

["XPND Swap"] = empty ,

["XPND Mode"] = Transponder_MODE_toggle ,

}

 

DME1 = {

["A +"] = empty ,

["A ++"] = empty ,

["A -"] = empty ,

["A --"] = empty ,

["PRESS"] = empty ,

}

 

FRE1 = {

["A +"] = Default_RADIOS_plus ,

["A ++"] = Default_RADIOS_plusfast ,

["A -"] = Default_RADIOS_minus ,

["A --"] = Default_RADIOS_minusfast ,

["PRESS"] = Default_RADIOS_press ,

}

[ScotFlieger 280]

-- ############################################### --

-- ## ARADIOS block mode1

-- ############################################### --

 

-- RADIOS block buttons and switches

RADIOS = {

["COM ."] = Default_COM_select ,

["NAV ."] = Default_NAV_select ,

["ADF ."] = Default_ADF_select ,

["DME ."] = Default_DME_select ,

["TRAN."] = Default_XPND_select ,

["TFR ."] = Default_RADIOS_swap ,

["STBY."] = Default_RADIOS_mode ,

["LAMP."] = Default_LAMP_toggle,

 

["COM1 Select"] = empty ,

["COM2 Select"] = empty ,

["COM1 Swap"] = empty ,

["COM2 Swap"] = empty ,

["COMs Mode"] = Radios_COM_AUDIO_toggle ,

 

 

Change the line ["LAMP."] = to that shown above, save and restart FSX and LINDA.

[Erni49 0]

Hi All

 

Are the problems with P3D v4 with Vri-FCU Airbus, Linda and AS-Airbus solved? I'm still on v2 and was waiting updating to v4, because problems were reported here. I also saw a topic from Scotflieger in the P3d forums. But also not a clear answer still there.

[ScotFlieger 280]

Hi All

 

Are the problems with P3D v4 with Vri-FCU Airbus, Linda and AS-Airbus solved? I'm still on v2 and was waiting updating to v4, because problems were reported here. I also saw a topic from Scotflieger in the P3d forums. But also not a clear answer still there.

 

 

I only have access to P3D v3.4 and LINDA works fine for me. The only issue is that add-on programmes like LINDA and AS16 are causing P3D v3.4 to crash on exit stopping these programmes closing automatically. I have no knowledge of P3D v4 so cannot make any statement on compatibility.