Leftos

I decided to clean up shop a bit and get rid of all LUA scripts I wasn't using, and along with the changes you suggested, I had a stutter-free flight this morning. Thanks again, John.

Two separate add-ons on side-by-side ids, funny that: //42's Flow Pro, and GSX. Thanks for helping me track that down. I've made the logging changes you suggested, and hopefully that helps, so I'll report back. 428656 [INFO]: ID=2109 P42_FLOW_SET_OTTO_CENTERED = 0.000000 428656 [INFO]: ID=2110 FSDT_GSX_NUMPASSENGERS = 106.000000

Appreciate the feedback, John. I'll make those changes you suggested and report back.

I'm on version 7.4.17 (registered), and I notice consistent stuttering every few seconds, displayed as a spike in latency in the Dev Tools "Display FPS" display. Disconnecting FSUIPC7 immediately resolves the stuttering, which returns as soon as I reconnect.In the Dev Tools Console, I see the following lines spammed over and over, only when I'm connected: [DEBUG]: EVENT_LVARSET_REQUEST_RECEIVED: lvarId='2109', param=0.000000 [DEBUG]: Lvar with id=2109 set to 0.000000 [DEBUG]: Lvar with id=2110 set to 1.000000 [DEBUG]: EVENT_LVARSET_REQUEST_RECEIVED: lvarId='2110', param=1.000000 No idea if they point to an issue or if they're benign. I'm attaching my .ini and .log file as well. FSUIPC7.ini FSUIPC7.log

Just wanted to come back and report everything has been working flawlessly since the adjustments you recommended.

I exited MSFS, and seeing as the date modified of fsuipc_wasm.log is 5 hours ago, I wouldn't be surprised if this pointed to a WASM module crash. I did fly through complex third-party airports with the PMDG B738, so I could see that combo having been fatal for WASM. Interestingly, the last line in the wasm log was: Wed Aug 28 17:00:12 2024 [DEBUG]: Scanning for new lvars: lvarScanFrequency=-5, last lvarScanTime=1724864407567, timeNow=1724864412622 (difference=5055) which would indicate an issue with lvar scanning, as you said. In the wasm prev log, I see it ending with END OF PROGRAM, which reflects the fact that I had no issues with my LUA script or FSUIPC during yesterday's play session. This is all very useful, thanks John. I'll try the parameters you suggested in the ini in the persistence location and see if that helps. I can't attach the logs because they're bigger than 3.59kb even zipped, but I can put them in something like pastebin if it helps. Let me know.

I will say that it hasn't consistently stopped working. Most of the time it works, but then sometimes it doesn't for a whole MSFS session.

See attached.FSUIPC7.log

No worries, enjoy your vacation!

I have a pretty simple LUA script I've been using to monitor the PMDG 737 seatbelt switch position and also set it in the MSFS seatbelt offset, so that external apps can detect it, but for some reason, without the script having changed at all, it stopped working as far as reading the Lvar is concerned, and when I use the key binding I've added to restart it, FSUIPC7 hangs completely, and has to be killed through Task Manager. function setSeatbeltSign(varName,varValue) print(varName,varValue) if varValue ~= 0 then ipc.writeUB(0x341D,1) else ipc.writeUB(0x341D,0) end end event.offset(0x64FB,"UB","setSeatbeltSign") event.Lvar("switch_104_73X",250,"setSeatbeltSign") (I added the print just for debugging purposes after it started hanging) Originally I was only listening to the 0x64FB offset, which is the published offset for the seatbelt sign on the PMDG 737, but then I noticed that when using PilotsDeck / Stream Deck, the PMDG 737 profile I was using for it was reading from and writing into the Lvar, so I added that one too. I had a few flights where it all worked great, and whether I was switching the seatbelt sign using the mouse, or using my Stream Deck, I could see the change reflected in the external app that was watching for the 0x341D offset. Today, I couldn't get the Lvar to work (only flipping the switch with the mouse would be reflected in the 0x341D offset, while writing into the Lvar using the Stream Deck would be reflected visually in the plane's cockpit, but 0x341D would remain unchanged), and whenever I try to restart the Lua script using my keybinding (lshift+c), FSUIPC7 hangs entirely. I can't open its UI, Windows says it's "not responding", Mobiflight reports having lots its connection with it, and same with Passenger2. Let me know whatever information I can provide, and whatever steps you'd like me to try so as to debug this. I've attached my .ini. Appreciate your help. FSUIPC7.ini