jazzmanPL

And one more thing - uninstall all kind of software either fm VRI, logitech or whatever You use there as they may conflict with Your setup and You need nothing just SPAD 🙂

I fixed it today. Try to change Your com port. I assigned a different one and it works flawlessly 🙂 good luck In case of any problems, try to open the sim with and without FSUIPC as I observed it can freeze the sim when working together with SPAD also.. You can find me on discord or use the discord channel for SPAD as they have one of the most user friendly and efficient help service ever 🙂

I have the same problem. Have You found any solution?

Lets hope it works in January 🙂 anyway thanks for Your effort to keep it alive 🙂

Hi I have some problems with getting Flight to work. Seems like the servers are dead already. Can You confirm that? Is anybody still playing the game here?

I was able to install the game as fresh one with the key provided on win10. When starting it is showing only the 'FLIGHT' logo, however no starting up. Any ideas? Thanks 🙂

East or West, home's best :) Thanks for Your support Andrew.

Hi again, Back to the topic :) The issue came back, but I finally and definitely managed to find the clue. I have to admit I'm the guilty person and it was totally my fault. I'm really sorry for Your spent time. Anyway, I had to learn my lesson. Two days ago I spent few hours to clean all soft from windows startup and start FSX in clean configuration (I switched them off at SIMSTARTER NG run manager). After that I launched FSX directly with no addons and SIMSTARTER. As I'm using the X-56 and have to load X & Y axes after every windows startup (bloody new LOGITECH software) I focused on the axes and their assignment both in FSX and FSUIPC. I had some undesirable key and joystick assignments in FSX slew mode, so I cleared them all totally and assigned all necessary axes with direct input with FSUIPC (however left controllers enabled option in FSX - it turned out it makes no difference if they are not assigned). By the way FSX has an annoying tendency of enabling some assignments after reloading - anyway after few startups they were all clear. So I had the clean config and sim with no addons, but the problem still existing. And ta-dah!!! I found the missing link - my old "on repeat" assignments in Linda :) I used only "on press" and I had my pieces of brain focused only on that one :) After clearing those, all came back to normal. The plug got finally connected to the socket :) That's worth a nearby donation for LINDA :) And a sky-dive for me :)

Hi there, Small update on the issue :) The problem returned just by itself /pure magic/ however thanks to that I managed to find the clue. The murderer is the Logitech Profiler. When I switched that off NGX tends to run smoothly with no ghost around managing the instruments. I'll do a few tests and confirm this one. Cye

Merry Christmas from Poland :) Thanks for Your great effort and making our simming lives full of happiness :)

Countdown started :D

Wilco :) Anyway, thanks for rapid and detailed explanation on possible errors and for the solution of the problem. Linda is a great app and I cannot imagine using VRI MCP without it. So... ho-ho-ho and Merry Christmas :) Time to warm up the engines in peace :)

Hi Andrew, First of all, I like to thank You once again for Your support. I managed to operate LINDA with no errors following step 2 only. I launch fsx and all my addons (that means a lot :) with Simstarter NG. Linda was one of those programmes. I took it off the Run Manager and switched on manually before launching Simstarter..... and it is working smoothly. Apparently, there was some discrepancy beetwen those. I am using module 4.11 as I mentioned before. 1. I talked with Maarten about the error in the SLX_G1000.lua two yeras ago- this one may be of no significance: 2. Thanks for the advice :) I'm using Simstarter NG as the main launcher. Getting LINDA out of the Run Manager fixed the "sync to sim" issue. 3. LogOptionProtect was at "YES" all the time. 4. The error was only with PMDG 737 NGX module - I'm using also other PMDG, QWSIM, FSLABS, MAJESTIC and CARENADO aircrafts - all working great 5-6 The error is fixed, so please give me a note if You like to see the other error logs for gear and autobrakes. I can launch LINDA with SIMSTARTER NG once again and email the logs to You for any future purposes if You like. Best wishes :)

It happens every time when I switch on "sync to sim". NGX version is the newest also - 1.20.8465.

a

Ok Andrew thank You for Your rapid help and time spent.

Hello, Has anyone expierenced such a problem? After starting fsx and switching linda to sync to sim, my PMGD 737 NGX is getting crazy :) All the switches and knobs programmed with LINDA start to operate by themselves with no interaction from my side. Gear lever, spoiler handle, autobrakes knob, reverse thrust etc. I'm using the lastest LINDA version and the latest module for NGX - 4.11. When I switch off syncing, all comes back to normal, however I cannot use the buttons programmed with LINDA. I use FSX boxed with FSUIPC registered. No buttons double assigned. Help please :)

I'm not using any compatibility mode, just running fsx.exe as admin via SIMSTARTER NG.

I checked my p3d and it was working with no problems at all, but I got v4.0 and was not even updating to v4.1 :/ Hope that helps :)

coolken I'm using FSX boxed just because I spent most of my cash on that :) However I got P3D v4 also, but I'm not using that much. Will check the default P3D v4 and revert shortly.

32bit - 278.6MB 64bit - 510.9MB

Microsoft did their homework.Works flowlessly :) Started up with SIMstarter NG, works with LINDA, FSUIPC, PRO ATC-X, AS 2016, FS real time, UT Live, GSX and Chaseplane. No errors. Checked with PMDG 737 NGX. Windows update 1709 - KB4054517 (OS Build 16299.125). Happy snow-flying :)

No Santa, no update :) FSX RIP :P

Yeah :) Sorry for that :)

Got it working in beta after full reinstallation. Thanks for fast and reliable support. The windshield got foggy already ;) Happy flying :)