madfred

Just found this post. So sorry to hear about Roy's passing. I had the pleasure of meeting him many years ago at the FSWeekend at the Aviodrome in Lelystad, the Netherlands. We spoke about the B-25J he developed. I have had many years of joy out of that airplane. Rest In Peace. you will be missed.

+1 Would love to be able to use AviaCDU with the ATR. Am already enjoying it for the currently supported FS2020 planes ;)

Another very nice paint job, Don. Just added it to my hangar

Thanks for the paint Ron, Downloaded and will take it for a spin in the morning, Jan, As usual another great cockpit. Looking forward to it

I use Plan-G, FS Commander, and Active Sky Next on a networked computer. Each has a manual that explains how to set that up. Just take the time to read, and you will be okay.

Ron, I too am looking forward to that repaint

Lee, Butchering a site, run by flight sim enthausiasts, for being overloaded due to a highly anticipated release is not really the way to go. I was lucky to be able to download the c-47, but have yet to successfully post in the thread. Being registered or having donated does not make any difference. I am convinced that you are not "blocked". You just have to have patience, like so many others. So, step out of the heat, have a glass of iced tea, and breath.Life does not end because we have to be patient. I am sure you will be able to enjoy the new C-47 release soon.

So last night (yeah really "NIGHT" LOL) I could not resist and and started up my flight simulator computer to give this update another try to see if I could get the device labels back. As stated earlier, I have a backup of the modules folder from before the 2.8.1 update. First I edited the FSUIPC.ini file to remove the [VRINSIGHT] listing that was added by Linda, after hitting the fix button. Followed the steps as listed in the install, and made sure ALL devices were connected. Loaded FSX and Linda and all was working except still no device names. Closed Linda, added the system/config-hid.lua file again. Reloaded Linda again, and..... Hurrah!! there are my device names. No idea why I had to add that file twice, but it did solve my issue. One thing I would suggest to be added to the Installation instructions, is to mention having ALL devices connected before upgrading to the new version. This was never an issue in previous versions, but certainly is important with version 2.8.1. Again, thanks for a great product.

Thank you for the prompt response. There was one device (joystick) unplugged, as I had the yoke plugged in. I never have then plugged in at the same time, as they will interfere with axis inputs.It has never been a problem with previous Linda updates. But I was going to give your suggestion a try. Result: no more device error, besides the MCP error. But only some assignments were working, even though none of the assignments were showing on the joystick page (similar to another post from someone on this site) So I went back again (for the x'ed time, lol) and cleared all files and folders related to Linda from the modules folder. Then pasted the 2.8.1 version in the Modules folder and added the Linda and Linda-cfg aircraft backup from the 2.6.7 version. Loaded FSX-Acc and Linda. Getting the error that the device config file could not be found. I closed Linda, and added the system\config-hid.lua from the 2.6.7 backup (which does have the device names listed.) Now all assignments are working again, but the device names are all "UNKNOWN". Guess naming the devices no longer transfer's with an update, and we should also make sure to back up the Linda-cfg/system/config-hid.lua file. Also, if you do not have an MCP combo, Linda will throw an error, and you will have to reload Linda to enable the devices.

Hello, First of all, congrats with the 5 year anniversary. I installed the new Linda 2.8.1v1 after removing all linda files and folders from the Modules folder.(YES, I did back up the aircraft folders). After copying back the linda and linda-cfg aircraft folders, I loaded up FSX-Acc, chose the default Cessna 172, and after loading the flight I started Linda. An error popped up stating that the device config file could not be found, Linda Tracer is grayed out. and the MCP states there is an error (I do not have an MCP). I have Linda fix the FSUIPC(even though I don't think there was an issue with the FSUIPC.ini file) The joystick settings show that the devices names that I preset are not being read, and also the Serial numbers are gone, After re-entering the device names, I can re-assign functions, but all the original custom assignments are gone. I can revert back to Linda 2.6.7 with no problems.

I purchased the 377 +COTS as well, as the sale was too good to pass by. It is certainly a "Study" aircraft, and I love the thought of what the Connie will be in the light of that. By the end of this Summer I will have to take at least a month off from work, to dig into my most favorite aircraft, being: 1) Manfred Jahn's DC-3/C-47 with Jan Vissers VCC, and TuFun's sound pack, 2) A2A's Constellation. 3) PMDG DC-6B And by then I hope to have mastered the 377 + COTS, which is a masterpiece on it's own.

Gonna try setting up the msflights.net software and will attempt to join. is that 7pm UTC? I will probably be flying the D-2, or MJ's C-47

Since last Christmas I am a very happy owner of the GoFlight MCP Pro. I fly the PMDG 737NGX, and am surprised every time I add an aircraft to the hangar, that I can use the MCP with it, even on simple freeware aircraft. I am loving this mcp so much, that I don't understand how I have been able to do without it for so long. My next purchases will be the GoFlight EFIS, and one or two GF-166 modules for N AV and COM radios

I am getting the same error, and last time it happened was this evening as I clicked to undock a panel in the PMDG 737NGX. Closing the error box, and re-loading Linda seems to keep linda working fine after the error.

I am certainly going to try and join.