Conao

Ok, got it. Thanks for a quick reply.

I downloaded a new version of a StreamDeck profile from internet and it comes with the corresponding group of scripts for AAO. What is the correct procedure to update this script group with the new version? Do I have to delete the old version and import the new one again or the import will overwrtite the existing one, automatically adding new scripts and updating existing ones? If I have to delete the old one, would that break any existing assignments for Axis and Buttons?

Hi! I'm trying to connect my old MCP Combo 1 to MSFS 2020 using LINDA 4.0.8.195 and FSUIPC 7.2.14. Yesterday, I installed all these latest versions and also VRiSim to find out what COM port to use. I followed the instructions in the LINDA Downloads post, observing the order to start the applications, and it worked. I had problems trying to change assignments, but let's leave this for a future step. For now, my problem is that today the MCP didn't connect to MSFS 2020. I observed the same order to start the applications, did it several times, rebooted the computer, re-checked the COM port and the configuration in LINDA and that FSUIPC was connected. The LCD displays were not updated by LINDA as they normally should and no response from any button. I'm using the MSFS Default aircraft profile with the default C208. Should I follow the Fault Diagnosis Procedure and send you the log files? I probably don't have to follow the whole procedure because I believe the problem is not with an aircraft profile or assignments. It appears it simply didn't connect at all. Anyway, just let me know how can I help you to help me. 🙂

No worries, fair enough. I just had to give it a try... 😉

Ok, clear. Thanks! Any chance the logbook could save the vertical speed on touchdown? There're many apps doing it now, dedicated add-ons or flight trackers, such as FSHub, Volanta and SimToolkitPro but, honestly, after trying most of them, I keep going back to the combo LNM + Navigraph for all my planning, tracking and logging. Of course, this excludes the online maps, but this is not my thing. LNM is a fantastic application, full of everything I need (and way more) for planning and tracking, and now I discovered it's a great logbook too. The only info I'm missing in the logbook is the landing data. It would be great to have it and skip all those other softwares. 🙂

I'll take a ride on this post instead of creating a new one... I tried the logbook feature today, for the first time. It looks great, with lots of information! However, I could see the aircraft's horizontal trail in the Map window, but not the vertical one in the Elevation Profile window. Is the trail recorded in the logbook limited to the horizontal track only or am I missing something?

Hi Andrew! I tested the updated beta version and I can confirm that it works well and finds all aircraft now, both in the Community and in the Official folders. Thanks for your support and for this great tool! /Marconi

Ok, I sent you the log file.

Ok, I see. So, it seems that LINDA cannot find my MSFS standard aircraft folder, right? Well, it's in the same Packages folder as my Community folder, which LINDA can find. The path for an standard aircraft is like this: D:\FSim\MSFS\Packages\Official\Steam\asobo-aircraft-c152. The path for an addon aircraft is like this: D:\FSim\MSFS\Packages\Community\C208B-mod I checked the linda2.log file and it found the right Packages folder: [MAIN] [ADDON] Flt Sim Path valid ++++ D:\FSim\MSFS\Packages\. I can also see that it checked every sub-folder under the Community folder ([MAIN] [ADDON] Checking Folder = Community) but absolutely nothing under the Official folder ([MAIN] [ADDON] Checking Folder = Official). Any idea why could that be? I uploaded the log file to the same dropbox folder as the pictures, in case you want to take a look in it. You can use the link in the post above. Thanks a lot for your support, much appreciated!

Thank you for such a quick reply, Andrew! It's good enough to use the default functions since these are default aircraft. However, the process you described to create a dummy module is exactly what I was trying to do (I guess), but it didn't work. If I type anything else in the "Aircraft search string" box than one of the add-on aircraft listed in the box below, none of the buttons in this window get enabled, except for CANCEL. Am I misunderstanding you? Here're a couple of screenshots of what I tried to do: https://www.dropbox.com/sh/lu37qf0zdf8gkqi/AAC-i-FZM3ITwCQgBnFowVnPa?dl=0 By the way, just to confirm, the assignments of the MCP Combo are also aircraft specific, right?

I always loved LINDA! It made it possible to use my Saitek Switch panel and MCP Combo, as well as made it easy to configure joystick assignments for different aircraft. But this was in the FSX days, when I basically only used add-on aircraft. Now that I'm using MSFS I noticed that it doesn't seem to be possible to create different sets of assignments for different MSFS default aircraft. Is that right? I mean, for instance, the assignments for the MSFS B787 must be the same as for the MSFS X Cub? I tried to create a new module, but I can only select from the list of add-on aircraft in the Community folder. If that's the case, the profiles in MSFS are actually more flexible, although, also limited (no support for Saitek panels configuration or the VrInsight MCPs). In the end, neither LINDA nor MSFS profiles are solving the problem. Is doing all the configuration in FSUIPC the only complete solution? Am I missing something or is it the way it is, i.e. we can create different assignments only for add-on aircraft?

Hi Scot, Thanks for your reply. The assignments that you suggested are exactly what I had in my config-hid.lua file, which I had already copied from the config-hid-saitek.lua file. But it simply doesn't work. It seems that LINDA completely looses communication with FSX when the Carenado BARON 58 module is selected. It communicates with the hardware, as I can see my buttons presses being indicated in LINDA, but nothing happens with the sim. Since it works fine with the FSX Default module selected (although I only have the basic commands), I decided to make a test where I replaced the Avionics assigment from the B58 library with the one from the FSX Default library in the Carenado module. I expected it to work, since it worked when the FSX Default module was selected, but it didn't. Hence my conclusion that it seems to loose communication when the Carenado module is selected, since even commands that work from other modules with this same aircraft, stop working. Or shouldn't it work anyway? Assuming that I have done all the installation and configuration of LINDA correctly (all my other aircraft are working fine), what else could be wrong with this module only? Regards, Marconi

Hi, I installed the Carenado Baron 58 module today but couldn't get it to work. No commands from any of my devices (Saitek Yoke, Saitek Switch Panel and VRi MCP1) make any changes in the aircraft. Actually, it works much better if I remove the module and use the default FSX assignments, many of them work with the Carenado B58. I renamed the file config-mcp.default to config-mcp.lua and copied the Switch Panel assignments from the file config-hid-saitek.lua to the file config-hid.lua (not sure I should do this, but it seemed reasonable to do it). The assigments show up in LINDA, but have no effect in the aircraft. My other aircraft are working fine with LINDA, including the Majestic Dash8 and the PMDG 737NGX. Any ideas about what could I have missed for exactly this aircraft? . Linda v2.8.3 . Module: Carenado BARON 58 v1.1 . FSX SP2 . Aircraft: Carenado Baron 58 (I guess the latest version) Regards, Marconi

Hi, Shouldn't the files in the "linda-cfg\aircraft" folder be under a folder named "\Carenado BARON 58", like all other aircraft files? I think there's something wrong with the installation zip file. /Marconi

It appears that Majestic uses their own code for radios, not standard FSX (read it in a forum somewhere, maybe this one). Hence the MCP Combo radios don't work with the aircraft's ones. A pity... Marconi