Search the Community

Hi there, I know Windows ans FSUIPC are limited to recognise more than 32 buttons per device. How is it with LINDA? Are there any limitations? Could I use a Leo Bodnar BBI-64 Button Box Interface and would LINDA recognise all buttons? Thanks 🙂

Hi I am trying to connect my Stream deck to the FS2020. I have installed Vjoy and UCR and up to there everything is active. i have installed LINDA. it gives me all green.... On FS 2020, I can see the VJOY in control and I see a text saying LINDA IS UPDATING COMMANDS. BUT.... it doesnt work... any advices? hints? something?? thanks alot!

Hi all: I have a problem with the combo 1 (first version) and any version of the LINDA higher than 1.13. It always blocked the CH Yoke. It starts working well, but at the moment, just 5 or 10 seconds after.... it blocks the joke and it does not work anymore. I have the throttle quadrant also, but only the yoke is blocked. It seems that it blocks the windows driver, although I do not know if it is motivated by the fsuipc or LINDA itself. Thank you, in advance. José M. Plasencia Fuentes.

Hi I'm new on this forum. I have : -- P3D v3.4. -- LINDA 2.8.8. -- saitek radio panel -- saitek multi panel 1. I have a message error in P3d when I "reload LUA engine" --> "Saitek Multi panel is DETECTED but couldn't be opended. I don't know how to resolve this error. 2. When LINDA is open, the radio panel always show the "COM1" frenquency and erase information on the multi panel. Thanks for your help. Noel :smile:

Several users have reported various errors with devices not connecting to LINDA. Some of these errors are related to newer USB devices such as touch screens and the wireless mice/keyboards. To help you to get LINDA working, it is useful to know what device is causing the problem. Please follow the following guidelines when reporting the error: 1. Unplug the USB for all your devices (joysticks, throttles, touch screen), reboot your system and open LINDA. 2. Plug in each device one-at-a-time and ensure that LINDA shows the device on the Summary and Setup Joysticks pages and that buttons are highlighted on the Joysticks page. 3. If an error message is displayed, either as a pop up dialog or on the LINDA Console, note or take a screen shot of the full error message. 4. Find and note the Vendor and Product IDs (VID and PID) as described below. 5. Report your problem on the Support forum quoting the LINDA version you are using. I will do my best answer your problem. PID & VID The PID and VID can be viewed by opening the Device Manager and looking under Human Interface Devices. Find the device that is not being recognised by LINDA and open the properties (double click or right click and select properties). Then under Details, select Hardware Ids from the Property dropdown. The Vendor and Product IDs (VID/PID) appear in the first and second line as a 4 character hexadecimal number. The VID and PID are used by LINDA to work out the type of device and whether it should be included in the list of devices. UPDATE Further investigation and testing by affected users has identified that the ‘Device cannot be opened’ errors are being generated by the third-party library routines used by LINDA to interface with HID devices. Even updating to the latest version of the library has not resolved the problem with certain devices. There is nothing more I can do a this time with the LINDA code until the library is updated. The only way forward I can suggest is for affected users to isolate the USB device that is stopping the others working and leave it disconnected. Not a satisfactory situation I know.

Users who have purchased or are thinking of purchasing the new Steam Edition of FSX (FSX-SE) will want to know that LINDA can be used with this latest version of Microsoft FSX. FSX-SE is installed using the Steam downloading service (priced £20 in UK). It is a big download at 10GB and took over 12 hours to download using my slow broadband internet connection. The main Steam directory is normally be installed in C:\Program Files (x86)\ but can be installed in the root directory as I did. When FSX-SE is installed it is buried deep in the Steam directory at \steam\steamapps\common\fsx. You will note that the folder has the same name as the boxed version of FSX. LINDA needs to be installed as normal in this FSX folder by copying both the \modules and \sound folders from the download and saying Yes to all overwrites. The main LINDA codes resides in the \Modules folder within FSX alongside the latest full (paid) version of FSUIPC (4.939). A shortcut should be created to LINDA.exe and placed in a convenient place on your Desktop. Remember this LINDA shortcut will be different from that used with your old FSX or Prepar3D. If you use all 3 flight simulators you will have 3 installation of LINDA. You will save yourself time by copying any configuration and aircraft files from your old FSX to FSX-SE. This will include files from \linda-cfg\aircrafts and \linda\aircrafts (just those aircraft you use and FSX Default)). If you FSX-SE on start reports that a copy of the program is already running, you probably find that LINDA is open and needs be closed before FSX-SE can be started.

As LINDA users will be aware I have let the real world get in the way of LINDA development and support. This busy period should come to an end towards the end of Oct 15. Please use this thread to lodge any suggestions for improvements and to raise any issues users are experiencing with LINDA 2.6.3. Even you have been in touch with me please post a detailed description of the problem and how to reproduce it. I cannot promise that everything will be included but it will allow me to assess the workload. Note: LINDA 2.6.4 has been issued to fix a problem with odd characters on the VRI Combo 2 (Boeing) panel and may fix some Range Check error reports.

Hello, i finished up my first LINDA module. It is for Cera Sims Bell 212/412. It has basic features for engine start, light control and door control. It is now possible to start the Bell 212/412 completely via joystick and/or switch controls. All necessary switches are working to get from cold and dark to ready to fly. No need for mouse clicks anymore. I did not hold on to the standard operating procedures discribed in the manual. v 1.2 Module features - Not available at this time - toggles now working - toggle standby attitude indicator - toggel anticolission light seperatly - toggle position light seperately - toggle fuel pumps seperately - toggle fuel pumps all on/off v 1.0 Module features - toggle rear doors open/close - toggle eject cockpit doors + rear seat rows - switch position lights + anti collision lights on/off - switch engine 1+2 start switch on/off - switch both battery switches on/off - switch inverter switches all on/off - switch generator 1+2 on/off - switch radios all on/off - switch pitot/static heater on/off Below is an dropbox link to download the module. CS Bell 212 CS Bell 412 Thanks Guenter for your help Greetz MJ

For those users thinking of upgrading to P3D v4.2 I can confirm that LINDA 3.0.5 works fine with it provided you revert FSUIPC5 back to v5.122. The latest FSLABS A320X v231 (requires P3Dv4.2) also works as before with the latest LINDA beta module.

This new module for the Milviz DHC3 Turbo Otter has been kindly provided by Graham McNicol. It is released on an 'as-is' basis for those keen to fly the aircraft with LINDA. No default VRi MCP Combo configuration files are provided. v1.2->v1.3 Module structure improvement so only "DHC-3T Otter" is required to sync to all variants. v1.1->v1.2 All function names changed to be user-friendly. (This will require updating your switch assignments.) Modules for all variants-- wheels, skis, floats, and amphibian added Instrument Light dimmer added combination T&S and Comp switch added Cabin fan Hi-Lo and toggle switch added Climate controls for Temperature selection and Fresh Air ventilation added Emergency Power controls added Emergency Fuel & Oil shutoff v1.0-->v1.1 Sound functions adjusted to avoid potential conflict with other lua files added MasterSwitch added Condition Lever Latch switch added StarterOff & P3 switch cover closed added DeiceBoth On/Off to handle Engine Deice & Icing Doors simultaneously Download: Milviz DHC3 Turbo Otter v1.3 To install the module: Download and expand the zip file into a suitable accessible location (ie. desktop). Open LINDA and ensure that the aircraft selector is not Sync-ed to Sim and --Aircrafts-- is displayed. Click on the Maintenance option. Under Import Aircraft Module click on Select Source Folder and locate the folder Milviz_DHC3_T_Otter_v1_2. Click on Select. Click on Install/Overwrite Module button. Open your Flt Sim and click on Sync To Sim (ensure DHC-3 Turbine Otter Milviz displayed and outlined in orange). Enjoy. Details of available functions are contained in the DHC-3T OTTER MILVIZ-Functions.txt file in the /module/linda/aircrafts/DHC-3T OTTER MILVIZ/. Standard default library functions may be used for many operations (eg. landing gear and flaps). Please report all issues and suggestion under LINDA Support.

Hello. Will LINDA continue to work in the future? As a big fan and user of Linda, I ask myself exactly this question. Against the backdrop of a 64-bit version of the Flight Simulator Prepar3D, which is expected to be released in the future, discussions are constantly taking place that 32-bit programs such as Linda would no longer work with a 64-bit P3D version. Since it would be for me of immense importance to learn how this with LINDA and P3D 64-Bit behaves. Cheers Christian

LINDA Problem and Fault Diagnosis - Guidance LINDA users reporting problems or faults with LINDA would greatly assist in the diagnosis of their problem by providing the following information: 1. LINDA application version (go to LINDA Settings/About). 2. LINDA aircraft module name and version (in LINDA header). 3. FSX, Prepar3D (P3D) or MSFS version. 4. Aircraft supplier, model and version. 5. What were you trying to do (ie. connecting, programming functions, operating panel, etc). 6. A detailed description of what the problem is. Comments like “It doesn’t work” are not very helpful. 7. When requested or when red errors reported or when requested please do the following: With LINDA 3.1.x and later Select Maintenance page. Click on Turn ON Fault Diagnosis Mode button. With previous versions Go to LINDA Setup page. Tick Developer Mode, GUI and LUA boxes. Select VERBOSE from the download menu. Open Console. IMPORTANT. You may need to remove a block on logging in FSUIPCx.ini. You need to open it in the editor and search for the line LogOptionProtect and change it to NO. You will need to restart FSX/P3D after doing this. Then Restart your Flt Sim and LINDA. Ensure that SYNC TO SIM is selected (aircraft outlined in orange). Run Flt Sim to reproduce error. Close down everything. Email FSUIPCx.LOG and LINDA2.LOG files (in /modules/ folder) together with the config-hid.lua or config-mcpX.lua for the aircraft you are using to LINDA @ awginfosys (dot) net (remove spaces). NOTE: If you are sending .LUA files it would speed my analysis if you renamed the file to add a new .TXT extension. With this information I will try to offer help to get users flying with LINDA.

I'm as useful at coding as an eye dropper at a forest fire. I'm trying to perform a simple toggle: Toggle open/close the front door Note:the default FSX door toggle key command map does not work in this plane and I do not want to use a mouse for this Is anyone good at Lua coding FSUIPC that can help please? The LINDA code below works with a button within LINDA but I want to map a keyboard press within FSUIPC. function DC6_ExitFwd_open () ipc.writeLvar("dc6_446_obj", 1) DspShow ("Frnt", "open") end function DC6_ExitFwd_close () ipc.writeLvar("dc6_446_obj", 0) DspShow ("Frnt", "clse") end function DC6_ExitFwd_toggle () if _tl("dc6_446_obj", 0) then DC6_ExitFwd_open () else DC6_ExitFwd_close () end end

Several LINDA users have reported incompatibility problems with Device Cannot Be Opened and other errors. Unfortunately, despite detailed investigation and analysis of the source code, I have been unable to identify the source of the errors messages or the cause. Certain touch screens and pads seem to feature in the reports. The devices identified so far are: Synaptics Touch Pad (vid 1532/pid 002b) - part of Razer SWTOR game keyboard Touch Computer (vid 04b4/pid c001) Viewsonic TD2420 (vid 0408/pid 3008) Elo Touchsystems (04e7/pid 0050) If you have experienced any similar problems then please report them together with their device VID/PID numbers. See separate post on how to identify these details. Please state the version of Windows (7/8/8.1) you are using. With hands-on access to one of these devices I am unable to take the investigation forward. If you live in the UK and are prepared to loan me your problematic device, please PM me.

Hello All For some time now I have been using LINDA with my Saitek switch panel, Yoke & VRInsite MCP . Great tool, thank you Guenseli. But eventually I thought that it was time to add more buttons and switches. I decided to buy an Open Cockpits i/p, o/p board and build it myself, having had some experience with electronics and software, no problems except that I soldered all the diodes the wrong way round. Everything working ok, programmed most of the switches and lights with SIOC to operate via FSUIPC. But,as I a fly several different types of aircraft and it's not easy to detect in SIOC the aircraft currently in use. So, I used LINDA to write a bit to a user byte in FSUIC which I could then detect in SIOC. Each user.lua sets a different bit (Boeing, Airbus, default, ..etc). That was a bit better. But programming in SIOC is so... time consuming I though there has to be a better way. So more study and research. I thought to write LUA code to be run by FSUIPC. I looked at writing my own app and running it in LUA/FSUIPC but then I thought much of the code is already available in LINDA actions.lua but I don't want to touch that. After much trial and error and searching I found the lib-user.lua Just what I need. I don't need to write my own routines everything is available from here. So what now happens. All that SIOC does is operate one of the virtual joystick buttons in FSUIPC , e.g. # SIOC code Var 0994, name JoyStick1, Link FSUIPC_OUT, Offset $3340, Length 4 // Joystick address Var 0169, name SetJoyBtn, Link SUBRUTINE { IF &BtnSet = 1 { &JoyStick1 = SETBIT &BtnNumber } ELSE { &JoyStick1 = CLEARBIT &BtnNumber } } -- one variable for each button Var 0170, name PBtn1, Link IOCARD_SW, Device 3, Input 8, Type I { &BtnSet = &PBtn1 &BtnNumber = 1 CALL &SetJoyBtn } Var 0171, name PBtn2, Link IOCARD_SW, Device 3, Input 6, Type I { &BtnSet = &PBtn2 &BtnNumber = 2 CALL &SetJoyBtn } Var 0172, name PBtn3, Link IOCARD_SW, Device 3, Input 7, Type I { &BtnSet = &PBtn3 &BtnNumber = 3 CALL &SetJoyBtn } These button events are caught by LINDA in lib-user.lua # LINDA lib-user.lua code function handleButtons(joynum, button, downup) -- call handler VButton_handler (joynum, button, downup) -- this fuction is in the user.lua of each airplane -- or you can handle each event separtely (globaly) here. if button == 0 then end if button == 1 then end if button == 2 then end if button == 3 then end if button == 4 then end -- etc end -- function -- events for virtual joystick buttons event.button(64,0,3,"handleButtons") event.button(64,1,3,"handleButtons") event.button(64,2,3,"handleButtons") event.button(64,3,3,"handleButtons") event.button(64,4,3,"handleButtons") event.button(64,5,3,"handleButtons") -- etc and sent to the button handler which is in LINDA user.lua # LINDA user.lua function VButton_handler (joyNo,btnNo,downUp) -- switch case would be nice here -- only joy stick 64 -- FSUIPC is from 0 .. 31, Linda 1.. 32 if btnNo == 0 then VButton_1 (downUp) elseif btnNo == 1 then VButton_2 (downUp) elseif btnNo == 2 then VButton_3 (downUp) elseif btnNo == 3 then VButton_4 (downUp) elseif btnNo == 4 then VButton_5 (downUp) elseif btnNo == 5 then VButton_6 (downUp) end -- etc end -- end VButton_handler This means that each aircraft in LINDA has its own set of actions for the aircraft currently in use and has full access to all the LINDA code. BINGO!!! Also all the user.lua code can be edited in LINDA editor. lib-user.lua should not need to be changed except for generic actions. I put the default settings in the templates/users/user.lua for any new aircraft. At the moment all my encoders are working ok, but I think I might try write something to be able to control them better in lua. What would be 'icing on the cake', if it was possible to assign functions to the virtual joystick buttons from the LINDA interface, but I realize that that is not quite as simple as I first thought. :wub: My thanks to Guenseli and Peter Dowson for there dedication and great support. Hope that this will be of use to others A very happy Carliolian

Hello, Could you help me please ? How can i use functions who are in actions.lua through FSUIPC ? actions.lua from : http://www.avsim.com/topic/341971-pmdg-737-ngx-module-47-new/ Example in FSUIPC : Key presses : SET : CTRL + J >>> NGX_PUMP1_AFT_toggle or Buttons + Switches : SET : 1 >>> NGX_PUMP1_AFT_toggle Thanks for help. PS : i have create a specific FSUIPC macro for the test, but i dont want do this for each function. PMDGBaseVar = 0x00011000 -- 69632 PMDG_ClkL = 0x20000000 -- 536870912 PMDG_ClkR = 0x80000000 -- -2147483648 PMDG_dec = 0x00002000 -- 8192 PMDG_inc = 0x00004000 -- 16384 PMDG_RelL = 0x00020000 -- 131072 PMDG_RelM = 0x00040000 -- 262144 PMDG_RelR = 0x00080000 -- 524288 function NGX_PUMP1_AFT_off () if ipc.readLvar('ngx_switch_37_a') ~= 0 then ipc.control(PMDGBaseVar+37, PMDG_ClkR) DspShow("PMP1", "Aoff") end end function NGX_PUMP1_AFT_on () if ipc.readLvar('ngx_switch_37_a') ~= 100 then ipc.control(PMDGBaseVar+37, PMDG_ClkL) DspShow("PMP1", "A on") end end if ipc.readLvar('ngx_switch_37_a') == 100 then NGX_PUMP1_AFT_off() else NGX_PUMP1_AFT_on() end PS : i have also test an include in lua MACRO file !? But dont still work ? require("scripts.actions") NGX_PUMP1_AFT_toggle() end Thanks for advance; Sky

Using LINDA 2.8.6 FSX-SE FSUIPC 4 I have coded several switches to manipulate LVars in an MFD I coded for the Lear45H aircraft in FSX-SE. The functions are in the aircraft folder in user.lua. This is the file path: C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\linda\aircrafts\Lear45H\user.lua Other files in that folder are: actions.lua ExtPFD-Learjet.exe ident.lua Lear45H-user.lua The code in the start of the user.lua are: -- Dummy user functions file -- =========================== -- This file is loaded right after main actions.lua script loaded. -- You can use this file to: -- 1. Override any functions or settings in main script -- 2. Execute any desired startup sequence for this aircraft (i.e. your own c&d state macro) -- 3. ... use your imagination -- Just a message in console _log("[uSER] User's modifications script is loaded...") ident = ipc.get("PATH_ACFT") .. "/Lear45H-user.lua" if file_exists(ident) then _log("[sTART] Functions found: " .. dir) require(ident) else _log("[sTART] Error not found Lear45H-user.lua: ") end strProgram = '"C:\\Program Files (x86)\\Steam\\steamapps\\common\\FSX\\Modules\\linda\\aircrafts\\Lear45H\\ExtPFD-Learjet.exe"' if file_exists(strProgram) then _log("[sTART] Lear PFD found: ") strCmd = 'start "" '..strProgram os.execute(strCmd) else _log("[sTART] Error not found Lear PFD: ") end function L45E_FMS () _L45E_FMS () end function L45E_NAV () _L45E_NAV () end function L45E_HSI () _L45E_HSI () end The Functions for example _L45E_FMS () are located in Lear45H-user.lua. These functions were assigned in the LINDA GUI and were contained in the User Functions drop-down when the Lear45H aircraft was selected. config-user.lua -- ## Jet Joystick ## (073822370) ## {NoSerNum} ############ JSTK["073822370"][1]="Brakes" JSTK["073822370"][5]="Flaps_up" JSTK["073822370"][6]="Flaps_incr" JSTK["073822370"][7]="Gears_toggle" JSTK["073822370"][301]="Trim_ELEVATOR_up" JSTK["073822370"][303]="Trim_AILERON_right" JSTK["073822370"][305]="Trim_ELEVATOR_down" JSTK["073822370"][307]="Trim_AILERON_left" -- ## DTA Pulse ## (16D004890) ## {NoSerNum} ############ JSTK["16D004890"][1]="L45E_HSI" JSTK["16D004890"][2]="L45E_TAC" JSTK["16D004890"][3]="L45M_Btn1" JSTK["16D004890"][4]="L45M_Btn2" JSTK["16D004890"][5]="L45M_Btn3" JSTK["16D004890"][6]="L45M_Btn4" JSTK["16D004890"][7]="L45M_Btn5" JSTK["16D004890"][8]="L45M_Btn6" The LINDA Lua editor showed a few errors which were corrected. When I open the aircraft in FSX-SE, everything seems normal, except I see no log messages from the user.lua file and apparently neither the Lear45H-user.lua module nor ExtPFD-Learjet.exe were loaded. I get an error when I pressed a button in the DTA Pulse HID. The LINDA Console displayed and the FSUIPC Log file contained the following: 13562 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 13562 Initialising SimConnect data requests now 13562 FSUIPC Menu entry added 14640 \\DONNADAVEKITCHE\Users\DaveDonna\Documents\Flight Simulator X Files\Lear KAVL.FLT 14640 C:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\Lear45H\Lear45.air 32125 Weather Mode now = Theme 36922 Aircraft="Learjet 45 CAF" 36937 System time = 19/01/2017 14:38:05, Simulator time = 14:37:59 (19:37Z) 125297 Starting everything now ... 125359 Using "C:\Program Files (x86)\GoFlight\GFDEV.DLL", version 2.2.6.0 125375 LUA.0: beginning "C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\ipcReady.lua" 125390 LUA.0: ended "C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\ipcReady.lua" 125640 LUA.1: *************************** STARTING LINDA ************************** 125656 LUA.1: LINDA:: [sTART] Loading System Configuration files 125765 LUA.1: LINDA:: [sTART] WARNING - All LUA logging switched off !!! 125781 LUA.1: LINDA:: [sTART] Go to Setup LINDA to switch on (if required) 125797 LUA.1: LINDA:: ********************************************************************* 126062 LUA.1: LINDA:: [sTART] System Configuration files loaded 128843 Advanced Weather Interface Enabled 148125 *** LUA Error: ...\common\FSX\modules\linda/aircrafts/Lear45H/user.lua:40: attempt to call global '_L45E_HSI' (a nil value) 204265 Sim stopped: average frame rate for last 83 secs = 8.5 fps Can you help me find what I am doing wrong? I cannot find in the LINDA GUI where to turn on the log but assume any _log function call would put the message on the console and in the FSUIPC log. The folder Lear45H was created using the LINDA GUI with the default FSX aircraft as a pattern. I was getting an error that the action.lua file was missing until I copied it from the FSX Default folder to the Lear45H folder. Thanks

Hello guys, how are you? Weel, I just bought a VRinsight FCU-COmbo, and I'm losing my head tryng to make this work. I think that something so expensive must be easyer to install. My isso is that the FCU dos not work on P3d. Here goes some info: P3D version 3.4.22 Linda 3.0.5 Aerosoft module 4.4 v3 FSUIPC 4.973, with the original registration key. Well, I did the MCP configuration on linda based on the manual, He finds the FSUIPC normaly. I first run linda as admin. I change the aircraft to Aerosoft Airbus, and sync. I open the P3D, with a default aircraft. I change the aircraft to any Airbus from Aerosoft. I go back to linda and change again the aircraft to aerosoft, but, and here cames the problem, when I click on SYNC, linda says LINDA not sync-ed to the FLT SIm. Anybody can save me? BEst Regards!

Hello guys, I'm currently building my own G1000 hardware with arduino due. I'm using P3D v3.2 and carenado 172SP G1000 as software. I am able to use LINDA for most of PFD's function. My problem is now reading / writing input for direct-to on PFD. I use LINDA tracer and get following Lvar activated when using direct-to button and outer FMS knob: TMP_PFDScratchpadIndex, PseudoScratchpadIndex, PFDSCRATCHPAD_TEMPORAL_INDEX, G1000_EnteringInput My problem is when I rotating inner FMS knob (from carenado VC) to enter airport / navaid into direct-to page, I couldn't get any Lvar or FS control reacted to the rotation. Any idea how to access scratchpad from LINDA ? Thank you. Best regards, Nikko

Hello, Maybe it's been written before but i can't find it. my problem is that i can't send signals to p3dv4 with my combo II(Boeing). i've tried everything what is possible the weird thing is that if i change something in p3dv4, it changes on the combo to but not the other way. i use the latest updates for fsuipc and linda. any suggestions? thank you already. regards, Kurt

Does someone have already a module for the amazing FMGS A320 for LINDA? I tried with the one provided 3 years ago at FMGS forum but with no luck. I can't establish any connection between my VrInsight MCP Combo II and the FMGS software. Any advises are also very welcome. Best Regards, Vic

Hi, here's a short introduction to how to create Mouse Macros in FSUIPC for use with LINDA. What is it: A Mouse Macro is kind of like a recorded mouse click, which you then later can replay to get the same effect. It normally works very well, but there are a few limitations: Not everything works with mouse macros. There is no simple rule for this, you will just have to try. The recorded marcros probably only works for the version of the plane they were recorded in. If a new version of the plane is released, then the macros need to be recorded again for that version. You can use a different livery without problems, but you will have to check to see whether different variants works with the same set of macros. You can only record macros with a full version of FSUIPC, so you will have to buy it. That should be a no-brainer. FSUIPC is the most important addon to get for FSX in my opinion. I have only tried to record macros in a virtual cockpit and in windowed mode. It may work in the other modes as well, I just haven't tried it. How to create a set of macros: Load the plane into FSX. Be sure that the buttons and dials you want to use are visible. Open FSUIPC from the addon dialog. In FSUIPC go to the "Buttons+Switches" page and click "Create Mouse Macro". Enter a file name in the dialog that shows up. Please use a name that is descriptive... Like "mjc8q400" which was the name used by Capt. Pero's macros for the "Majestic Dash 8 Q400". The file will be placed in "...\Microsoft Flight Simulator X\Modules". The same place where Linda was installed. After pressing Ok, you are returned FSUIPC. Press Ok here too; this returns you to the cockpit view. Now the magic starts. Right click, left click or scroll mouse wheel on the button/dial you want to record. Do exactly as you would when flying. When you do this a green or red window is shown (the colour does not mean anything, it just switches between red and green for each time you record a macro). This indicates that FSUIPC noticed you clicked on something. Optional: You can now press TAB to try the recorded macro. This will perform the action again. If satisfied, then enter a name for the macro (up to 16 characters) and press return. If not satisfied, press ESC. If you want to record more macros, then repeat from step 6 again. If you are done recording macros for now, then open FSUIPC in the Add-ons menu and go back to the "Button + Switches" page. Click "End Macro Making", then close the FSUIPC dialog and you are done recording the macros. That is all there is to it... Easy B) How to use a macro from Linda: To use the macro from Linda, you should create a function that "fires" the macro. I am not going to explain in detail how this is done. You can check out the Majestic Dash 8 Q400 for an example. See the contents of the actions.lua file in "....\Microsoft Flight Simulator X\Modules\linda\aircrafts\Majestic Dash 8 Q-400". Here is an example of a function firing a macro from that file: function AP_HDG_press () ipc.macro("mjc8q400: AP_HDG_press") end In the line above "mjc8q400" is the name of the macro file (leaving out .mcro), and AP_HDG_press is the name of the macro. That is, the name you typed in while recording the macro. Please, please: Try to decide on a systematic way to name the macros. It should be possible to figure out what each macro does just from this name. This makes it much easier to understand what happens when examining/writing the Linda file. It also makes it possible for someone else (or yourself for that matter) to re-record the macros later if a new version of the plane is released. The names of the Majestic macros is a good example. I was able to redo them with the new Dash 8 version based only on the name of the macros. For instance. What do you think the macro "AP_HDG_press" does? Well, it presses the HDG button on the Autopilot (AP). If Capt Pero had called that macro for "Coolname1" then I could not have re-recorded it easily Editing macros: You can edit the macro file with notepad; do not use Word or another word processing program. When you open the macro file, you can delete macros you don't want (maybe you recorded some by mistake), and you can rename macros if you think you have a better name for a macro or made a spelling error. Be sure not to modify the stuff after the second equal sign. That is FSUIPC's description of what you did when you recorded the macro. I always renumber the macros if I delete some. I don't know if this is necessary. Recording more macros: If you go into FSUIPC and start recording macros again with the same file name, then the macros are appended to the file if it already exists. Macro files can be used if they are in the modules folder. If you create some macro files just for testing, then delete them after use. Otherwise you use memory for a lot of macros that never are used. If you need more help, then ask, or read the FSUIPC manuals. Helge

Hi all. I had this Splash Screen hanging problem with FSX-S stopping on the initial splash screen and never loading from there. It was resolved by deleting the "logbook.bin" file within the Flight Simulator X folder inside My Doucments. If you want to find out how I am sure this was the solution to the problem in my case, read on. If not rename the logbook.bin file and let FSX create a new one on start up, back it up before deleting it, just in case. After experiencing this hanging on the splash screen error and finding no real help on the www, I decided a complete reinstall from Windows 10 up was in order. Cunningly, I made full system images at every step of the reinstall process using the native Windows backup tool. I installed all of my office programmes etc. first then set about Steam - FSX - FSUIPC - Linda - TrackIr before next setting about the Orbx scenery addons. After I had installed Vector and 4 patches, I decided to go flying as I missed it. A simple flight across 5 miles of the Isle of Wight in the default Piper Cub. Turned off the PC, went to bed, work, home, booted the PC and went to have a quick flight again before commencing the install of Orbx Europe etc. FSX hung up on the splash screen again, Impossible I was gobsmacked! But felt reassured that my painstakingly produced system image's would solve the problem. I set about using the last image created before Vector, taking me back to the full system state just before it was installed. I was even more gobsmacked to find out that even that did not solve the freezing splash screen problem But I realised that the only files that had not been replaced by the system image was in fact the Flight Simulator X files in My Documents folder. I ahd configure the system image file to replaced only drives C - F - G (Windows - Steam - FSX) whereas the My documents folder resided on my D drive and not on the image, the only files inside the Flight Simulator X folder were the Piper Cub flight and the logbook.bin files. I deleted the logbook.bin file attempted to start FSX and all was well again, it worked a treat Game on. Promptly I used the Image of Vectors install state to quickly get back to where I was and the newly created logbook.bin file worked a treat there as well, there was no problem with anything just the logbook.bin file. Reading through some forums I found some great help and advice but none of it worked for me. I only came across 1 thread that indicated deleting the logbook.bin file was an option. But did not believe it. Now I am convinced, blow me down who would have guessed it? on a newly created install Windows 10 up. I hope this helps someone out there, knowledge of this file's corruption when all is newly installed let alone an old installation could save a lot of time and effort, hence the reason to explain how I came to realise this was right for me at least. ALWAYS backup or rename the suspect logbook.bin file before deleting it, you will loose your pilot and flight records in FSX if they are not already lost, but that a welcome exchange in my opinion. That said one could always keep a back up of it so an uncorrupt copy could be copied over, I found the recycle bin is a great place to store these back up files, right up until the time you forget and empty it. Hope this helps someone out, lets go fly. A big thank you to the person who said delete the logbook.bin file, you were right, I am sorry I did not believe you.

I have recently answered several queries from owners of the original VRInsight MCP1 panel. They report that LINDA is not working with their MCP1 with advanced aircraft like the PMDG 737NGX and Aerosoft Airbus A318/A319/A320/A321. The reason is twofold. First, the config-mcp.lua file has been generated from the default aircraft configuration for SPD/HDG/ALT and these are not suitable for more complicated aircraft like PDMG and Aerosoft products. You need to go through the specific module menu and assign functions specifically written for your aircraft. Second, because your MCP panel is no longer sold, neither I nor Guenselli, have this panel to create a specific config-lua.default file for MCP1 users. However, I have been working on this problem. Using 2.9.x there is now a method of copying the MCP2 configuration to work with your MCP1 panel. The procedure is as follows: Open LINDA and manually select PDMG737NGX or other aircraft from the dropdown. Go to Setup MCP. Select MCP2(Boeing) and save. Select the Combo MCP page. Click twice on the EFIS Mode 3 tick box at bottom (or make any other change) to highlight save button. Hold down CTRL key and click on SAVE. You will see a confirm message that MCP1 config-hid.lua file has been created. Go to Setup MCP and change back to MCP1 panel and save. Start your flight sim and load the above aircraft. Select FSXSync ON (orange box). You should now have functioning SPD/HDG/ALT knobs and buttons. Please note that not all LINDA aircraft modules will have a config-mcp2.default file. The default aircraft supplied with your flt sim (eg. Beechcraft 58) will work with the default functions included in the default template and the library LIB-FSX Default.

Hello everybody, So...I need some help. I recently installed Linda 3.0 on my pc in order to be able to use more features of the aerosoft a320 through the buttons of my joystick and throttle quadrant(planning later on to build a command box with rotary encoders and other buttons) . The only problem is that it doesn't work. I have installed the Aerosoft Airbus A318/19/20/21 v1.31, FSUIPC 4.858 and linda 3.0.9. I downloaded from AVSIM the aerosoft airbus module 4.4 v3. When I try to assign commands to buttons in the joysticks section initially the command is red but when I save becomes black(when I do it for FSX standard planes it becomes green but still doesn't work). Do I have something wrong installed? Do I do something wrong? Please help. Thank you in advance. Cristian