Glenn Weston

Very Clever Reinhard, I will keep that one up my sleeve.... Cheers Glenn.

Hi Reinhard, Good to see somebody else can see the benefit here, it sounds like you have done a similar thing to me. I can also independently disable particular modules that may not be required, by way of a CFG file, that also is in the Modules folder too under the current system. It is just a simple text file that all the Lua's read from to load variables etc. And I too experienced what you say about things getting slower as the Lua's get bigger and that also lead me to breaking it all up into smaller separate chunks. The Encoder modules that I have written require very fast sampling and cannot tolerate any other activity within the routine. Axes type modules also perform beautifully but again I require a separate Lua for each knob, so the files add up quickly. My Main Switch module has over 1700 functions, this includes cycle as well as commanded switch positioning that are otherwise not available for ALL multi position rotaries. As you say they can tolerate being all in a single Lua because it sits dormant most of the time and only event triggers when a switch is flicked, a human can't flick switches fast enough to see any real delay so as for a switch routine you can certainly get away with a single Lua. It is definitely when you want to be able to cater for ALL cockpit Knobs/Encoders that you really need to start breaking it up and the Lua count rises proportionately. And of coarse the Aircraft is ALL Lvars. There really is not any other way to do it. Profile support would be Awesome Pete, but your initial plan certainly will help me for sure and to keep it tidy. I imagine the profile support would also help with the limit of having only 127 Lua's Registered to the Pull Downs. I can tell you Pete that when developing I have hit the 127 Limit a few times and found myself scratching my head wondering why I could not find the Assignment in the pulldown, But I am well aware of that now and always keep a close eye on my number of Lua's in the Modules folder. I have to say the Lua system is very very stable and reliable, It is a great extension to the FSUIPC system. Any trouble that I have had with it is usually more my coding...LOL! Cheers Glenn.

Thankyou Pete, that is definately quite sufficient and would be fantastic. Thankyou once again. Cheers Glenn.

Thankyou Pete, I appreciate your consideration. All my Lua's are Pre-compiled and All are event driven and written so they are pretty efficient and never get called re-entrantly. For example all the Axes assignments are done via the luavalue assignment, so the Axes value gets passed to the module that is already running..... Otherwise as you say it would not be very good and more than likely cause something to crash, especially if had many Lua's being re-run over and over every time there was some axes jitter or something. The suite has been well tested by the community, not just myself. I have certainly used macros and attempted to interface using them but found them too restrictive. The Lua environment allows much better integration to control things and the Luas that may not be required by certain users can be disabled by the way of a configuration file. These are fairly complex and not just a basic routine, they include selectable on screen user diagnostic utilities, pre-scaling for axes modules, all of them read from a configuration file to get required variables and some pass variables to each other macro's just cannot do these sorts of things. So it is very much a Lua suite for a particular aircraft that is user configurable. So you can see why I would like to have them in there own folder. Thanks Pete for your great support as always. Regards Glenn.

Thanks for your reply Pete, Yes I can understand why you would ask how I could build up so many Lua's.They are all for one Aircraft. I have a very complex suite of Lua files that allow a full interface to the VRS FA/18E Superbug, The aircraft panels are completely built using Lvars.I cannot utilise any standard FSUIPC Controls to interact with any of the panels to control switches, knobs and rotary's, The Annunciator data for the lamps are also ALL Lvars.To interface my pit to this aircraft I have 68 Individual Lua Files, the other 44 Lua's are just ones that I have been fiddling and experimenting with and are just residual and can be removed, but they build up quickly when playing around. All the INPUT Lua's need to be assigned directly in FSUIPC pull downs to Axes for discrete knob control, Others handle Rotary Encoders, there is one main one that handles all the Toggle switches and push buttons for the aircraft. I need to be able to assign to all those via the FSUIPC Pull downs, The Annunciators are fine and certainly could be moved to a sub directory right now as they do not require any assignments but that is only 12 of them, that leaves 56 Lua's that are required to be in the MODULES Folder but I wanted to keep them all together in one place if possible, simply to keep things tidy, otherwise they function perfectly as is. I certainly understand that 32Bit (FSUIPC4) has come to a halt and can live with that, I could even Live with 64Bit (FSUIPC5) the way it is but it would be nice to have them separated, even if it was a SET folder that is hard coded in FSUIPC that could be scanned as well as the MODULES Folder. I know that many people these days are using Lua's more an more so it just might be a good idea to separate them and a logical step in the right direction, that's all. So if it is possible to have this as a requested feature in 64Bit and it is not too difficult to implement, I think it would be a great Idea. Mouse Macros are not the way I want to go as this is for pit building mouseless operation and definitely a NIL Virtual Cockpit environment. Regards Glenn.

Hi Pete, I would just like to ask the question if it is possible to have a sub folder under the Modules folder that gets scanned by FSUIPC for Lua file registration to the [LuaFiles] Section of the INI file. Either a pre defined folder, such as "Luafiles" for example or possibly a user definable one (or many would be better) that could be set in the INI file to host lua files, similar to the way one can define a Sound Files Path in the [Sounds] section of the INI file. The reason I ask is that I have quite a collection of Lua files in my modules folder and I would like to have them separated from the other files that are required to be in the modules folder. In the documentation it does say that you can have up to 256 Lua files registered , this would be rather messy if it were the case, I currently have a 112 on one of my systems so I am getting there.... So it would make sense if we could put them into cubby holes and keep it tidy. With many of the modern aircraft models it is becoming more necessary to run Lua Files to control things these days, so I could see this being useful for many users, not just myself. Cheers Glenn.

No that is the only thing that I read from the log file. It was just a quick and dirty way for me to find the full path to the modules folder. Regards Glenn.

Thankyou for the consideration Pete. I could certainly also go about it differently looking at Thomas' suggestions. I would just have modify my scripts to do that, so if it is a major issue I can always modify my side. Cheers Glenn.

Hello Pete, I Finally made the move to P3D V4.1 and purchased FSUIPC5. All went fairly well, and thankyou for your continued support. I just have noticed a small issue that is not a show stopper but it is something I refer to with one of my Lua Scripts to get the Modules folder location of the currently running FSUIPC. In Version 4 of FSUIPC the FSUIPC4.log contained the lines: ********* FSUIPC4, Version 4.947c by Pete Dowson ********* Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.ini" Running inside Prepar3D v2 on Windows 7 Module base=649C0000 In Version5 of FSUIPC the FSUIPC5.log file looks like this: ********* FSUIPC5, Version 5.122 (17th November 2017) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FEDB840000 As you can see the "Reading options" line is missing in the Version 5 Log file. I just wanted to point it out to you and hopefully ask for you too put it back in the log file on the next iteration of FSUIPC5. Thanks Pete Regards Glenn.

Hi Pete, 64Bit FSUIP5 is more exciting news than the actual P3D V4 announcement LOL !! As many would agree, your support here in the forum is second to none, and I will certainly be purchasing V5. You have applied many fixes for me directly as I have found small issues in the Lua facilities, sometimes overnight, I do not know any other developer who would do that. My Lua Scripts that I developed for use with the VRS Superbug, also known as Superscript rely heavily on the display facilities for end user assistance when configuring things in the scripts such as assignments etc. So it will be good if some sort of similar on screen display facility can be developed with LM to maintain a similar functionality, multi colours would be cool if possible. Looking forward to this very much and I have my Credit Card ready too, hope you had a great holiday with many more to come. Cheers Glenn.

Yes Oldpop,, not that I am aware of or have ever seen....... unless anyone else can offer any other suggestions. FSUIPC gives the ability to link a Joystick button to a Key Press, you can set it up so the button controls both the Key Press and Key Release events, so that should take care of it for you, as I mentioned above so that is currently probably the best route to take for now. Glenn.

Hi Oldpop, I will jump in here as I am the Author of the SuperScript Lua I/O package for the VRS FA18E aircraft. Mickey is correct, the VRS Radio's are VRS's own creation and sort of work outside the realm of FSX/P3D and most of the controls are done by Lvar for the radio. However VRS do tie their radio back to the FSX/P3D radio via simconnect so effectively when you carry out radio channel changes etc, you are controlling the Sim radio's in P3D/FSX, so there should be no problem there. As far as I know VRS do not supply a PTT Button or Variable for the Radios for TX nor does FSUIPC, the Controls you have mentioned 66463 and 66464 are purely to select the active TX Radio. These controls would be the same as the VRS KCM Commands "Control + Shift + 8" for COM1 and "Control + Shift + 9" for COM2 Using SuperScript these KCM options can be called with Parameter 40044 for COM1 and 40045 for COM2 but all any of these commands are going to do is change the Active TX Radio. I am assuming you are familiar with this documentation from the P3D site.....On how it all works. http://www.prepar3d.com/SDKv2/LearningCenter/getting_started/multiplayer/multiplayer_chat.html I think what you need to do currently is use FSUIPC to assign a joystick button to control the Keyboard DOWN/UP for the Multiplayer TX Keys on P3D. Have a look at the "Key Press/Hold" "Key Release" "Key Press & Release" in the FSUIPC Pull Down List, refer to the FSUIPC Documentation for the Key Codes to provide the correct parameters for the assignments. That should get you going, and this then will have nothing to do with what aircraft you are flying. Just a note for you in regards to SuperScript..... I have currently built another Lua module for SuperScript for the VRS Aircraft that is called a PTT_MANAGER. This module is purely for controlling ANY Voice PTT Activated client, such as TeamSpeak, any of the VATSIM or IVAO Voice Clients, Roger Wilco (if it is still used) and any other Voice Client that has assignable Keyboard shortcuts for the PTT Keys, so even the P3D Multiplayer Chat should work with it too.... BUT I have not released the Module as of yet and will be a feature of SuperScript Version 2.09, The Currently available release of SuperScript is 2.08 which does not have that module unfortunately. SuperScript is supported and maintained by myself and is hosted at http://www.hornetpits.org complete with a support thread. Some of the cool features of this new module are: Support for Dual or Single PTT Switch Allocation to both COM radio's Auto Radio Selection in the VRS Cockpit when in Dual PTT config. TX activation is sensitive to VRS Radio Power Knobs and will give Audible warning when trying to TX on a radio that is powered OFF. User settable TX Time OUT Timer, Audible warning at 5 Seconds prior to TX Timeout. User settable BIT Control for COM1 and COM2 within Custom Offsets 0x66C0, 0x66C3, 0x66C5 allowing for a real TX Lamp (Pit Builders) Optional on screen small TX Lamp Monitor so you know when you are on air, can be positioned in different locations on screen. So keep an eye out at hornetpits for SS 2.09........ Cheers Glenn.

Thankyou so much Pete !! Regards Glenn.

Hi Pete, I am having trouble trying the get the Lua Plugin logs to be created separately for each Plugin, I have used this facility before and I remember it was quite an easy thing to turn on in the Logging Tab, but I cannot not get it to work. I cannot tell you the last version that it worked on as I have not used the facility for some time, probably 6 Months or so but I tried to switch it on and cannot get the separate log files to generate. The Lua Plugin logging remains in the FSUIPC4.log file, so I can still see the logs there but I wanted them separated as I am running quite few plugins and it saves sifting through the data in a single file. I am running on FSX with all the latest patches and have just downloaded and Installed FSUIPC 4.948 to try and fix the issue but still cannot get it working. Below is a cut/paste of just the start of my main FSUIPC4.log so you can see the Log options that are set. I currently have all 9 ticked. Thanks Glenn. ********* FSUIPC4, Version 4.948 by Pete Dowson ********* Reading options from "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Module base=5B270000 User Name=************* User Addr=***************************** FSUIPC4 Key is provided WideFS7 Key is provided 15 System time = 08/11/2015 23:01:30 15 FLT UNC path = "\\SIM01\C_Drive\Users\Glenn\Documents\Flight Simulator X Files\" 47 Trying to connect to SimConnect Acc/SP2 Oct07 ... 47 FS UNC path = "\\SIM01\C_Drive\Program Files\Microsoft Games\Microsoft Flight Simulator X\" 203 ---------------------- Joystick Device Scan ----------------------- 203 Product= Joystick - HOTAS Warthog 203 Manufacturer= Thustmaster 203 Vendor=044F, Product=0402 (Version 1.0) 203 Serial Number= 203 Product= Throttle - HOTAS Warthog 203 Manufacturer= Thrustmaster 203 Vendor=044F, Product=0404 (Version 1.0) 203 Serial Number= 203 ------------------------------------------------------------------- 608 LogOptions=F0000000 0000001F 608 ------------------------------------------------------------------- 608 ------ Setting the hooks and direct calls into the simulator ------ 608 --- CONTROLS timer memory location obtained ok 608 --- SIM1 Frictions access gained 608 --- FS Controls Table located ok 608 --- Installed Mouse Macro hooks ok. 608 --- Wind smoothing fix is fully installed 608 --- G3D.DLL fix attempt installed ok 608 --- All links checked okay 608 ------------------------------------------------------------------- 608 SimConnect_Open succeeded: waiting to check version okay 608 Trying to use SimConnect Acc/SP2 Oct07 10826 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 10826 Initialising SimConnect data requests now 10826 FSUIPC Menu entry added 10858 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 10858 \\SIM01\C_Drive\users\glenn\documents\flight simulator x files\YSRI Ready.FLT 10858 \\SIM01\C_Drive\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\VRS_FA-18E\FA-18E-6.8_SE.AIR 11419 Memory in use: 654Mb, Avail=1394Mb 11419 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW 12028 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 10150 (0x000027a6) PANEL_ID_OPEN 12028 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 10150 (0x000027a6) PANEL_ID_OPEN 12028 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 10150 (0x000027a6) PANEL_ID_OPEN 12574 *** EVENT: Cntrl= 66598 (0x00010426), Param= 0 (0x00000000) VIRTUAL_COPILOT_SET 12574 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12574 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 79249 (0x00013591) COM_RADIO_SET 12574 *** EVENT: Cntrl= 66442 (0x0001038a), Param= 79249 (0x00013591) COM2_RADIO_SET 12574 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 69905 (0x00011111) NAV1_RADIO_SET 12574 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 69905 (0x00011111) NAV2_RADIO_SET 12574 *** EVENT: Cntrl= 66479 (0x000103af), Param= 16777216 (0x01000000) ADF_COMPLETE_SET 12574 *** EVENT: Cntrl= 66556 (0x000103fc), Param= 16777216 (0x01000000) ADF2_COMPLETE_SET 12574 *** EVENT: Cntrl= 65832 (0x00010128), Param= 0 (0x00000000) RADIO_VOR1_IDENT_DISABLE 12574 *** EVENT: Cntrl= 65834 (0x0001012a), Param= 0 (0x00000000) RADIO_DME1_IDENT_DISABLE 12574 *** EVENT: Cntrl= 65833 (0x00010129), Param= 0 (0x00000000) RADIO_VOR2_IDENT_DISABLE 12574 *** EVENT: Cntrl= 65835 (0x0001012b), Param= 0 (0x00000000) RADIO_DME2_IDENT_DISABLE 12574 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12574 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12574 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12574 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12574 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12574 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12574 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12574 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12574 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12574 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12574 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12574 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12574 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12574 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12574 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12574 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12574 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12574 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12574 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12574 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12589 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12589 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12589 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12589 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12589 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12589 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12589 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12589 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12589 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12589 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12589 *** EVENT: Cntrl= 65750 (0x000100d6), Param= 0 (0x00000000) PANEL_LIGHTS_TOGGLE 12589 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 12589 *** EVENT: Cntrl= 65554 (0x00010012), Param= 0 (0x00000000) ENGINE 12589 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 12589 *** EVENT: Cntrl= 65554 (0x00010012), Param= 0 (0x00000000) ENGINE 12589 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 12589 *** EVENT: Cntrl= 65538 (0x00010002), Param= 0 (0x00000000) SELECT_1 12589 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 12589 *** EVENT: Cntrl= 65554 (0x00010012), Param= 0 (0x00000000) ENGINE 12589 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 12589 *** EVENT: Cntrl= 65538 (0x00010002), Param= 0 (0x00000000) SELECT_1 12589 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 12589 *** EVENT: Cntrl= 65539 (0x00010003), Param= 0 (0x00000000) SELECT_2 12589 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 12652 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 1820 (0x0000071c) FLAPS_SET 12652 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 1820 (0x0000071c) FLAPS_SET 12652 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 1820 (0x0000071c) FLAPS_SET 12652 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 1820 (0x0000071c) FLAPS_SET 14461 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 3640 (0x00000e38) FLAPS_SET 14461 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 3640 (0x00000e38) FLAPS_SET 14461 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 3640 (0x00000e38) FLAPS_SET 14461 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 3640 (0x00000e38) FLAPS_SET 14461 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 3640 (0x00000e38) FLAPS_SET 14461 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 3640 (0x00000e38) FLAPS_SET 14461 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 3640 (0x00000e38) FLAPS_SET 14461 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 3640 (0x00000e38) FLAPS_SET 14461 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 3640 (0x00000e38) FLAPS_SET 14461 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 3640 (0x00000e38) FLAPS_SET 14461 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 3640 (0x00000e38) FLAPS_SET 23431 Weather Mode now = Theme 24118 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 24180 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 24320 *** AXIS: Cntrl= 66420 (0x00010374), Param= -16384 (0xffffc000) AXIS_THROTTLE1_SET 24320 *** AXIS: Cntrl= 66423 (0x00010377), Param= -16384 (0xffffc000) AXIS_THROTTLE2_SET 26255 System time = 08/11/2015 23:01:57, Simulator time = 11:30:57 (01:30Z) 26676 Aircraft="US NAVY Blue Angels #1" 27768 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 10150 (0x000027a6) PANEL_ID_OPEN 27768 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 10150 (0x000027a6) PANEL_ID_OPEN 27768 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 10150 (0x000027a6) PANEL_ID_OPEN 28252 *** EVENT: Cntrl= 66598 (0x00010426), Param= 0 (0x00000000) VIRTUAL_COPILOT_SET 28252 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 79249 (0x00013591) COM_RADIO_SET 28252 *** EVENT: Cntrl= 66442 (0x0001038a), Param= 79249 (0x00013591) COM2_RADIO_SET 28252 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 69905 (0x00011111) NAV1_RADIO_SET 28252 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 69905 (0x00011111) NAV2_RADIO_SET 28252 *** EVENT: Cntrl= 65832 (0x00010128), Param= 0 (0x00000000) RADIO_VOR1_IDENT_DISABLE 28252 *** EVENT: Cntrl= 65834 (0x0001012a), Param= 0 (0x00000000) RADIO_DME1_IDENT_DISABLE 28252 *** EVENT: Cntrl= 65833 (0x00010129), Param= 0 (0x00000000) RADIO_VOR2_IDENT_DISABLE 28252 *** EVENT: Cntrl= 65835 (0x0001012b), Param= 0 (0x00000000) RADIO_DME2_IDENT_DISABLE 28252 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 28252 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 28252 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 28252 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 28252 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 28252 *** EVENT: Cntrl= 66886 (0x00010546), Param= 3 (0x00000003) BLEED_AIR_SOURCE_CONTROL_SET 28252 *** EVENT: Cntrl= 65554 (0x00010012), Param= 0 (0x00000000) ENGINE 28252 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 28252 *** EVENT: Cntrl= 65554 (0x00010012), Param= 0 (0x00000000) ENGINE 28252 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 28252 *** EVENT: Cntrl= 65538 (0x00010002), Param= 0 (0x00000000) SELECT_1 28252 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 28252 *** EVENT: Cntrl= 65554 (0x00010012), Param= 0 (0x00000000) ENGINE 28252 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 28252 *** EVENT: Cntrl= 65538 (0x00010002), Param= 0 (0x00000000) SELECT_1 28252 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 28252 *** EVENT: Cntrl= 65539 (0x00010003), Param= 0 (0x00000000) SELECT_2 28252 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 28579 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 28595 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 1820 (0x0000071c) FLAPS_SET 28595 *** AXIS: Cntrl= 65698 (0x000100a2), Param= 1820 (0x0000071c) FLAPS_SET 29234 *** EVENT: Cntrl= 65568 (0x00010020), Param= 0 (0x00000000) HEADING_GYRO_SET 29234 *** EVENT: Cntrl= 65584 (0x00010030), Param= 0 (0x00000000) BAROMETRIC 29500 *** EVENT: Cntrl= 66720 (0x000104a0), Param= 0 (0x00000000) ANTISKID_BRAKES_TOGGLE 29671 Starting everything now ... 29687 LUA.0: beginning "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\ipcReady.lua" 29687 LUA.0: ...es\Microsoft Flight Simulator X\Modules\ipcReady.lua:1 29687 LUA.0: Global: ipcPARAM = 0 29687 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 30295 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 74576 (0x00012350) COM_RADIO_SET 30295 *** EVENT: Cntrl= 66442 (0x0001038a), Param= 75008 (0x00012500) COM2_RADIO_SET 30295 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 71296 (0x00011680) NAV1_RADIO_SET 30295 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 70000 (0x00011170) NAV2_RADIO_SET 30701 LUA.0: ...es\Microsoft Flight Simulator X\Modules\ipcReady.lua:2 30701 LUA.0: ...es\Microsoft Flight Simulator X\Modules\ipcReady.lua:3 30701 LUA.1: beginning "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\linda.lua" 30701 LUA.0: ended "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\ipcReady.lua" 30701 LUA.1: ...Games\Microsoft Flight Simulator X\Modules\linda.lua:18 30701 LUA.2: beginning "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\SS_Loader.lua" 30701 LUA.1: Global: ipcPARAM = 0

Hi Guys, No I am still kicken' around here Pete !! Rustam, This script to support the VRS SuperBug has now developed into a Suite of Script Modules that I have written using Pete's FANTASTIC Lua Libraries which now provide a FULL Cockpit I/O Interface to the VRS Superbug and is aptly named "SuperScript" for the VRS SuperBug. It handles many things, not just switches now. Current versions give access to Annunciators, Knobs using Pots, Rotaries with software acceleration, a Special TDC Radar Cursor Control and even non flight Gauge Instrument data extraction to build real instruments if you want. I have also written a module that allows VATSIM Transponder control from the F18's UFCD/MIP. The package has complete built in on screen Diagnostic routines to help troubleshoot when assigning and building annunciator panels etc. Shortly I will be adding UDP Network Packet transmission for all the output modules and am also considering a UDP INPUT Module too. So it is still currently being maintained by Myself and is only available from http://www.hornetpits.org That is a cockpit building site dedicated not only to the VRS Superbug builders but F18 Hornet builders in general, no matter what platform you are building on. However all are welcome and the signup to the forum is free, there is a wealth of knowledge at the site, so please take a look around, grab a coffee and make yourself at home. The current version is Version 2.08 and currently supports VRS Superbug/Tacpack 1.4.2.3. I am actively working on a 2.09 Release and in the middle of UDP Testing which is the reason for the delay, as I also have to write some documentation and it all takes time. There are dedicated Support threads for the package which I and others monitor and assist when required. The good news is that it is still available for download for free, I provide it as a "Donation Ware" package. Here are some Links to get you going.... Downloads for Version 2.00 through 2.08 can be found here, registration will be required to access the download section : http://hornetpits.org/index.php?board=55.0 For Support thread for the various versions, Really only the current 2.08 Version is supported. Take a look through these links: Version 1.04 http://hornetpits.org/index.php?topic=132.0 Version 2.03 http://hornetpits.org/index.php?topic=135.0 Version 2.04 http://hornetpits.org/index.php?topic=206.0 Version 2.05 http://hornetpits.org/index.php?topic=353.0 Version 2.06 http://hornetpits.org/index.php?topic=413.0 Version 2.07 http://hornetpits.org/index.php?topic=459.0 Version 2.08 http://hornetpits.org/index.php?topic=502.0 Regards Glenn.

No problem Pete, Thankyou for taking the time to look at it ... much appreciated. I will keep you posted if I discover anything else. I had this strange feeling it was going to come down to maybe an LM issue. In saying that is there a possibility that in the future FSUIPC could have some Alternate live display facility, even if it was in a window outside of P3D itself. Something similar along the lines of the Display Library for WideClient , that could be written for the P3D host machine or is that a massive task that would not be worth undertaking. Glenn.

I wrote that example to demonstrate the problem as it would replicate the issue 100%. I knew that it was never a problem in FSX because many users of my script have been running it for some time in FSX. Also I have noticed even if it is not once every second, even at a much much less rate, it still crashes eventually, so I do not think it anything to do with timing or how fast it is recalled. I have a couple of scripts, but not many, that will change the window title during the course of the script, that is how I tracked it down. What does bother me is I have seen several scripts running together displaying windows that can also cause the crash too, and all those scripts only call the Ipc.setowndisplay function once. I could not reliably reproduce the crash that way, it seemed to be more random and I wanted to demonstrate it to you with with something that could reproduce it all the time, so I feel there is also some issue with even the Ipc.display function. I will do some more experimenting and see if I can get it to happen just with the ipc.display function and let you know. I have only just started using P3D so I have not used my scripts on anything prior to 2.5 unfortunately. I have also noticed when running the sample script that I supplied there is a very quick flash of a display at the top left of the screen before the correctly positioned window is displayed, this seems to happen every time the Ipc.setowndisplay function is called. Take another look and you will see it but it is very quick, don't blink....but that might give some clues too. Regards Glenn.

Hello Pete, Hope you had a nice break. I have stumbled upon some issues surrounding the ipc.display and ipc.setowndisplay functions in the Lua libraries running under P3D. Here is a simple script that will replicate the issue every time. n = ipc.elapsedtime() function DISPLAY_TEST() ipc.setowndisplay("FSUIPC has been running for "..n.." milliSeconds", 2, 40, 95, 10 ) DISPLAY() end function DISPLAY() n = ipc.elapsedtime() ipc.display("The current FSUIPC Elapased Time = "..n) end event.timer(1000, "DISPLAY_TEST") I am Currently running: Windows 7 64Bit Prepar3d Academic 2.5.12945.0 Simconnect 2.5.0.0 FSUIPC 4.939k What happens is when this script runs, it displays on screen fine and the display gets updated perfectly. Then after about 25 Seconds P3D Hangs and crashes to a White see though screen with dialog that says: Lockheed Martin Prepar3d has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. I have to hit the "Close Program" Button and I am back to the desktop. Here is my FSUIPC.LOG file: ********* FSUIPC4, Version 4.939k by Pete Dowson ********* Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.ini" Running inside Prepar3D v2 on Windows 7 Module base=644A0000 User Name="Glenn Weston" User Addr="" FSUIPC4 Key is provided WideFS7 Key is provided 31 System time = 20/04/2015 00:26:04 31 FLT UNC path = "\\SIM01\Users\Glenn\Documents\Prepar3D v2 Files\" 31 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\SimConnectP3D2.dll 31 Found it: trying to connect 31 FS UNC path = "\\SIM01\Prepar3D v2\" 343 LogOptions=00000000 00000001 343 --- CONTROLS timer memory location obtained ok 343 --- SIM1 Frictions access gained 343 --- FS Controls Table located ok 343 --- Installed Mouse Macro hooks ok. 343 --- Wind smoothing fix is fully installed 343 SimConnect_Open succeeded: waiting to check version okay 343 Trying to use SimConnect Prepar3D 6396 Running in "Lockheed Martin® Prepar3D® v2", Version: 2.5.12945.0 (SimConnect: 2.5.0.0) 6396 Initialising SimConnect data requests now 6396 FSUIPC Menu entry added 6427 \\SIM01\Users\Glenn\Documents\Prepar3D v2 Files\YSRI Ready F18.fxml 6427 \\SIM01\Prepar3D v2\SimObjects\Airplanes\VRS_FA-18E\FA-18E-6.8_SE.air 21918 System time = 20/04/2015 00:26:26, Simulator time = 12:30:07 (02:30Z) 22090 Aircraft="VFA-105 "Gunslingers" CAG" 22901 Starting everything now ... 22917 LUA.0: beginning "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\ipcReady.lua" 23931 LUA.0: ended "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\ipcReady.lua" 24336 Advanced Weather Interface Enabled Here are the details from the App Crash log in Windows: Faulting application name: Prepar3D.exe, version: 2.5.12945.0, time stamp: 0x55145f5e Faulting module name: g2d.dll, version: 2.5.12945.0, time stamp: 0x55145f43 Exception code: 0xc0000005 Fault offset: 0x0006360e Faulting process id: 0x764 Faulting application start time: 0x01d07aacc332ad21 Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe Faulting module path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\g2d.dll Report Id: c2d74726-e6a0-11e4-9c1c-fcaa1469df7b I have developed a fairly complex set of Lua Script modules to Interface to the TacPack VRS F/A-18 In these modules I make use of the Display functions extensively to give the user Feedback to see that Assignments have been made correctly and that things are working as they should be, at which point they would then disable the displays to fly normally. The Problem seems to be very sensitive to using repeat calls to the ipc.setowndisplay function within the same script, however I have seen the same crash happen from multiple displays on screen at the same time which are only using the ipc.display function calls, but that does not seem to be as sensitive as when re-calling the ipc.setowndisplay function within the same script. By the way this works perfectly under FSX, so it could be an LM issue rather than an FSUIPC Lua Library issue. The Crash has been reported by many users on different hardware platforms running P3D (Same Version as me) and FSUIPC (Same version as me) so I don't think it is Video driver related. I understand that the Faulting Module g2d.dll is something to do with 2D Graphics within P3D and is nothing to do with FSUIPC. I can also say that this can be replicated with the default aircraft in P3D so it is nothing to do with VRS' Model. As you can see FSUIPC does not even get to Log the problem so it is a pretty fast and serious crash. Anyhow I just wondered if I could bring it to your attention and see if there is any possible fix or should this lay in the hands of LM. Regards Glenn.

That's a Mother Load of Annunciators........... Beautiful !! Thanks Pete !! Cheers Glenn.

Pete, Don't write off your WND library so fast, sometimes you just have to think outside the square..... in this case outside the window !! So I went back to the WND library again in the manual and was just looking at the commands, then the penny dropped...... Just create multiple little windows which each can be color controlled, Background and Text all independently. Attached is a looping demo script exercising different colors across the display, This could also be used for Radio Frequency Displays too, it's not limited to Annunciators by any means. One quick question if I may..... How many Individual displays can be created with the WND library ? Cheers Glenn. --[[ Looping Demo Annunciator Panel. Created using the WND Library for use on a WideClient PC and WideFS By Glenn Weston I will leave it to your Imagination what you can do with this. --]] -- Create window and define title, font, size and colours w1 = wnd.open("TEST PANEL1", WND_FIXED, 200,200,100,35) wnd.font(w1, WND_ARIAL, 24.0, WND_BOLD) --Font, Size and Properties wnd.backcol(w1, 0x000) -- background colour w2 = wnd.open("TEST PANEL2", WND_FIXED, 300,200,100,35) wnd.font(w2, WND_ARIAL, 24.0, WND_BOLD) --Font, Size and Properties wnd.backcol(w2, 0x000) -- background colour w3 = wnd.open("TEST PANEL3", WND_FIXED, 400,200,100,35) wnd.font(w3, WND_ARIAL, 24.0, WND_BOLD) --Font, Size and Properties wnd.backcol(w3, 0x000) -- background colour w4 = wnd.open("TEST PANEL4", WND_FIXED, 500,200,100,35) wnd.font(w4, WND_ARIAL, 24.0, WND_BOLD) --Font, Size and Properties wnd.backcol(w4, 0x000) -- background colour while 1 do ipc.sleep(1000) wnd.textcol(w1, 0xF00) wnd.text(w1 , " RED") wnd.textcol(w2, 0x0F0) wnd.text(w2 , "GREEN") wnd.textcol(w3, 0x00F) wnd.text(w3 , " BLUE") wnd.textcol(w4, 0xFFF) wnd.text(w4 , " WHITE") ipc.sleep(1000) wnd.clear(w1) wnd.clear(w2) wnd.clear(w3) wnd.clear(w4) ipc.sleep(1000) wnd.textcol(w1, 0xF00) wnd.text(w1 , " RED") ipc.sleep(250) wnd.clear(w1) ipc.sleep(250) wnd.textcol(w2, 0x0F0) wnd.text(w2 , "GREEN") ipc.sleep(250) wnd.clear(w2) ipc.sleep(250) wnd.textcol(w3, 0x00F) wnd.text(w3 , " BLUE") ipc.sleep(250) wnd.clear(w3) ipc.sleep(250) wnd.textcol(w4, 0xFFF) wnd.text(w4 , " WHITE") ipc.sleep(250) wnd.clear(w4) ipc.sleep(250) wnd.textcol(w1, 0x00F) wnd.text(w1 , " BLUE") wnd.textcol(w2, 0x00F) wnd.text(w2 , " BLUE") wnd.textcol(w3, 0x00F) wnd.text(w3 , " BLUE") wnd.textcol(w4, 0x00F) wnd.text(w4 , " BLUE") ipc.sleep(1000) wnd.backcol(w1, 0xFFF) -- background colour wnd.backcol(w2, 0xFFF) -- background colour wnd.textcol(w1, 0x0F0) wnd.text(w1 , "GREEN") wnd.textcol(w2, 0x0F0) wnd.text(w2 , "GREEN") wnd.textcol(w3, 0x0F0) wnd.text(w3 , "GREEN") wnd.textcol(w4, 0x0F0) wnd.text(w4 , "GREEN") ipc.sleep(1000) wnd.backcol(w1, 0x000) -- background colour wnd.backcol(w2, 0x000) -- background colour wnd.backcol(w3, 0xFFF) -- background colour wnd.backcol(w4, 0xFFF) -- background colour wnd.textcol(w1, 0xF00) wnd.text(w1 , " RED") wnd.textcol(w2, 0xF00) wnd.text(w2 , " RED") wnd.textcol(w3, 0xF00) wnd.text(w3 , " RED") wnd.textcol(w4, 0xF00) wnd.text(w4 , " RED") ipc.sleep(1000) wnd.backcol(w3, 0x000) -- background colour wnd.backcol(w4, 0x000) -- background colour wnd.textcol(w1, 0xFB0) wnd.text(w1 , "-----------") wnd.textcol(w2, 0xFB0) wnd.text(w2 , "-----------") wnd.textcol(w3, 0xFB0) wnd.text(w3 , "-----------") wnd.textcol(w4, 0xFB0) wnd.text(w4 , "-----------") ipc.sleep(3000) end

No problems Pete, I will take a look at that, Thankyou Cheers Glenn.

OK yes, That would be an option, I have not played with the "wnd.bitmap(w, "pathfilename")" command. This may be a solution, I guess it gets harder to deal with when there are more lamps to deal with, There are actually 10 Indicators on the left and 11 on the right some are hidden in that image, so that would be 1024 bitmaps for the left and 2048 bitmaps for the right. I could be pulling my hair out on that one.....so maybe not practical. I presume that completely refills/refreshes the whole screen with the new image, so every indicator must be handled in the bitmap. If there was a way to draw/refresh the screen with multiple bitmaps in set positions, then I would only need two bitmaps for each lamp, 20 for the left and 22 for the right, that would be doable. Cheers Glenn

OK Pete, That's OK I Understand. Thank you for taking a look at it anyhow. Here is a Video Link demonstrating what I did with the WND Library. http://www.youtube.com/watch?v=VMAiD3jqIb0 It is the quite a good solution for this particular Annunciator panel that I tied it into, that Annunciator is from the VRS F/A-18E and the Lamps are driven by Lvars in the aircraft itself. I take the Lvar values and assign each one(lamp) to individual BITS in a 16BIT Word, each BIT corresponds to a lamp which I then feed to a Custom Offset at 0x66C0, The WideClient WND Script monitors the 0x66C0 Offset and displays the appropriate lines of text based on the BIT Values in 0x66C0. Unfortunately the Other two Annunciator panels that I wanted to render have different colored text on the same line and therefore causing me a problem. Here is an image of the Annunciators, I am wanting to render the Left and Right Annunciators in this image, not necessarily the MASTER CAUTION and APU FIRE lamps but the other labels. Here are the arguments for this approach on this Annunciator...... Advantages: 1)Little to no cost in Frame rates because the panel is rendered on another PC, 2)Undocking just an Annunciator panel to put onto a small screen is not always available to to you, depending on the aircraft designer. 3)Can handle a lot of Annunciators in one hit, saving on LED Boards, Wiring and Physical Annunciator building. 4)As you can see in the Video, the Annunciator can be rendered easily on multiple PC's making it available for mare than one pilot or instructor stations. 5)Easily rendered on small, cheap USB Display Screens that are available these days. 6) Can be setup over IP networks, Even using Wireless such as in the Video Disadvantages: 1)Will require a second PC, but it is easy and cheap to find unwanted laptops and PC's that could handle this task very easily. 2)Will require WideFS (But more Sales for you Pete !!) 3)Will require a Network setup for the communications to take place over WideFS. 4)Unable to handle multicoloured text on the same line, I also have not looked at how it would go with a flashing label or indicator That's about all I can think of at this point. I have looked at the Button Screen but that is more geared towards an INPUT screen in conjunction with a touch panel and restricted a bit for the use as an OUTPUT screen. Maybe it might be easier to make modifications to the Button Screen area to allow for a wider color range of Text and Background colors and be able to control those colors programatically. That way individual buttons could be addressed for color or addressed for a flashing event etc. Anyhow that's sort of where I was coming from, It might be worthwhile to provide something that can do on screen OUTPUT like this, what do you think ? Thankyou again Pete for your time. Regards Glenn.

Just a reminder Pete, when you have time to take a look. Cheers Glenn.

No Problems Pete, Thankyou very much for considering this.......It's not urgent at all. I will give you a nudge on the 9th for sure. Have a great Holiday !! Cheers Glenn.