Hallo LINDA friends,

after upgrading to latest FSUIPC version I get the following error-message:

 

 

[E] *** LUA Error: ...steamapps\common\FSX\modules\linda/system/common.lua:4314: attempt to compare number with nil

 

 

and LINDA is completly out of busssines.

 

Help is appreciated.

 

regards,

 

Wolfgang

 

What version of LINDA are you using?

Hallo Scotflieger,

I`m on Linda version 2.8 latest version and latest version of FSUIPC.  Meanwhile I cleared out that this failure only concerns the Aerosoft Airbus on all the moduls

I`ve available.

I tried multiple combinations of Linda versions and Airbus moduls, they all gave me the bad result.

What me surprises is the fact, that the Linda 2.8 / Airbus 4.x combi went fine until yesterday afternoon, and suddenly things went south.

Couldn`t imagine what I`ve done to trigger this.

BTW  I´m the one with the LSK6R function for the Bus but that should not be the culprit.

Thanks for Looking on to it +

kind regards,

Wolfgang

Hi Wolfgang, the error you reported is occurring in the common.lua function DspALTs. Although this function exists, it should not be called in the current Airbus 4.3 module. Can you confirm that you are using a VRInsight Airbus FCU panel? Have you tried to use any of the DspALT functions or added any addition code?

@ Scotflieger,

 

using the old VRI MCP1 panel.  Maybe I tried such a function to see what it is, but is not assigned to a knob. No additional code is added.

regards,

Wolfgang

I am having the same issue with the Aerosoft Airbus since updating to 2.8.4 using the MCP II Boeing panel and Saitek panels. Was using 2.6.3 prior with no issues. No panels are working. Linda recognizes all button and switch movements in the UI but they are not reflected in the sim.

I am having the same issue with the Aerosoft Airbus since updating to 2.8.4 using the MCP II Boeing panel and Saitek panels. Was using 2.6.3 prior with no issues. No panels are working. Linda recognizes all button and switch movements in the UI but they are not reflected in the sim.

UPDATE: A full reinstall of LINDA 2.8.4 got my saitek panels working but the Boeing MCP2 is still not working.  I have double checked the setup for it in Linda and it seems correct to me.

UPDATE: A full reinstall of LINDA 2.8.4 got my saitek panels working but the Boeing MCP2 is still not working.  I have double checked the setup for it in Linda and it seems correct to me.

I am about to issue an update (2.8.5) to address reported problems like yours. Please switch on developers mode, tracer and select LUA verbose logging. Restart FSX and LINDA and confirm fault. Then email me at [email protected] the files: linda2.log and fsuipc4.log.

I am about to issue an update (2.8.5) to address reported problems like yours. Please switch on developers mode, tracer and select LUA verbose logging. Restart FSX and LINDA and confirm fault. Then email me at [email protected] the files: linda2.log and fsuipc4.log.

 

I got it working. Here were the steps I took:

 

1) I copied my Linda linda-cfg folders as you suggest in the install instructions (thank goodness).

2) I deleted all existing Linda folder and files in the Modules folder.

3) Did a fresh reinstall of 2.8.4

4) Copied back in my Aircrafts folders into both the linda and linda-cfg folders.

5) Was still having problems with all panels (Saitek and VRinsight MCP2).

6) Found another forum post that advised that if you have multiple Airbus folders (e.g., A319, A320, etc.) in your modules/linda-cfg/aircrafts folder to get rid of all of Airbus folders as the new linda version uses a single Aerosoft Airbus folder.

7) This got my Saitek panels (i.e., radio, switch, and TPM) working but the VRinsight MCP2 still wasn't.

8) I then copied the config-mcp2.lua file from my old linda-cfg/Aircrafts/Aerosoft Airbus A320 CFM folder and replaced the one in the linda-cfg/Aircrats/Aerosoft Airbus folder and the MCP2 started working.

 

 

So from this I surmise this that there is some difference between the installed config-mcp2.lua and the one I have but I haven't found the difference yet.

I am pleased you have got things sorted and working again.

 

The duplicate Aerosoft Airbus folders would cause your reported problem. A full restart after deleting or renaming the old folders should have got things working.