ScotFlieger

Broken Link fixed

Broken link fixed

I think there is a limit of 32 devices with LINDA. I would need to look into the code to give you a definitive answer but I am unable to do so at present.

Hi Cedric You should not have any difficulty with the Default FSX functions with LINDA 2.8.3, FSUIPC4 and P3D 3.2. The standard functions work for me with the default Baron 58. The only possible issues I can think of are that you need the full, paid version of FSUIPC4 or, if you are using P3D 3.3, there are issues with FSUIPC4 offsets. That said you say that you have PDMG 737NGX working.

I then suggest you manually added the correct serial numbers. I can't solve individual problems remotely. I have other work I need to get on with.

There is an issue with the Multi-panel display when using LINDA 2.8.3. It will be at least a month before I will have time to investigate the problem.

There are 2 config-hid.lua files (system and aircraft). Which one is showing NoSerNum? I was trying to say. You need edit your current default aircraft Joystick assignments and save. This should correct any errors in the aircraft file. The correct serial numbers should be recorded.

The reason that "analog" was displayed in the original error message was LINDA had assumed it was the device ID because proud are used brackets. It was looking and should have displayed 1DD210010. You can either manually edit your current files or go back to the dated backup before you named the card "Bodnar (analog)" . You need to ensure that the system config-hid.lua.lua (in linda-cfg\system\) has the correct device ID and corresponding serial number. After edit save file. The next time you change the Joystick for Default aircraft it should correctly formatted. I will add code next time to stop users pulling key characters into the device description.

I suggest you remove the brackets around the description (analog). As you will see the device is enclosed in round brackets and this is used to determine the right sections of the description.

I have not updated to P3D v3.3.5 yet so I can not test for this crash. Which version of LINDA are you both using?

The aircraft config-hid.lua file should include the Leo Bodnar device serial number. You can fix this by edited the file and replace the corresponding NoSerNum with the reported serial number. The initial position of switches is not reported to LINDA. You do need to operate at least one button on the device for the position to be recognised.

Glad you got sorted. All aircraft modules are under LINDA Downloads.

I understand there is a problem with 2D windows (something I don't use) which I have still to investigate. Please wait for next update.

Both 'features' described are normal for LINDA 2.8.3. The on-screen messages for LINDA starting and not to press any buttons until complete were added to stop some input runaways. The function queue is suspended during the reset. Assignment changes for each device should be saved before moving to a new one.

Sorry. My mistake. I AM the Aerosoft Airbus expert(ish). You will need to use the LINDA Tracer to look through the available LVars to see if the next waypoint data is available. It should be as it appears in the top right corner of the MFD.

LINDA uses FSUIPC4 and not SimConnect to communicate with the flight sims. I do not know enough about SimConnect to advise you. Perhaps you should look if FSUIPC4 can provide what you need.

Sorry I am not the PDMG module expert so I can not help with the offset you need.

Hi Moonwolf Welcome to LINDA. Do you have a particular aircraft in mind? You need to create a function in the aircraft's user.lua file (modules\linda\aircrafts\{your aircraft}\user.lua) along the lines of: function DropSmoke ipc.control(66658,0) -- droppable objects ipc.control(65559,0) -- smoke toggle end You will find the correct FSX Control code and param by using the LINDA Tracer and test by clicking SEND. I have not be able to test as none of my default P3D aircraft have droppable tanks or smoke. Then assign the function to the button required.

Es ist gut dass Sie das Problem gelöst haben. Es tut mir leid dass ich bin zu spat ihren zu helfen. Ich hatte die Tracer neu bearbeitet. (Bitte mein schlecht Deutsch entschuldigen).

Sorry for the late response. I have been away. LINDA has identified the MCP2a and run its initialisation. The CMDRST is required to initialise the VRi MCP2a so I don't understand how deleting it has solved your problem. I will need to investigate further.

Welcome to LINDA. You need a full, paid version of FSUIPC4 for LINDA to work. Please post questions under Support in future.

Hi Roland I am not experienced in Macros but I will have a look at your question when I get time. Unfortunately, I am extremely busy with my 'day job' and can not give any attention to it at the moment.

I do not use any Saitek drivers or software. Windows Device Manager should pick up your Multi Panel in any case. If it does not, there is something wrong with the hardware.

Thank you for the files you sent. As you suggested, your Multi Panel is not being detected by LINDA or FSUIPC4. In fact it is unusual for your system is trying to connect the Yoke and Pedals 3 times. I would open the Windows Device Manager and check that Windows is detecting the Multi Panel. It could be that it is faulty. Although the Multi Panel did not detect the Multi Panel, you managed to include a screen shot of its default assignments. I can not see the bottom icon and device name. Can you email me a screen shot of the Joystick Setup page with all devices plugged in. Also I would ask you to repeat the test and sent me the linda2.log and fsuipc4.log file. However, this time can you operate some buttons on each device and then close LINDA before copying the files.

Thank you for your report Mads. I have the same blank display both I had assumed that it was an hardware issue with my Saitek Radio Panel as it was intermittent. I will need to investigate further. Can you run a couple of tests for me? Start FSX:SE and LINDA. Goto to Setup LINDA and select Developer mode and Verbose logging. Also uptick the Saitek checkbox. Open up the Console and open \linda\system\common.lua in the Editor. In editor locate the function TestSRP, ensure function name in not highlighted and right click on the function name. This will run the self test on the Radio Panel. On mine I am only getting the AP buttons to illuminate. Click on Reload Lua Engine and email me the following files to [email protected]: \modules\linda2.log and fsuipc4.log.