LeoSchoonbroodt

Sorry John, Only just now i see your other questions from Yesterday so i will try to answer them here Why are you running luas when MSFS is in the main menu? FSUIPC7 only fully functions when you have an aircraft loaded and the camera system is out of the menu system. The ipcInit.lua should only be used for any one-off initialisation you need to perform, it should not wait for events. The ipcInit.lua just monitors Planeselection change and updates an offset that is monitored by a wideclient, but i could move this to another lua started by ipcInit.lua but i don't see the difference. The only thing this Wideclient does at this moment is display the many functions of Switches of my cockpit for the selected Aircraft (which are different for each Aircraft) to give the possibillity to set switches as they should be for this Aircraft before the Aircraft is loaded and the Auto lua starts and reads those switchsettings. Especially important for warmstarts as you can imagine if switches are in wrong positions, the Aircraft may shutdown. I could reprogram the Wideclient lua's to monitor the offset "3D00" and would not use ipcInit.lua anymore, but it always worked this way. Are you doing this outside of the main menu? FSUIPC7 should not process button assignments when MSFS is in the menu system. Yes, i can manually load the Aircraft lua only when the Aircraft is loaded and do this when the "Checking for Aircraft auto's" doesn't load the lua which sometimes happens. The buttonmapping is in the profile file for the Aircraft which is only loaded once the Aircraft loads. Also used this in the past while developing the lua's to reload a modified lua after making changes without always having to go to the main menu If it happens again that the auto lua isn't loaded i will attach the logfiles. But again thanks for your help with the above problem. Leo

Hi John, Your advice was exactly to the point. I switched the WASM LvarUpdateFrequency back to 6Hz and removed it from the [WAPI] section of FSUIPC7.ini and now all works as before. No inaccessible FSUIPC7-window or very slow responses anymore and no Error entries in the FSUIPC_WASM.log. Don't know when this double LvarUpdateFrequency is put into the [WAPI] section of the FSUIPC7.ini but it could only be me who did it, just can't remember when and why. Anyway, thanks for your help, going to enjoy my flights again 😂 Leo

John, tried with LvarUpdateFrequency=0 and now the FSUIPC_WASM.log doesn't contain those errors and i got no errors indicating WASM stopped in the FSUIPC7.log. Especially did for a short flight with an Aircraft that makes a lot of Lvar reads. So far so good. Didn't think about testing if the FSUIPC-window was normally accessible in the main menu but will certainly test this tomorrow. Still wondering how these errors suddenly happen as the LvarUpdateFrequency has always been 6Hz in my configuration, but for now it works. Thanks for your help, hope for happy flying hours again cheers, Leo

Hi John, Used as sugested LvarUpdateFrequency=0 but no change. Started MSFS and created flight from KLAS to KLAS, so far all good. BUT after: 185250 10080 Lvars/Hvars received - checking aircraft autos.... nothing happened anymore so i had to load the Aircraft lua manually again via a buttonmapping in the ini file. After that everything seemed to work correct up to 1161516 4548 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Also the 5 second regular check for transponderstate by using DataCalculatorCode failed, for me an indication that WASM was not running anymore. So i had to Disable and re-Enable WASM again through the Add-on menu after which everything worked fine again. Also noticed that the FSUIPC_WASM.log again had almost 6000 entries of [ERROR]: Ignoring request to update LVARs as updated internally So nothing changed so far i can see. This is something from the last versions as i had this never before and my configuration didn't change. Will try another flight but now with another Aircraft although i don't see how thwt could help but doing nothing is also no option. Hope this will help to pinpoint the problem. EDIT Sorry, just see that i i set the LvarScanFrequency=0 instead of the LvarUpdateFrequency=0 My mistake, so forget about this post, will try another one with correct settings Leo Logs.zip

John if i look in the logs then i see 647719 23128 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! 647828 7668 [ERROR]: Error setting Client Data Calculator Code [-1073741648]: '(A:TRANSPONDER STATE:1, number) (>L:TransponderState)' if i then Disable and re-Enable the WASM again via the Add-ons-menu, (see 658563 and 920828) everything worked again. in the last FSUIPC7.log i had to do this twice, after which all calculator code worked again and I could normally end my flight. This indicates to me that the WASM stopped and had to be started again which was the original bug you repaired or do i see this wrong? The only WAPI client i have is FSUIPC, i dont use any other modules that query the FSUIPC_WASM and the setting in the FSUIPC_WASM.ini was -2, so once every 2 seconds. But i will try with LvarUpdateFrequency=0 Will report back to you after that.

And another one, have the feeling it's getting worse instead of better. Another question, how can i disable WASM logging? I tried by setting it to Disable in the FSUIPC_WASM.ini in the persistant storage and in the modules fsuipc-lvar-module folder, but that seemed not to work as can be seen from the logs. Logs.zip

Hi John, Problem of WASM stop still present, see logs. My other problem (FSUIPC-Window not accessible), still present, but only when in main menu, during Flight this is accessible normal. Have seen that FSUIPC_WASM.log contains about 5000 lines "[ERROR]: Ignoring request to update LVARs as updated internally" for a short flight. Although it's logged to an SSD drive could that be the culprit of FSUIPC-window not accessible? and when so, why then only in main menu? Leo Logs.zip

Hi John, Have a flight logged with examples of this FSUIPC7 hanging Started MSFS and when in main menu selected another Aircraft (Schweizer) as seen at 144297 BUT ipcInit.lua doesn't execute the plane change Did some screenshots of Taskmanager, FSUIPC window and Console and as you can see from taskmanager FSUIPC is at more than 10% and this for minutes long while the CPU is barely around 36%. Only when lost focus to MSPaint for saving a screenshot suddenly ipcInit executed the planechange Then when starting a flight at 731234 FSUIPC all looked normal until Checking for Aitcraft lua's which did not load. I also have seen this several times with older versions. After waiting for 118 seconds i loaded the Schweizer.lua manually from a Buttonbinding in the ini file and as this worked, it's an indication that FSUIPC is alive, but (maybe doing other tasks until interupted???) From there on everything looked correct but i finnished to save the logs. btw i provided an exit in all Aircraft luas when Plane parked and OnGround because if not autostarted it will also not be killed. Above description happened several times last days and fwiw i got the feeling the problems always happen if FSUIPC is idle for some time but that's only a feeling. For completeness i also included the ipcInit.lua, the Schweizer.lua and the Schweizer.ini Leo FSUIPC SLOW.zip

Hi John, I have a problem that my WASM stops during flight. I have seen it before and cannot be certain it started with this latest version but this time i have it logged with the Extra logging option. Noticed it because i could switch on the wipers via calculator code and some time later couldn't switch them OFF. Looking at the FSUIPC-Console i found a lot of errors indicating that the WASM was not running anymore, so to test this i disabled and re-enabled it via the menu and the errors ceased and all started working again. I attach the FSUIPC7 and WASM logs. Another thing i have seen in the past days is that FSUIPC menu's are sometimes not accessible and FSUIPC seems to hang when in the main menu, and then after some time starts working again, but i have no clean logs when that happened as i tried several things to get it working again which might confuse the matter, but thought to mention it as i am not sure if it's related, If it happens again i also will provide those logs Leo Logs.zip

A quick update on Version 7.4.8b Did 3 complete flights and some more starts with different Aircraft which gave problems before, now all running fine. Will do some more flights tomorrow. Leo

Hi John, Glad that you found it. 👍 Meanwhile i did 3 short starts and all went well. Start now using the latest one and will report back if something happens. Have a nice evening, Leo

Will use version with Empty check, Don't have a lot of time today but will report back as soon as something goes wrong or if all stays well probably tomorrow as by then i should have had enough starts to confidently say that it's fixed cheers

John, I am sorry but also this last version has caused the [Buttona] section of the FSUIPC7.ini to be missing. also here there is a button with line 1000 detected at the very begin but at the end the buttonsection was gone again. I attached the FSUIPC&.ini and log files. First flight with the H145 went well, then selecting the Cabri end at the end was missing the section again. Leo FSUIPC7.log FSUIPC7.ini

Will use the new version and post logs if it happens again. Attached files were from last flight with previous version so don't know if they are of any value but attached them anyway. Leo FSUIPC7.ini FSUIPC7.log

OK, send you the log when it happens again, could take a while as yesterday a few flights were OK. Leo

John, Yes the Schweizer was from the last flight Yesterday evening and today i switched to the Bell407. No Assignment window opened at all. When i mention during flight i really meant to say "somewhere before end of the flight" As i use only a few buttons from the buttonscreen which are captured by an Buttonevent in the lua script. In the FSUIPC7.ini i mostly have buttons assigned which are used before any lua script is running and a few others seldom used ones. So i found out at the end of the flight when i tried to end the flight with the Esc and End buttons from the buttonscreen who are defined in the FSUIPC7.ini Is it a possibillity to make the FSUIPC7.ini and profile files ReadOnly which should then generate an error for a write attempt so we have an indication where it happens. I realise i can't make any assignments then but this is anyway something i do only when modifying something?

Hi John, Problem of clearing [Button] section still present. Did yesterday evening two flights which went well. Today my first flight worked EXCEP: Buttons defined in FSUIPC.ini didn't work In short: TEST 4 MSFS started Aircraft Bell407 selected Aircraft Bell407 loaded ALL SEEMS TO WORK WELL EXCEPT: Buttonscreen buttons defined in FSUIPC7.ini NOT WORKING ButtonScreen buttons captured by Bell407.lua WORK CAUSE: [Buttons] section from FSUIPC.ini gone MUST HAPPENED DURING FLIGHT AS: Here still present 63703 25912 Button changed: bRef=0, Joy=6 (M), Btn=28, Pressed 63703 25912 [Buttons] 1000=PM,28,C1003,31 63703 25912 FSUIPC Control Action: Ctrl=1003, Param=31 At Ending Flight with Esc/End buttons from ButtonScreen (defined in FSUIPC7.ini) NO ACTION Research found [Button] section missing from FSUIPC7.ini Leo FSUIPC7.ini FSUIPC7.log

Restored all from Backup and had another testflight with latest version. All worked normal so will continue flights with this versions logging enabled and will post the logfile if the problem happens again cheers

At this moment the client has only the button screen. Buttons in the profile are all on the server machine, the device connected on the client died some time ago and was disconnected and not replaced anymore. About the 2 joystick devices those are not in use anymore and detached. At this moment i hesitate to make any changes that may complicate troubleshooting as it has always worked this way, but i definitely cleanup my ini file one of these days

will try tis version in about an hour and a half, wive called for dinner and i want to keep her happy😇

OK here are the profile files i used during testing. All button linenumbers above 1000 for buttondefinitions come from FSUIPC7.ini Lower than 1000 come from profile files. I have anyway the idea that it's intermittend as the first flight with the Schweizer worked and the last flight didn't and if you say this version 7.4.8a only added additional logging then the other conditions are the same. Also because yesterday the main problem was that profile auto lua's were not loaded and i have never seen that today. Now the main problem seems to be that buttondefinitions from the profile files are not loaded. FSUIPC7.ini CabriG2.ini Schweizer.ini Bell206.ini

Yes, i switched Aircraft several times to see if it was Aircraft specifioc. I don't have the logfiles from earlier flights anymore but i past you my Journal with notes that i kept since the additional debugging options. TESTS WITH DEBUG EXTRA OPTION =============================== TEST 1 MSFS started ButtonScreen use Aircraft Schweizer selected Aircraft Schweizer loaded EVERYTHING WORKS TEST 2 MSFS started ButtonScreen use Aircraft Cabri selected Aircraft Cabri loaded EVERYTHING WORKS TEST 3 MSFS started ButtonScreen use Aircraft Bell206 slected Aircraft Bell206 loaded Lua Loaded as Arduino's are initialized Buttons defined in Bell206.ini Don't work BUT Bell206.ini is loaded as [Auto] Bell206.lua is loaded Several times Button & Switches reload from menu without result AT END when pressing ESC and END buttons from Buttonscreen (Defined in FSUIPC7.ini): these work Also enormous amount of Axis data in log, could this hinder Button detection??? Have seen that when i enable lua logging, it is almost impossible to use the simulator NEW Version of FSUIPC7.4.8a ============================ TEST 1 MSFS started ButtonScreen use Aircraft Schweizer selected Aircraft Schweizer loaded Lua Loaded as Arduino's initialized Buttons defined in Schweizer.ini NOT working Buttons defined in FSUIPC7.ini working Buttons from buttonscreen working Enabled lualogging from one of those and to see if enabled switched some undefined commands in the homecockpit on and off. Do find this in the logging: RECEIVED: ZZ696720 NOT RECOGNISED/EXECUTED btw. all buttons above 1000 are defined in the FSUIPC7.ini, those work

Sorry forgot to submit my previous reply. Meanwhile a did a testfly with version 7.4.8a and got the same result. lua loaded but buttons in profile ini file not. buttons in FSUIPC7.ini loaded See attached logfile. FSUIPC7.log

Yes i will try this version. It's a strange problem, Yesterday any first flight didn't load the profile lua, didn't matter which Aircraft and successive flights were always OK. Today my first two flights went very well, no problem using Buttonscreen before flightload lua and ini file loaded. First one with the Schweizer second one with the default Cabri. The third flight with the Bell206, the lua was loaded as i can see that my Arduino's were initialized but when i tried to use the buttons defined in the Bell206.ini they didn't work. Did several reloads of Button & Switches via the assignments menu to no result. Then when i gave up and used the Buttonscreen's ESC and END buttons, those worked. So for me an indication that only buttons in the Bell206.ini were not working. I send you that logfile in case you want to have a look. FSUIPC7.log

Yes it's loaded in the [Auto] section of the profile. The correct profile ini file is loaded otherwise i couldn't manually load the lua as this button is defined in the profile file i will add logging today and will send you the files. Leo