Gypsy Baron

As I recall, the mode switch on Saitek products does not get sent through to FSX/FSUIPC4 normally. The Saitek software traps that button/switch. There is a work-around that requires an edit in the registry, I believe. I don't recall the details exactly but a google search or a search of this forum should turn up the solution. I use a different approach to mapping multiple commands to the same switch/button/key. I assign one of the user-defined offsets to be my 'mode idicator' and then use the contents of that offset as the qualifier for my mappings. An example, FYI, showing a portion of the mappings for my A2A P-40:: [Buttons.Curtiss P-40] 1!==//------- Control Set 1 ----------------- 0=PA,4,Cx510066C0,x00040001 ;//CONTROL SET INC Max = 4 Step = 1 1=PA,5,Cx610066C0,x00040001 ;//CONTROL SET DEC Max = 4 Step = 1 2=B66C0=0 PD,14,C66400,0 ;//Magneto - OFF 3=B66C0=0 PD,15,C66400,2 ;//Magneto - Left 4=B66C0=0 PD,16,C66400,3 ;//Magneto - Both 5=B66C0=0 PD,17,C66400,1 ;//Magneto - Right . . 2!==//--------- Control Set 2 ----------------- 20=B66C0=1 PD,14,CM9:14,3 ;//Fuel Tank Select - CYCLIC 21=B66C0=1 PD,15,CM9:18,0 ;//Hydraulic Pump Toggle 22=B66C0=1 PD,16,CM9:15,0 ;//Generator Toggle 23=B66C0=1 PD,17,CM9:5,0 ;//Battery - Toggle . . 3!==//--------- Control Set 3 ----------------- 40=B66C0=2 PD,14,C66389,0 ;//Toggle Canopy 41=B66C0=2 PD,15,CM9:1,0 ;//Toggle Gunsight 42=B66C0=2 PD,16,CM9:8,0 ;//Klaxton Test Toggle 43=B66C0=2 PD,17,CM9:10,0 ;//Prestone Test Toggle . . 4!==//------- Control Set 4 ----------------- 60=B66C0=3 PD,14,C66506,225 ;//Toggle GPS 61=B66C0=3 PD,15,C66506,440 ;//Toggle ANR-75 radar 62=B66C0=3 PD,16,C66506,14992 ;//Toggle AP Chart 63=B66C0=3 PD,17,C65910,0 ;//MAP - TOGGLE (Panel 5) . . 5!==//------- Control Set 5 ----------------- 80=B66C0=4 PD,14,CM9:32,0 ;//Oil Dilute TOGGLE //81=B66C0=4 PD,15, SPARE 82=B66C0=4 PD,16,CM9:25,1 ;//ON Jacks 83=B66C0=4 PD,17,CM9:25,0 ;//OFF Jacks The user-defined location 66C0 indicates the current mode. That number must match the number indicated in the INI for a particular button/switch/key for that mapping to be active. I sdome of my aircraft I have up to 9 'modes' so this method would work well for those with a minimum number of buttons/switches. I have 10 switches on my Saitek dual throttle quads that I assign in this fashion. Only 4 are shown in the snippet above. I assign two switches, PA 4 and PA 5, to increment/decrement the mode. (Lines 0,1 above) Also, when the mode number changes I have a Lua script that displays the current mappings for the mode for 3 or 4 seconds to remind me as to what each switch currently does :) Paul

L:Vars can be declared in an MCRO file. This adds them to the list of controls that can be manipulated by FSUIPC4 via the Buttons & Switches menu and the axis assignment menu. Lua has the ability to read L:vars and offsets as well as write to them (ipc.read and ipc.write) The User defined offsets, 0x66C0 - 0x66FF, can be used as you wish. I suggest that you read and re-read the Advanced User Guide PDF as well as the Lua Library PDF in the documents folder. Those two, along with the Revised_List_of_FSX_Controls.pdf and FSUIPC4_Offsets_Status.pdf, should answer a lot of questions and enlighten you to the poser of FSUIPC4 and Lua. Paul

I recall a very old thread that addressed the issue of having to have the MS Game Controller properties window open, but that was concerned with being able to 'see' the 'Mode' select switch on the Saitek product. I have a Saitek X-45 connected using my old DAT files from years ago, as well a a Pro Yoke and dual throttle quads all programmed in FSUIPC4....no Saitek software installed (dastardly .pro files!) for those items. All work just fine, and I have all the A2A Accu-Sim aircraft with aircraft-specific FSUIPC4.ini sections and Lua scripts. On the Mode switch(s), there seems to be some internal code that inhibits them from being seen externally...i.e. by FSUIPC4. Opening the MS Controller seems to bypass this. If the inoperable functions rely or use the Mode switch, they won't work as 'raw' inputs to FSUIPC4. Paul

I would try some of the following controls, found in the Revised List of FSX Controls.pdf: NEXT_SUB_VIEW 66153 NEXT_VIEW 65827 PREV_SUB_VIEW 66154 PREV_VIEW 65828 VIEW_MODE 65567 VIEW_MODE_REV 65749 VIEW_TYPE 65829 VIEW_TYPE_REV 65830 Paul

As a former assembly language programmer, I would definitely opt for a single script with copious comments to 'remind ones self' what you are doing and why :) I use a Lua script for each of the aircraft I fly often, mostly the A2A Accu-Sim birds, and each script has several functions that are triggered by various events. When I need to add or change something for a given aircraft, I know immediately 'where to go'...that single aircraft-specific script file. Paul

Thank you Pete! I add those 'extra' // marks out of habit, plus they let me see the added comment better. The simi-colons can seem to get lost on my high res monitor :) Paul

Just a note on the simconnect error issue. I just read a topic over in the A2A forums that indicates the Estonian Migration Tool for P3D was causing simconnect errors on the A2A aircraft. The author is or has fixed the problem. Paul

That A2A Simconnect error is usually bcaused by a large lag or delay in the communications. The only way to clear it once it occurs is to completely exit the sim and then re-enter. Also, it is recommended that one does not use time acceleration with Accu-Sim aircraft and I have a suspition that slew mode is not 'tolerated' too well. Much of the Accu-Sim code runs 'outside' of the FSX/P3D environment and thus some of the 'standard' FSX/P3D operations such as time acceleration are not tolerated well. I haven't been able to pin down the exact conditions to cause that error but I noted that on my WinXP x32 boot, I can load then re-load an accu-sim aircraft or a combination of accusim aircraft exactly 3 times before the error occurs. On my Win7 x64 boot, I can rel;oad accu-sim aircrat 6 or 8 times before the error appears, My Win7 install runs mquite a bit faster and smoother than my old Xp install so this points toward a time lapse condition. I haven't seen it recentlyand I've been flying all the accu-sim aircraft except my B-377. Many hours in the B-17 and P-51's but the most I ever re-load aircraft these days is usually twice. During beta testing I would re-load often and sometime get the error. Some rather bizzare things can occur seemingly 'out of the blue' until the causes are tracked down. I recall a awhile ago that someone noted a failure of the 'direct tuning' capability in either the A2A C-172 or the Cherokee when they changed from an unregistered state in FSUIPC to the registered state, The cause was soon tracked to a change in the sequence of the commands in the code that rapidly switched between the standby and active frequencies to implement the 'direct tune' mode. A slight change in the timing of the code execution in FSUIPC4 was allowing one command to 'get ahead' of another, getting them out of sequence and causing the problem. Once that was identified Pete had a fix for the condition and all was well again :) Paul

Thanks Pete. No hurry.I just received my new gaming laptop and it is going to take me awhile to get it set up. Also, I am heading back to Europe for a couple of weeks on Monday :) Paul

Simply press the "Reload" button on the FSUIPC4 Buttons + Switches menu. That will read the INI file and apply any changes that you may have made by editing the file. Paul

Another solution in this case would be to assign one action on the button 'press' and the 2nd action of the button 'release'. This can be done via the FSUIPC4 Buttons + Switches menu but is ONLY applicable for the case of 2 actions for a given button. My implementation on my setup uses multiple actions for each of my switches (many more than 2) so I have become quite adept at editing the INI file :) As Reinhard indicated above, most 'answers' are available in the FSUIPC4 documentation. Paul

Look in the Modules folder and find the FSUIPC Documents folder. In there you will find the "Revised_List_of_FSX_Controls.pdf" In that document you will find the following entries with their control codes: RADIO ADF IDENT DISABLE RADIO ADF IDENT ENABLE RADIO ADF IDENT SET RADIO ADF IDENT TOGGLE RADIO ADF2 IDENT DISABLE RADIO ADF2 IDENT ENABLE RADIO ADF2 IDENT SET RADIO ADF2 IDENT TOGGLE RADIO DME1 IDENT DISABLE RADIO DME1 IDENT ENABLE RADIO DME1 IDENT SET RADIO DME1 IDENT TOGGLE RADIO DME2 IDENT DISABLE RADIO DME2 IDENT ENABLE RADIO DME2 IDENT SET RADIO DME2 IDENT TOGGLE RADIO SELECTED DME IDENT DISABLE RADIO SELECTED DME IDENT ENABLE RADIO SELECTED DME IDENT SET RADIO SELECTED DME IDENT TOGGLE RADIO VOR1 IDENT DISABLE RADIO VOR1 IDENT ENABLE RADIO VOR1 IDENT SET RADIO VOR1 IDENT TOGGLE RADIO VOR2 IDENT DISABLE RADIO VOR2 IDENT ENABLE RADIO VOR2 IDENT SET RADIO VOR2 IDENT TOGGLE If you are using an "advanced" high fidelity aircraft, chances are that many functions are coded using local variables (L:Vars) in the various gauges. These variables, unlike the default FSX commands such as those above, are not 'visable' for FSUIPC4 to use unless you create a MCRO file definuing those variables and the type of operation to perform (SET, TOGGLE, etc). You will fimd information on these items, and many other valuable bits of knowledge, in the "FSUIPC4 for Advanced Users.pdf:, a 'must read' for anyone wanting to exercise the power of FSUIPC4. Page 37 begins the section on the MCRO file. Pages 40 and 41 have information on Gauge local variables (L:Vars). I would set up shortcuts to both of those documents as the information they contain will be most helpful in unleashing the power of FSUIPC4 :) Paul

Thanks for the reply Andy. I plan to purchase another copy of FSUIPC4 primarily to support Pete and his efforts, considering the myriad benefits I have reaped over the years by using my current copy :) Paul

I have recently begun setting up aircraft-specific sections in my FSUIPC4.INI file for eventual transfer to a new gaming laptop that will use a Logitech G13 'gamepad'. Essentially a programmable keyboard with a mini-joystick. I will be obtaining a new registered copy of FSUIPC4 for this system but am currently tesing my approach on my home desktop system. In the process of creating the new "Keys" section I discovered that, unlike the "Buttons" section, comments appended to the entries are being removed whenever I reload that section. The same is true of the "Axis" and "Joystick Calibration" sections also. In the past I have not had any reason to add comments in the "Keys" sections as all my customization has been done via the "Buttons" entries, but with the G13 being seen as a keyboard I needed to create a rather lengthy and complex "Keys": section for the aircraft I will primarily be flying on the new laptop while away on my many travels. Currently I have to save a copy of my INI file with the added comments and use that copy to make any changes. I then have to replace the actual INI file with a copy of this saved copy. It would be nice if the comments were retained in the "Keys" section. Actually retention in all sections would be ideal. This statement from the Advanced Users Guide in the section discussing Button programming is what I would like to see for the Keys section as well: "You can add comments following a semicolon ( ; ) at the end of the line, and these will be retained." Just to demonstrate my use of the Keys section in which I emulate the 'multiple mode' technique of my current "Buttons" sections, below is a listing of 3 of the 13 unique groups of key assignments that I have defined so far. This should serve to demonstrate my 'need' for comments as well as demonstrate to others what can be accomplished through the use of the Logitech G13 and other programmable keyboard devices. (There is virtually no practical information available for using the G13 in FSX) !0=//----------- C=Control S=Shift Nx=NUMx ------------- !0=//--- KEY ASSIGNMENTS FOR THE G13 MODE 1 G-KEYS ----- !0=//-- G1 G2 G3 G4 G5 G6 G7 !0=//-- C+S+1 C+S+2 C+S+3 C+S+4 C+S+5 C+S+6 C+S+7 !0=//--------------------------------------------------- !0=//-- G8 G9 G10 G11 G12 G13 G14 !0=//-- C+S+F5 C+S+F6 C+S+F7 C+S+F8 C+S+F9 C+S+F10 C+S+F11 !0=//--------------------------------------------------- !0=//-- G15 G16 G17 G18 G19 !0=//-- S+F5 S+F6 S+F7 S+F8 S+F9 !0=//--------------------------------------------------- !0=//-- G20 G21 G22 !0=//-- C+6 C+7 C+8 !0=//--------------------------------------------------- !0=//-- Joy Left Joy Bottom !0=//-- C+F5 C+F7 !0=//--------------------------------------------------- !0=//--------------------------------------------------- !0=//--- KEY ASSIGNMENTS FOR THE G13 MODE 2 G-KEYS ----- !0=//-- G1 G2 G3 G4 G5 G6 G7 !0=//-- 5 6 7 8 9 S+F2 C+S+8 !0=//--------------------------------------------------- !0=//-- G8 G9 G10 G11 G12 G13 G14 !0=//-- C+F6 S+F1 C+F11 C+F12 C+S+B C+S+E C+S+J !0=//--------------------------------------------------- !0=//-- G15 G16 G17 G18 G19 !0=//-- C+I C+S+M S+J S+N S+F3 !0=//--------------------------------------------------- !0=//-- G20 G21 G22 !0=//-- S+J S+N C+S+W !0=//--------------------------------------------------- !0=//-- Joy Left Joy Bottom !0=//-- C+F5 C+F7 !0=//--------------------------------------------------- !0=//---------------------------------------------------- !0=//-- KEY ASSIGNMENTS FOR THE G13 MODE 3 G-KEYS !0=//-- DEFAULT FSK KEY ASSIGNMENTS USED HERE !0=//---------------------------------------------------- !0=//-- G1 G2 G3 G4 G5 G6 G7 !0=//-- F3 F6 S+NUM 4 S+NUM 6 NUM 4 NUM 8 NUM 6 !0=//---------------------------------------------------- !0=//-- G8 G9 G10 G11 G12 G13 G14 !0=//-- F2 F7 S+NUM 8 S+NUM 2 NUM 0 NUM 2 NUM ENT !0=//---------------------------------------------------- !0=//-- G15 G16 G17 G18 G19 !0=//-- G F9 F12 S+F9 NUM 5 !0=//---------------------------------------------------- !0=//-- G20 G21 G22 !0=//-- NUM * NUM - S+F8 !0=//---------------------------------------------------- !0=//-- Joy Left Joy Bottom !0=//-- CTL+F5 CTL+F7 !0=//---------------------------------------------------- [Keys.Boeing B-17G "Fearless Fosdick" Test] !0=//----------- MODE 0 ----------------- !0=//---- Generators, Batteries, Hydraulic Mode !0=//---- Ignition, Inverter !0=//----------- MODE 0 ----------------- 0=B66C0=0 49,11,M6:13,0 ;//TOGGLE GENERATOR 1 1=B66C0=0 116,11,M6:32,0 ;//APU MACRO 2=B66C0=0 50,11,M6:14,0 ;//TOGGLE GENERATOR 2 3=B66C0=0 117,11,M6:64,1 ;//RADIO POWER 4=B66C0=0 51,11,M6:15,0 ;//TOGGLE GENERATOR 3 5=B66C0=0 118,11,65858,0 ;//PITOT HEAT 6=B66C0=0 52,11,M6:16,0 ;//TOGGLE GENERATOR 4 7=B66C0=0 119,11,66535,0 ;//MASTER IGNITION TOGGLE 8=B66C0=0 53,11,M6:43,1 ;//HYDRAULIC MODE MANUAL 9=B66C0=0 120,11,M6:43,0 ;//HYDRAULIC MODE AUTO 10=B66C0=0 54,11,M6:38,0 ;//INVERTER SWITCH ON 11=B66C0=0 121,11,M6:38,2,M6:38,1 ;//INVERTER OFF / NEUTRAL 12=B66C0=0 55,11,M6:18,1 ;//BATTERY 1 ON MACRO 13=B66C0=0 55,11,M6:19,1 ;//BATTERY 2 ON MACRO 14=B66C0=0 55,11,M6:20,1 ;//BATTERY 3 ON MACRO 15=B66C0=0 122,11,M6:18,0 ;//BATTERY 1 OFF MACRO 16=B66C0=0 122,11,M6:19,0 ;//BATTERY 2 OFF MACRO 17=B66C0=0 122,11,M6:20,0 ;//BATTERY 3 OFF MACRO 18=B66C0=0 55,11,65908,0 ;//PANEL 4 OPEN - CONTROLS 19=B66C0=0 55,11,L17:R,0 ;//START DISP B17G 20=B66C0=0 55,11,L32:R,0 ;//START CALC TRACK !1=//----------- MODE 1 ----------------- !1=//---- Fuel Valves and Pumps, Tail Wheel Lock, Carb Filters !1=//---- Controls Lock, Windows, Parking Brake !1=//----------- MODE 1 ----------------- 30=B66C0=1 49,11,M6:39,0 ;//TOGGLE ENG1 FUEL VALVE 31=B66C0=1 116,11,66340,0 ;//TOGGLE FUEL PUMP 1 32=B66C0=1 50,11,M6:40,0 ;//TOGGLE ENG2 FUEL VALVE 33=B66C0=1 117,11,66341,0 ;//TOGGLE FUEL PUMP 2 34=B66C0=1 51,11,M6:41,0 ;//TOGGLE ENG3 FUEL VALVE 35=B66C0=1 118,11,66342,0 ;//TOGGLE FUEL PUMP 3 36=B66C0=1 52,11,M6:42,0 ;//TOGGLE ENG4 FUEL VALVE 37=B66C0=1 119,11,66343,0 ;//TOGGLE FUEL PUMP 4 38=B66C0=1 53,11,M6:45,1 ;//CONTROLS LOCK ON 39=B66C0=1 53,11,M6:46,1 ;//CONTROLS LOCK ON 40=B66C0=1 54,11,66541,0 ;//TAIL WHEEL LOCK 41=B66C0=1 55,11,M6:44,0 ;//CARB FILTER TOGGLE 42=B66C0=1 120,11,M6:45,0 ;//CONTROLS LOCK OFF 43=B66C0=1 120,11,M6:46,0 ;//CONTROLS LOCK OFF 44=B66C0=1 121,11,M6:81,99 ;//OPEN PILOTS COCKPIT WINDOW 45=B66C0=1 121,11,M6:82,99 ;//OPEN COPILOTS COCKPIT WINDOW 46=B66C0=1 122,11,65752,0 ;//PARKING BRAKES !2=//------ MODE 2 ------------------- !2=//------ Mags, Suit Heaters, Vent !2=//------ MODE 2 ------------------- 50=B66C0=2 49,11,x11000892,x00030001 ;//MAG1 INC 51=B66C0=2 116,11,x21000892,x00000001 ;//MAG1 DEC 52=B66C0=2 50,11,x1100092A,x00030001 ;//MAG2 INC 53=B66C0=2 117,11,x2100092A,x00000001 ;//MAG2 DEC 54=B66C0=2 51,11,x110009C2,x00030001 ;//MAG2 INC 55=B66C0=2 118,11,x210009C2,x00000001 ;//MAG2 DEC 56=B66C0=2 52,11,x11000A5A,x00030001 ;//MAG2 INC 57=B66C0=2 119,11,x21000A5A,x00000001 ;//MAG2 DEC 58=B66C0=2 53,11,M6:83,50 ;//SUIT HEATER 1 50% 59=B66C0=2 54,11,M6:84,50 ;//SUIT HEATER 2 50% 60=B66C0=2 120,11,M6:83,0 ;//SUIT HEATER 1 0% 61=B66C0=2 121,11,M6:84,0 ;//SUIT HEATER 2 0% 62=B66C0=2 55,11,M6:85,100 ;//CABIN VENT OPEN 63=B66C0=2 122,11,M6:86,0 ;//CABIN VENT CLOSE For this aircraft I have 9 "modes" defined by the 0x66C0 offset. Also, the G13 allow me to program three unique sets of keys for the 22 primary keys. For one of those sets I have programmed the default FSX keys for a number of functions. That is my "G13 Mode 3". My G13 Mode 1 and 2 make use of 44 of the unassigned keys in FSX. These then are used to create the 'multiple FSX modes' as shown above. In theory I could wind up with 9 'modes' in each of the first two G13 modes and a single addition mode in the G13 Mode 3 for a total of 19 groups of 22 unique assignments. So you see this can, ney will, become quite complicated and thus my desire for persistent comments. I fly the A2A Simulations "Accu-Sim" warbirds almost exclusively and a great deal of the functionality of those aircraft is down by coding 'outside' of FSX. I use L:Variables extensively to enable a 'push button' environment with my dual Saitek quadrants and most of those sircraft require from 4 to 9 'modes'....hundreds of lines of hand-edited INI entries. Now, creating a 'button-free' setup, I need to se my "Buttons" sections as a guide to creating the new "Keys" sections. Without the existing comments in my "Buttons" section, that task would take a good many hours more than the 16 or 20 hours that I have spent so far. Paul

That was just to indicate that I couldn'tr remember the exact name of that control as shown in the FSUIPC4 Buttons+Switches menu. Just go down the menu looking for "List" as the first word and you should find the control. Paul

I don't have the X55 however I do have the old X-45 as well as the Saitek Pro yoke and dual throttles. I use the Saitek software for setting up much of the X-45 hats, buttons, switches and use the stick for my flight controls. For the Pro yoke/throttle stuff I do NOT load the Saitek software but instead program everything via FSUIPC4. You might try disabling/removing the X55 software and then try setting up everything via FSUIPC4. You might want to investigate the source of the continous space characters if they still exist after disabling the X55 software. With my X-45, even though I use the software and load a profile, the buttons/switches that I do not create assignments for in the profile get passed directly through and FSUIPC4 'sees them' and I can make assignments there. Paul

I am not quite sure what you are asking for here, but the standard WinXP/Win7 calculators have the ability to convert numbers between bases...Decimal, Hex, Octal, Binary, Just select "Scientific" under the "View" option in the calculator. Paul

Thanks for that input, Reinhard. Good to know for those that use profiles. I don't use profiles as I stayed with the 'aircraft specific' method I have used over the years. Paul

The FSUIPC4.ini file contains all the settings. When updating, that is preserved. At least I have never had any issues when doing the incremental or full upates. If new lines are needed in the General section they are inserted without disturbing the rest of the file. That said, it is always good practice to save a backup copy periodically,,,,just in case :) Paul

Here are a couple of VAS-related items. A quick & dirty Lua script to give you 'notice' when the VAS is below a threshold that you can define as you like. Also I include some XML code for a simple 2-D gauge to display VAS and when it drops below a threshold, the normally white characters then turn red. Read the comments and use as you wish. No guarantees or support :) //==== A Lua Script to display VAS when it drops below threshold ======= //==== When the VAS value changes in offset 0x024C that event then ===== //==== triggers the function which then reads the offset and sends ===== //==== the current VAS to the L:Variable, L:VAS. The current value ===== //==== is then tested against an arbitrary threshold (500000 in my ===== /===== case and if the VAS is less than the threshold a small Lua ===== //==== display opens on the FSX screen and displays the VAS for a ===== //==== set time...2 seconds in the case below. ===== //==== To use this code, simply copy and paste it to a test file ===== //==== and then save it as VAS.lua in your FSX modules folder. ===== //==== You will also need to add it to the FSUIPC4.ini file [Auto] ===== //==== section so that is loaded and running when you start FSX. ===== //==== [Auto] //==== 1=Lua KillAll //==== 2=Lua VAS //==== //========== Paul "Gypsy Baron" Strogen August 05, 2014 ================ function VAS(control, vas) <!-- The line below defines the position and size of the Lua display window --> <!-- Adjust the values to suit your needs. I use the display for several other --> <!-- Multi-line outputs so I set it larger than required here. --> ipc.setdisplay(770, 50, 500, 100) vas_in = ipc.readUD(0x024C) ipc.writeLvar("L:VAS", vas_in) if vas_in < 500000 then ipc.display("VAS = "..vas_in,2) end end event.offset(0x024C,"UW","VAS") //===================== End of Lua Script =============================== <!-- //== In several of my aircraft I have a 2-D gauge that is open most of ==== //== the time so I extended the background BMP in the vertical (Y) ==== //== dimension to allow for the continuos display of the current VAS. ==== //== The original BMP was a 112x132 rectangle. I extended it to 112x166 === //== You could create a BMP of 112x34 to display the VAS and adjust the === //== Y="138" entries below to Y="6" - NOTE: Edited to do that ============ //== As long as the VAS is equal or greater than my arbitraty threshold === //== of 500000, the display is white. When VAS goes below the threshold === //== the display is RED. This display code relies upon the above Lua ====== //== script running and saving the current VAS to "L:VAS". otherwise ====== //== this readout will always be zero! One could change/add code here to == //== read the offset directly, I suppose, but I already had the script ==== //== so chose to use the L:varible that it created. ======================= --> <!-- ===================== DISPLAY VAS =================================== --> <Gauge Name="VAS Display" Version="1.0"> <Image Name="VAS_Background.bmp"/> <Element> <Visible>(L:VAS, number) 499999 > </Visible> <Position X="25" Y="6"/> <Text X="80" Y="12" Length="8" Fixed="Yes" Font="arial" Adjust="Left" VerticalAdjust="Top" Color="#EAEAEA" Bright="Yes"> <String>%((L:VAS, number))%!07d!</String> </Text> </Element> <!-- === Change display color to RED when VAS is less than 500000 ====== --> <Element> <Visible>(L:VAS, number) 500000 <</Visible> <Position X="25" Y="6"/> <Text X="80" Y="12" Length="8" Fixed="Yes" Font="arial" Adjust="Left" VerticalAdjust="Top" Color="#FF0000" Bright="Yes"> <String>%((L:VAS, number))%!07d!</String> </Text> </Element> </Gauge> <!-- ========================================================================== -->

Assign a button/switch temporarily to the FSUIPC4-provided "List Local Panel Variables" or words to that effect. Hit the button/switch and the L:Vars will be sent to the current FSUIPC4.log file. After doing that, select "New Log" under the Logging options so that you can then have a look at the first log, renamed, Each entry will have a time stamp prefacing the L:Var entry but you can do a "Find/Replace" to replace the time stamp with a blank space or just do not enter anything in the"replace" entry and the time stamps will be removed. Also, clear the jbutton/switch that you assigned to the list command so you don't keep filling the log files if you hit that button/switch again :) Paul

NP. Thanks Pete. You support here is much appreciated! Paul

In all previous installer packages, the "Changes" documents has been a PDF file. The "Install_FSUIPC4931.zip" package instead contains a "FSUIPC 4.931 Changes.docx" file. I do not have anything on my system to read this format, nor do I wish to install yet another 'special' utility to do so. Why the change from the universally supported PDF format to thie docx format? Paul

The value for the glareshield mounted defrost sliders should max out at '50'. I use two buttons to control those sliders and they work just fine. My C172 MCRO file contains these two definitions: 46=L:WindowDefrosterControl1=CYCLIC 47=L:WindowDefrosterControl2=CYCLIC My switch/button assignments in the FSUIPC4.ini file are: 36=RA,0,CM16:46,50 ;//LEFT WINDOW DEFROST 37=RA,1,CM16:47,50 ;//RIGHT WINDOW DEFROST I'm not using the "WindowDefrosterControlKnob" L:Var. In most of my "cyclic" operations or those that use the "R", repeat, switch modifier I also create a Lua script to display the current value(s) for the L:Var as I am changing it. I didn't do that for these two operations but here is a sample for another A2A product, the P-40, where I display the current "vent" position as I am changing it: A similar construct could easily be created for the C172 vents, having the button/switches modify a couple of the User-defined offsets, as I have done for the P-40, and use the 'event' trigger to run the Lua script to do the controlling and display. Paul

FYI, I use the FSUIPC4 command "List Local Panel Variables". This will dump those into the current FSUIPC4.log file. Then I select the "new log" function from the menu. That will leave the FSUIPC4.log.1 in your modules directory and you can then go in and remove all the non-Lvar stuff. I use a 'find and replace' to strip out the leading space and the time stamp, leaving just the L:vars. This method doesn't use Lua and I just un-map the button I assigned the "List all...." command to. Paul