dougfir

Pete, I'm not familiar with "the MSFS window problems". John has answered the problem. Edit the .ini file as well as the script.

More on my first lua foray, page 1 of the FSUIPC Lua Plug-Ins.pdf reads "When you start a Lua program running which is already running, the previous incarnation is first ruthlessly and unceremoniously terminated. " I found this not to be the case. I edited my previous test script and then invoked it again from the same Key Assignment but the previous code would always run. I was just trying to change the window position and size. I finally had to quit both the sim and FSUIPC7 and restart in order to see the new script. I hope I'm missing something here, that would be a really tedious way to code.

Further to my post above I redid the key assignment leaving out the "Alt" key. So "D" alone triggered the script and this worked. Is there some problem using "Alt" with Lua and MSFS2020?

I'm missing something about running a Lua script.. I'm using a registered version of FSUIPC7 v 7.1.0 with MSFS2020 I modified one of the provided lua examples and named it "IASDisplay.lua" and put it into the root FSUIPC7 folder. In my FSUIPC7.ini file I have: [LuaFiles] 1=IASDisplay Under the Assignments menu I assigned Alt+D to run LuaIASDisplay I run FSUIPC7 which starts MSFS2020 and shows Connected. Everything looks normal but using Alt+D does not start the script, at least not that I can see. FSUIPC7.log shows "KeyDown received from FS but not programmed" but in Key Assignments it shows that script assigned to Alt+D. So, I'm looking for a way to start the script, either through the FSUIPC7 Assignments menu or through MSFS2020's Controls dialogs. Log attached. IASDisplay Script: w = wnd.open("IAS", WND_FIXED, 100,100,425,185) -- Update the display at 1000 msec intervals (see event at end) function mytimer(time) -- display 1 = airspeed airspeed = math.floor((ipc.readSD(0x02BC) / 128) + 0.5) --display.show(h, 1, "Airspeed " .. airspeed .. " knots") wnd.text(w,airspeed) end -- Adjust timing to taste: 1000 = 1 second event.timer(1000, "mytimer") Thanks FSUIPC7.log

Additional info to the above problem. From fsuipc.log appears may be a simconnect problem: 94 System time = 11/10/2016 11:28:53 94 FLT path = "E:\Docs\Flight Simulator X Files\" 94 ------ Module Version Check ------ 94 acontain.dll: 10.0.61472.0 94 api.dll: 10.0.61472.0 94 controls.dll: 10.0.61472.0 94 fs-traffic.dll: 10.0.61472.0 94 G3D.dll: 10.0.61472.0 94 language.dll: 10.0.61472.0 94 sim1.dll: 10.0.61472.0 94 visualfx.dll: 10.0.61472.0 94 weather.dll: 10.0.61472.0 94 window.dll: 10.0.61472.0 94 ---------------------------------- 125 Trying to connect to SimConnect Acc/SP2 Oct07 ... 141 FS path = "G:\FSX\" 235 ---------------------- Joystick Device Scan ----------------------- 235 Product= Saitek AV8R Joystick 235 Manufacturer= Saitek AV8R Joystick 235 Vendor=06A3, Product=0461 (Version 1.18) 235 Serial Number= Saitek AV8R Joystick 235 ------------------------------------------------------------------- 235 LogOptions=00000000 00000811 235 ------------------------------------------------------------------- 235 ------ Setting the hooks and direct calls into the simulator ------ 235 --- CONTROLS timer memory location obtained ok 235 --- SIM1 Frictions access gained 235 --- FS Controls Table located ok 235 --- Installed Mouse Macro hooks ok. 235 --- Wind smoothing fix is fully installed 235 --- G3D.DLL fix attempt installed ok 235 --- SimConnect intercept for texts and menus option is off 235 --- All links checked okay 235 ------------------------------------------------------------------- 235 SimConnect_Open succeeded: waiting to check version okay 235 Trying to use SimConnect Acc/SP2 Oct07 235 Opened separate AI Traffic client okay 1579 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 1579 Initialising SimConnect data requests now 1579 FSUIPC Menu entry added 1610 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 1610 G:\FSX\FLIGHTS\OTHER\FLTSIM.FLT 1610 G:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 1891 Memory in use: 570Mb, Avail=3526Mb 8563 G:\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR 8563 Weather Mode now = Theme 8563 e:\docs\flight simulator x files\c172 narrows.FLT 9094 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 9516 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 20907 Aircraft="Cessna Skyhawk 172SP Paint1" 20907 System time = 11/10/2016 11:29:13, Simulator time = 11:39:27 (18:39Z) 23844 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 26704 Starting everything now ... 26704 Note: "G:\FSX\Modules\PFCFSX.DLL", Error 126 (The specified module could not be found. ) 26704 Note: "G:\FSX\Modules\EPICINFO5.DLL", Error 126 (The specified module could not be found. ) 26735 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 68954 Memory in use: 1097Mb, Avail=2999Mb 69032 **** No SimConnect events or states being received! Re-connecting now ... **** 69141 SimConnect_Open succeeded: waiting to check version okay 69141 Opened separate AI Traffic client okay 111360 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 111360 Initialising SimConnect data requests now 111360 FSUIPC Menu entry added 111438 C:\Users\user\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 112407 System time = 11/10/2016 11:30:45, Simulator time = 11:39:31 (18:39Z) 112579 Advanced Weather Interface Enabled 114969 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y Note the time at line 20907: 11:29:13 Then @ 69032 no simconnect, re-connecting Then @ 112407 we are up and running @ 11:30:45 about a 1.5 minute delay which is what I'm experiencing. Anyone know how to troubleshoot simconnect? I have the standard 3 simconnect.dlls in the PC that appear after initial FSX install and the SP1 and SP2. John

Weird problem, let me explain. Also I see Pete is out until mid October so I hope someone else has some ideas. First, new Windows 10 64 bit PC, new FSX (box) install, FSX works ok. Normal behavior: start FSX, load C172, any field, active runway. I use the windowed mode and as soon as the scenery finishes loading and I see the aircraft on the runway, FSX is completely active. Meaning I can move my joy stick, throttles, switches, move the window around,see the prop spinning, etc.. Now, if I load a registered copy of FSUIPC (tried v 4.946 and the latest 4.957) and then start FSX with the same aircraft, field, etc here is what happens. Scenery finishes loading, you see the aircraft but everything is frozen, props are not visible but you can hear the engine running. You cannot move the window nor activate any controls, no action at all for about 1 minute. After 1 minute or so, everything resumes normal operation, prop spins, controls work, etc. It is as if FSUIPC is looking for something, loading something ... I have nothing set in FSUIPC, just stock as it comes after an install. Weird. I can reproduce this every time with the only variable being whether or not the fsuipc dll is in the modules folder. Any ideas? Thanks John