kaha

It happened again, here's the log file. FSUIPC7_log.zip

I did not iconify the window. However, I hadn't coded a wnd.close for the terminate event. I did that now and will see if it happens again. In the screenshot you can see which "Restart" I did. Also I attached a screenshot of the event viewer. I will

Sometimes FSUIPC just quits without obvious reasons. John, this is just to let you know, it doesn't happen frequently. Here's what I did this time: - startup the sim (and automatically FSUIPC) - load Icon A5 and do some assignments and checks in FSUIPC - go back to Main Menu - load Carenado C182RG - do several starts and landings - go back to main menu - start another flight with the Carenado C182RG - did a "Restart" when 5 minutes into the flight. After the restart FSUIPC was not running anymore. I attached the logfile. Karl FSUIPC7_prev.log

Ok, thanks.

Yes, the function is there, I implemented it. But why does it report then that there are still open COMs?

John, from this I assume the script that still has open COMs is HIDSwitch.lua and all other scripts don't? 610765 Killing aircraft lua Autos.... 610765 Lua threads being terminated: 610765 7 = "C:\FSUIPC7\L_Teensy.lua" 610781 Waiting for lua threads to process termination event.... 612968 LUA: "C:\FSUIPC7\L_Teensy.lua": killed 612968 8 = "C:\FSUIPC7\L_Throttle.lua" 612968 Waiting for lua threads to process termination event.... 615171 LUA: "C:\FSUIPC7\L_Throttle.lua": killed 615171 9 = "C:\FSUIPC7\L_Mixture.lua" 615171 Waiting for lua threads to process termination event.... 617359 LUA: "C:\FSUIPC7\L_Mixture.lua": killed 617359 10 = "C:\FSUIPC7\L_Prop.lua" 617359 Waiting for lua threads to process termination event.... 619546 LUA: "C:\FSUIPC7\L_Prop.lua": killed 619546 11 = "C:\FSUIPC7\HIDSwitch.lua" 619562 Waiting for lua threads to process termination event.... 619984 **** DevCom read/write threads still running - will exit anyway but could cause issues... 620296 **** DevCom Read thread terminated 620375 LUA.11: HidSwitch ends....... 621765 LUA: "C:\FSUIPC7\HIDSwitch.lua": killed 621765 Stopping WAPI (as MSFS in main menu)... 621890 [INFO]: SimConnect_Close done Would you need the .lua script? FSUIPC7_log.zip

Thank you!

Ok, as soon as it happens again I will send the log.

Today I made two flights with the Shorts 330.On the second flight I got error messages: "**** InputEvent received but not known: ....." in FSUIPC.log and "...Error sending Input Event 'LIGHTING_GLARESHIELD_1'" in the log of my lua script. The errors about input events are in regard to interior lighting. I did not change anything in my script, the errors just came unexpected. I then exited to the Main Menu and made another flight with the Shorts. Everything worked again. I attached FSUIPC.ini, FSUIPC.log and the log of my lua script. Karl Karl_InputEvent_errors.zip

Sometimes lua scripts that reside in the [AUTO] section of the .ini file keep running when the flight is ended and I go back to the Main Menu. This happens since recently only, maybe introduced with version 7.4? Is there a reason for it?

Thank you, John.

Alos, I cannot get "Pan Heading" working on an axis.

For some reason I struggle to get it working. For all 8 external quickviews I see the same camera view from behind the aircraft.

Thank you John. I'm on a flight right now but will use the new .exe then. Karl

Sorry John, it works. I made a mistake with testing. The .ini file is ok.

There's adifference to the old .exe: As long as FSUIPC is running the parameters show correctly in the Buttun Assignment window when changing to different switches. In the old version it showed zeros only. But after ending FSUIPC the .ini file stills is not updated, it still shows zeros.

In [Buttons] its nr. 61 to 64. The corresponding .lua files are in the .zip together with the .log files which don't show an error. Karl Karl.zip

Thank you, Karl

I also tried to edit the .ini file, but it getss reverted. Karl

I cannot find controls for external quickviews for Button and Switch Assignments. Here's what I mean displayed in MSFSs control options. THank you, Karl

Test your input event with the button assignments and then take a look at the input events list from the log menu. Use this for the lua script. In my example I use input event ELECTRICAL_Battery_1. Here is the lua script: --[[ Battery 1 for Caribou 1 = on 0 = off ]] ipc.execInputEvent("ELECTRICAL_Battery_1", ipcPARAM) Is your input event really named B:LIGHTING_PANEL_1_Inc? The input events I see in my aircraft don't start with B: ... DHC4_ENGINE_Propeller_1<> DHC4_ENGINE_Propeller_2<> ELECTRICAL_Alternator_1<> ELECTRICAL_Alternator_2<> ELECTRICAL_Battery_1<;FLOAT64> ENGINE_Throttle_1<;FLOAT64> ENGINE_Magneto_1<> ...

Was my fault, works now. The reason it didn't work was that I used a wrong parameter.

I also cannot get it to work. Karl

Also, sometimes the checkbox "Select for FS control" gets unchecked when looking at button assignments.

One strange thing: When assigning a lua script to a button the Parameter is not saved, it goes back to 0. Other lua scripts work. Renaming the script does not cure it. Not sure what's the reason. Here is a video (Dropbox link): https://www.dropbox.com/scl/fi/aumkxe9n18ero2cl99eqo/FSUIPC.mp4?rlkey=oqxlh23b6fss1gglyvcto5uh3&dl=0 Anything I can do, John? Do you need any logs or anything else? Thank you, Karl