LeoSchoonbroodt

No it doesn't happen always, and it indeed happens only when i go back to the main menu. I tried to kill the lua manually by reloading it, in the past but as far as i can remember this never was a problem. The reason i started a new one was indeed to only log the part where it happens, that's also the reason why i started logging when finishing the flight. If i start the logging earlier, it slows my system in such a way that the script misses a lot of button events. In fact it is unflyable. But i could start logging, load a flight and then whitout taking off go back to the main menu. Have to exercise this until i get a crash/hang. I included the FSUIPC.ini and the JS145.ini. Wil start above procedure and see if i get a crash/hang in which case i send you the complete log. Leo FSUIPC7.ini JS145.ini

i John Implemented the event.terminate and in this routine i close the com ports. Also implemented a check if a comport is open before sending data. Took a while because if i set lua-logging, my system becomes very slow, so slow that the lua script missed several events and could not get a hang of FSUIPC, unless i turned lua logging off. So i modified my JS145.lua to send less info to the arduino's (i think the sim updates some events at the fps rate and my script couldn't keep up with this) So i replaced some event driven data transfers to 250 ms (UpdateTimer) driven data and also cleaned up a little bit unused things, more for readabillity because the airplane is a work in progress and so is the lua file for it. Tested today and did a flight this afternoon with logging off and switched logging on just before return to the MSFS main menu, the point where it always happened I got a FSUIPC hang and include the log and the lua file (because it has changed). Hope this helps to pinpoint the problem. Leo FSUIPC7.log JS145.lua

Hi John, Will run this evening with Lua debugging. Display function is indeed not working anymore is still present (as a few other things) from a previous version when it was working. Wil allso use the event.terminate function and remove some other old stuf which isn't used anymore just to make the file more readable. After that will send you new information. Thanks so far for investigating things.

Hi John, Attached the lua file. It works fine mostly but sometimes when ending a flight I get this error. don't worry, no hurry, downloaded 7.2.11 today and until now still not happened. Also i don't know for sure if a plane change is needed for it to happen so in a few days i probably have more information about the conditions when it happens. will test further with 7.2.11 Thanks for your time investigating it. JS145.lua

Hi John, I have the registered version of FSUIPC7 v7.2.10 and Wideclient v7.160 When i end a flight and want to start another one, the lua file for the plane is not loaded and when investigating the matter it seems that FSUIPC isn't responding anymore. I have to end FSUIPC via taskmanager and start it again. In the log i find a lua crash error 7871063 LUA.1: Crash E06D7363 at 7FFB5FC24F99: "F:\FSUIPC7\JS145.lua" I do not get any errors in the lua editor and everything runs fine during flight. I included the FSUIPC logfiles. This happens a few weeks now, don't know exact time, because i first thought it was an incident and did not pay to much attention to it. Thanks for any advise to solve this. With kind regards, Leo Schoonbroodt FSUIPC7 Hang ending flight.log FSUIPC7_HANG AT AIRPLANE CHANGE FROM H145 TO R44.log FSUIPC7_hang.log

Thanks John, This one works!!!!

Hi Pete/John, Installed FSUIPC7 V7.2.5 yesterday and from then on cannot acces Lvar variables via my lua script. WASM is enabled but all other menu-items (except Disable) from the Add-ons/WASM menu are grayed out so i cannot list available Lvars. Via the standalone WASMClient works everything fine, here i can list and set Lvars.

Thanks, John, Yes I was refering to the undocked Instrument windows of MSFS. For FSX there was a program Simtimizer that could do this but that doesn't work anymore for MSFS. That's why i wondered if it maybe could be done with lua, but could not find anything about it in the lua-library docs. Would not give up wihout asking the expert though. Thanks for the nice program especialy the WASM extension of the beta is very useful. Regards, Leo

Hi Pete/John, Do you know if it is possible to readout the position and size of undocked windows with lua and then store it and restore them on a new startup, so to make this persistant? I looked in the lua library but are not able to find it, maybe i am overlooking it or it is indeed not possible. Thanks for your time and the great program.

John, your the best, I had the Model Behaviors window open to monitor the Lvar changes. I have closed that and restarted FSUIPC7 and it works all. I was indeed on version 7.1.0e, my mistake. Now everything worked!!! Thanks

Thanks John, Tried it but cannot access the Lvars with the FSUIPC7 version 7.1.0d althoug i have the WASM module installed, can access and set Lvars with the testclient and have enabled the WASM module under Add-ons in FSUIPC7. See that the other options in the WASM submenu of FSUIPC7 (List Lvars, List Hvars Set Lvar etc) are all grayed out, only disable is available. Also event.Lvar in my lua script is not triggered when the Lvar value changes, so i think i still have problems accessing Lvars via lua. I used the lua documentation from FSUIPC4 and FSUIPC7 extensively, was only missing Lvar documentation. Thanks for that.

Hi John, Where can i find this Lua Library ducumentation, the only Lua library documentation i find is the one i got with the registered version of FSUIPC7 but that doesn't mention Lvar support.

Me too, also make intensive use of Aircraft dependant lua files to setup and handle things. Eager to see this becoming available.

Thanks John, Had time to try the mobiflight WASM module and it solved my problem. Thanks for the tip. I also found a lot of other controls which were listed in the aforementioned document that are not working e.g. zoom and zoom_fine and many others. I asume this list was not checked to be valid? regards, Leo

Hi Pete and John, I can't use my buttons that are used for control of the G1000 which send the controls listed in "Controls List for MSFS Build 999.txt" Also ZOOM_IN and ZOOM_OUT are not working. These controls are listed in the "Controls List for MSFS Build 999.txt the log shows the cotrols beeing send but no action happens Is this list verified to be working? Sorry if this support request is transmitted more than once, because i was unable to login first an was not sure if it was send. Thanks for your beautiful program.

Tested it tonight and worked like a charme!!! My [button] area in the ini is a lot smaller now! Thanks for the tip!

Ok understand, thanks again. Have to dig up my old programming knowledge a little bit because that's long long ago. But think many examples can be found on Internet. Leo

Hi Pete, inrementing or decrementing 66C0 between 0 and 7 but only using value 0 and 7? Why not just have t toggline between 0 and 1? No, i am using all the values for Incrementing and decrementing the Scale of the ND Display as you can see from the linenumbers, I just didn't want to clutter the post with all these lines. Doesn't loading and executing a Lua plugin cost extra performance? The PMDG 737 eats already a lot of the performance of my system. Anyway thanks for your time, maybe i will start experimenting with Lua.

Hi Pete, Thanks for your wonderfull program. I have a (maybe dumb) question. In my FSUIPC.ini make use of the Cyclic Byte Increment and decrement functions to incr/decr. user offset, which i then use as conditions in Button assignments. But is it not possible to send the Value of this offset directly in FSUIPC.ini as parameter to the control assigned to a button press instead of using it as a condition which would save a lot of lines in my .ini file because i make extensive use of it. Also I don't like using LUA scripts, seems to me that this is at the cost of Performance (one more thing to load and execute). Fastest way is directly in the button assignment in my humble opinion. As example: 350=CP(+64,4)(+Y,8)(+Y,16)Y,2,Cx510066C0,x00070001 -{offset byte cyclic inc, offset 66C0 (Incr=1, Limit=7)}- 351=CP(+64,4)(+Y,8)(+Y,16)Y,3,Cx610066C0,x00070001 -{offset byte cyclic dec, offset 66C0 (Decr=1, Limit=7)}- 352=B66C0=0 CP(+64,4)(+Y,8)(+Y,16)Y,2,C69993,0 -{Custom control: <69993>}- ;EFIS ND Scale 353=B66C0=0 CP(+64,4)(+Y,8)(+Y,16)Y,2,C70049,0 -{Custom control: <70049>}- ..... 366=B66C0=7 CP(+64,4)(+Y,8)(+Y,16)Y,2,C69993,7 -{Custom control: <69993>}- 367=B66C0=7 CP(+64,4)(+Y,8)(+Y,16)Y,2,C70049,7 -{Custom control: <70049>}- 368=B66C0=0 CP(+64,4)(+Y,8)(+Y,16)Y,3,C69993,0 -{Custom control: <69993>}- 369=B66C0=0 CP(+64,4)(+Y,8)(+Y,16)Y,3,C70049,0 -{Custom control: <70049>}- ....... 382=B66C0=7 CP(+64,4)(+Y,8)(+Y,16)Y,3,C69993,7 -{Custom control: <69993>}- 383=B66C0=7 CP(+64,4)(+Y,8)(+Y,16)Y,3,C70049,7 -{Custom control: <70049>}- Wouldn't it be nice to replace it with: 350=CP(+64,4)(+Y,8)(+Y,16)Y,2,Cx510066C0,x00070001 -{offset byte cyclic inc, offset 66C0 (Incr=1, Limit=7)}- 351=CP(+64,4)(+Y,8)(+Y,16)Y,3,Cx610066C0,x00070001 -{offset byte cyclic dec, offset 66C0 (Decr=1, Limit=7)}- 352=CP(+64,4)(+Y,8)(+Y,16)Y,2,C69993,<VALUE OF B66C0> -{Custom control: <69993>}- ;EFIS ND Scale 353=CP(+64,4)(+Y,8)(+Y,16)Y,3,C69993,<VALUE OF B66C0> -{Custom control: <69993>}- Hope you can help me out here. Thanks anyway for your time and great program!