Gypsy Baron

If the X52 is similar to the X45, the Mode switch is seen as a seperate 3-position switch. In the WinXp control panel Game Controllers page if you select the X52\Properties you should see it listed under the "Switches" heading. In FSUIPC, under the Buttons + Switches tab, if you activate the mode switch you should see the data in the Joynumber and button windows change. These would be the codes you would use to create compound control functions. That is, you would use the state of that switch as seen in FSUIPC to qualify/modify the functions of the other buttons, axis, rotaries etc. Paul

Try changing "Tog" to "TOGGLE" or "Toggle". I don't see "Tog" listed as an ACTION in the Advanced Users guide. Paul

I have several of my Saitek X-45 functions programmed with the Saitek software and others set vis FSUIPC4. I also have the Saitek Pro yoke/quadrant and 2nd quadrant that I program exclusively via FSUIPC4. Paul

That's what I thought was the case but wanted confirmation. I understand that operation. I was hoping that there was an outside chance that the "ref" was a parameter supplied by FSX and remained constant during a session for a particular "wav" file. I have no problem detecting the "wav" file playing with the "query" function as long as I started it with the "play" function. That doesn't help me for my application however. The use of the "sound detection" was what I hoped would be a way of determining, from within a XML gauge or Lua plugin, when an effect was being generated. Alas, there does not appear to be an easy way to get "external events" such as that into the user-aircraft environment. It seems I will have to resort to a messy continuous comparison of current Lat/Lon with a table of several hundred "lat/lon rectangles". :( Thanks for the reply. Paul

Hello Pete, I have a question regarding the Lua Library sound functions. Specifically: 1. "ref = sound.play("name-of-wave")" 2. "bool = sound.query(ref)" What assigns the "ref" parameter when the "wav" file is played using the first function above? Does this come from within Lua or from the FSX sound system? Once the "ref" parameter is obtained via the first function, does it remain the same if that same "wav" file is played as a result of an FSX "effect"? Or does the "ref" change each time the "wav" file plays? An explanation of my desired use: What I am attempting to do is recognize when the user aircraft is within range of some FLAK explosion effects so that I can use that information eo effect damage to the aircraft without the user having to do anything. At the moment the only solution I have for this is to create "dummy" DME stations with very short ranges and locate them in the FLAK areas. I have an XML gauge that sets the standby NAV2 freq to 117.95 and if the user tunes the active NAV 2 to 117.95 the "Flak Damage Code" is enabled in the XML gauge code. Once in range of the DME I sense the signal strength, and if above a threshold level, consult a couple of random number generators to determine if damage is to be inflicted and the type of damage. This is rather a kluge in that the "dummy DME" sites clutter up the landscape as I have several hundred FLAK sites and thousands of "eefect controllers" spread around Europe. (I started this little project with the A2A B-17G in mind) I was hoping to use a method that was less of a kluge and since the effect files and controllers with the WAV file references were already located where I want them, sensing the sound being played would be ideal. I experimented with a Lua Plugin to use the two functions noted above and then subsequently use the "query" function to see if I could "see" the WAV file played as a result of the effects but to no avail. Another approach, albeit very messy, would be to do a Lat/Lon compare but there are just too many sites that I would have to create tables of min/max Lat and Lon for. The one "interface" between the user aircraft and external effects, "cause damage", was removed by Microsoft for FSX as I understand it. What I wish to do is perhaps possible via SimConnect but I have no experience writing code for that application so Lua and XML are my choices. Paul

Hello Neal, I've got Lua plugins for the B-377 for implementing the prop reverse as well as handling several of the functions like inter-cooler flaps, mixture, carb air and others. The coding I included above uses those files along with a MCRO macro file. In addition, the coding is unique to my setup in that FSX assigns the controller ID's based on how it sees them attached. So my controller "A" may not be your controller "A". Note that I am using the FSUIPC "AutoAssignLetters=Yes" feature under the "JoyNames" section. I can give you some guidance on using my "multi-mode" approach with the B-377 as an example. I also have similar configurations for the A2A B-17G and the A2A P-47D. This would best be carried out via email so send me a PM here and we can work on this. I think that I could easily create a [buttons.Boeing Stratocruiser] entry for your setup that you could just copy and paste into your FSUIPC4.ini file and then you can experiment and adapt the technique to other aircraft. Paul

I have the Saitek Pro Yoke with dual throttle quadrants as well a Saitek X-45 stick & throttle. I use FSUIPC4 to assign functions to all those axis, buttons and switches. With the various programming capabilities of FSUIPC4 and the Lua facilities, you can create very complex control structures. As an example, I have a setup for my A2A B377 that assigns 7 different functions to each of the switches on my dual throttle quadrant. That would be like have a 7-mode switch. in fact, using the technique that I implement, I could have up to 256 "modes". The ability to create aircraft-specific assignments allows you to do pretty much what the Saitek software multiple profiles would do but with more capabilities. You can keep the Saitek software on your system as well as the drivers. As long as you don't load a profile, they won't be used. I suggest you have a good look at the documentation, specifically the Advanced Users guide and the Lua Library documents to get an idea of what is possible with FSUIPC4. As an illustration of one of my implemntations, below is the "Buttons" section of my FSUIPC4.ini file for the A2A B-377. The coding is, of course, unique to my hardware assignments and Lua routines but it may give you some insight into what is possible. I use one of the 6 double-pole switches on the quadrants to switch "modes" and the other 5 switches to control various functions. I can pretty much get into the cockpit of that complex aircraft and get it into the air without having to use the keyboard or the mouse :) Paul ( BTW, I'm an old aircrewman and EE - 69 years old now ) :) !1=//------------------------ A2A B-377 CONTROL SETS ------------- [Buttons.Boeing Stratocruiser] !1=//SET 0 STARTUP SETUP 0=B66C0=0 PD,14,Cx110066C9,x00040001 ;//INC ENGINE SELECT through LUA routine 1=B66C0=0 PD,15,Cx210066C9,x00000001 ;//DEC ENGINE SELECT through LUA routine 3=B66C0=0 PD,16,CM4:8,1 ;//PRIMER 4=B66C0=0 UD,16,CM4:8,0 5=B66C0=0 PD,17,C65858,0 ;//PITOT HEAT 6=B66C0=0 PD,18,CM4:7,1 ;//STARTER 7=B66C0=0 PD,19,CM4:6,1 ;//BOOST 8=B66C0=0 PA,0,C66340,0 ;//FUEL BOOST PUMP 1 9=B66C0=0 PA,1,C66341,0 ;//FUEL BOOST PUMP 2 10=B66C0=0 PA,2,C66342,0 ;//FUEL BOOST PUMP 3 11=B66C0=0 PA,3,C66343,0 ;//FUEL BOOST PUMP 4 12=PA,4,Cx510066C0,x00060001 ;//CONTROL SET INC Max = 6 Step = 1 13=PA,5,Cx610066C0,x00060001 ;//CONTROL SET DEC Max = 6 Step = 1 14=PD,20,CM4:5,1 ;//ADI ON 15=UD,20,CM4:5,0 ;//ADI OFF 16=PA,8,CL2:R,0 ;//REVERSE THRUST ON 17=UA,8,CL1:R,0 ;//REVERSE THRUST OFF 18=PC,10,C1079,0 ;//TRAFFIC ZAPPER !2=//SET 1 GENERATORS,CARB HEAT/AIR/TURBOS 20=B66C0=1 PD,14,C66363,0 ;//GEN 1 21=B66C0=1 PD,15,C66364,0 ;//GEN 2 22=B66C0=1 PD,16,C66365,0 ;//GEN 3 23=B66C0=1 PD,17,C66366,0 ;//GEN 4 !3=//----------- THE FOLLOWING CODE EXECUTES "ON EVENT" CALLS TO A LUA PLUGIN ------ !4=//----------- THE EVENTS ARE CHANGES TO LOCATIONS 0X6662, 0X66C3, 0X66C4 ------ 24=B66C0=1 PD,18,Cx010066C2,x01 ;//CARB HEAT ON 25=B66C0=1 PD,19,Cx010066C2,x00 ;//CARB HEAT OFF 26=B66C0=1 PA,0,Cx010066C3,x01 ;//CARD AIR ON 27=B66C0=1 PA,1,Cx010066C3,x00 ;//CARB AIR OFF 28=B66C0=1 PA,2,Cx010066C4,x01 ;//TURBO CLIMP 29=B66C0=1 PA,3,Cx010066C4,x00 ;//TURBO TAKEOFF !3=//SET 2 AP/OIL/COWL/IC FLAPS SETUP 30=B66C0=2 PD,14,C65580,0 ;//AUTOPILOT MASTER 31=B66C0=2 PD,15,C65726,0 ;//ALTITUDE HOLD 32=B66C0=2 PD,16,CM4:9,2 ;//OIL XFER FORWARD 33=B66C0=2 UD,16,CM4:9,1 34=B66C0=2 PD,17,CM4:9,0 ;//OIL XFFER BACK 35=B66C0=2 UD,17,CM4:9,1 36=B66C0=2 PD,18,CM4:20,5 ;//OIL XFER ENGINE SELECT 37=B66C0=2 PD,19,C66465,0 ;//COMM RCVR AUDIO 38=B66C0=2 RA,0,Cx7C0037F0,x0000000F ;//COWL FLAPS 1 INC 39=B66C0=2 RA,0,Cx7C003730,x0000000F ;//COWL FLAPS 2 INC 40=B66C0=2 RA,0,Cx7C003670,x0000000F ;//COWL FLAPS 3 INC 41=B66C0=2 RA,0,Cx7C0035B0,x0000000F ;//COWL FLAPS 4 INC 42=B66C0=2 RA,1,Cx7C0037F0,xFFFFFFF1 ;//COWL FLAPS 1 DEC 43=B66C0=2 RA,1,Cx7C003730,xFFFFFFF1 ;//COWL FLAPS 2 DEC 44=B66C0=2 RA,1,Cx7C003670,xFFFFFFF1 ;//COWL FLAPS 3 DEC 45=B66C0=2 RA,1,Cx7C0035B0,xFFFFFFF1 ;//COWL FLAPS 4 DEC 46=B66C0=2 RA,2,Cx010066C1,x01 ;INTER-COOLER FLAPS INC VIA LUA PLUGIN NEW IMPLEMENTATION 47=B66C0=2 UA,2,Cx010066C1,x00 ;INTER-COOLER FLAPS SWITCHES OFF 48=B66C0=2 RA,3,Cx010066C1,xFF ;INTER-COOLER FLAPS DEC VIA LUA PLUGIN 49=B66C0=2 UA,3,Cx010066C1,x00 ;INTER-COOLER FLAPS SWITCHES OFF !4=//SET 3 RADAR ALTS/RMI 50=B66C0=3 PD,14,CM4:21,0 ;//RADAR ALTIMETER 1 ON/OFF 51=B66C0=3 PD,15,CM4:22,0 ;//RADAR ALTIMETER 1 RANGE SWITCH 52=B66C0=3 PD,16,CM4:23,0 ;//RADAR ALTIMETER 2 ON/OFF 53=B66C0=3 PD,17,CM4:24,0 ;//RADAR ALTIMETER 2 RANGE SWITCH 54=B66C0=3 PD,18,CM4:25,0 ;//RADAR ALTIMETER 3 ON/OFF 55=B66C0=3 PD,19,CM4:26,0 ;//RADAR ALTIMETER 3 RANGE SWITCH 56=B66C0=3 PA,0,CM4:27,0 ;//RMI 1 NAV/ADF TOGGLE 57=B66C0=3 PA,1,CM4:28,0 ;//RMI 2 NAV/ADF TOGGLE 58=B66C0=3 PA,2,C66719,0 ;//SEAT BELTS 59=B66C0=3 PA,3,C66718,0 ;//NO SMOKING !4=//SET 4 LIGHTS 60=B66C0=4 PD,14,CM4:29,0 ;//LANDING LIGHTS EXTEND/RETRACT 61=B66C0=4 PD,15,C65751,0 ;//LANDING LIGHTS ON/OFF 62=B66C0=4 PD,16,C66379,0 ;//NAV LIGHTS 63=B66C0=4 PD,17,C66376,0 ;//WHITE LIGHTS/PASSING LIGHT 64=B66C0=4 PD,18,C66240,0 ;//NOSE TAXI LIGHT 65=B66C0=4 PD,19,C66378,0 ;//GEAR TAXI LIGHTS 66=B66C0=4 PA,0,C66239,0 ;//BEACON 67=B66C0=4 PA,1,C65560,0 ;//STROBES 68=B66C0=4 PA,2,C65750,0 ;//RED LIGHTS 69=B66C0=4 PA,3,CM4:30,0 ;//EMERGENCY EXIT LIGHTS ARM !5=//SET 5 MIXTURE 70=B66C0=5 PD,14,Cx110066C5,x00030001 ;//INC Mixture1 through LUA routine MAX 3 71=B66C0=5 PD,15,Cx210066C5,x00000001 ;//DEC Mixture1 through LUA routine MIN 0 72=B66C0=5 PD,16,Cx110066C6,x00030001 ;//INC Mixture1 through LUA routine MAX 3 73=B66C0=5 PD,17,Cx210066C6,x00000001 ;//DEC Mixture1 through LUA routine MIN 0 74=B66C0=5 PD,18,Cx110066C7,x00030001 ;//INC Mixture1 through LUA routine MAX 3 75=B66C0=5 PD,19,Cx210066C7,x00000001 ;//DEC Mixture1 through LUA routine MIN 0 76=B66C0=5 PA,0,Cx110066C8,x00030001 ;//INC Mixture1 through LUA routine MAX 3 77=B66C0=5 PA,1,Cx210066C8,x00000001 ;//DEC Mixture1 through LUA routine MIN 0 78=B66C0=5 PA,2,CM4:19,0 ;//APU Start 79=B66C0=5 UA,2,CM4:19,2 ;//APU GEN ON 80=B66C0=5 PA,3,CM4:19,1 ;//APU OFF !6=//SET 6 MAGNETOS, BATTERY, AVIONICS 90=B66C0=6 PD,14,C66127,0 ;//MAGNETO 1 INC 91=B66C0=6 PD,15,C66126,0 ;//MAGNETO 1 DEC 92=B66C0=6 PD,16,C66129,0 ;//MAGNETO 2 INC 93=B66C0=6 PD,17,C66128,0 ;//MAGNETO 2 INC 94=B66C0=6 PD,18,C66131,0 ;//MAGNETO 3 INC 95=B66C0=6 PD,19,C66130,0 ;//MAGNETO 3 INC 96=B66C0=6 PA,0,C66133,0 ;//MAGNETO 4 INC 97=B66C0=6 PA,1,C66132,0 ;//MAGNETO 4 INC 98=B66C0=6 PA,2,C66241,0 ;//BATTERY 99=B66C0=6 PA,3,C66293,0 ;//AVIONICS !7=//INITIALIZE 100=PD,22,C1084,0 ;//KILL ALL LUA PLUGINS 101=UD,22,CL18:R,0 ;//RUN LUA PLUGIN 18 102=PD,11,CL18:D,1

Guenter, I have two small Lua plugins that implement the thrust reverse on the A2A B-377. I use a detent switch on my throttle quadrant to call the routines. The first routine is named "B377_reverse.lua" i = 0 ipc.keypress(112) ipc.sleep(250) while i < 14 do ipc.keypress(113) ipc.keypress(113) ipc.keypress(113) ipc.sleep(50) i = i + 1 end The second routine is named "B377_exit_revers.lua" i = 0 while i < 15 do ipc.keypress(114) ipc.sleep(50) ipc.keypress(114) ipc.sleep(50) i = i + 1 end The plugins merely send the F1, F2 and F3 keystrokes, as required, to obtain a smooth transition in and out of the reverse state. In my Saitek Pro dual throttle quadrant setup I have programmed my #4 throttle detent switch to trigger the 1st plugin when I pull the throttles back to the detent and the 2nd plugin when I push the throttles forward out of detent. The number of times the loops execute and the delays can be "tweaked" to your linking. Paul

To add to Ian's inputs here, if you connect two yokes or joysticks physically at the same time, you can go into the FSX Controls menu and disable the unused axis' to prevent contention. I currently have both my Saitek X-45 stick and throttle quadrant attached along with my Saitek Pro Yoke and quadrant plus an additional quadrant. I prefer flying with the X-45 stick so have disabled the Pro Yoke axis. Likewise, I prefer to use the Pro quadrants for throttles and have disabled the X-45 throttle axis. All the buttons and switches on both sets of devices are still usable. I also use the method Ian mentioned for renaming the FSX.exe file and associated CFG file so that I have different configurations available...FSX_Military.exe, FSX_Propliner.exe, FSX_OZ.exe and FSX_Test.exe. A registered version of FSUIPC completes my setup, enabling a whole range of configuration and customization options. I wouldn't do without that utility! Paul

Let me add my "Thanks" as well. The layout is now easy to navigate and use once again. Paul

WTF happened to the format of this forum? Suddenly it is virtually impossible to use it! There used to be definite delineation between the pinned topics and the new threads. Now it is just one jumbled mess of difficult to read topic headers. The font really sucks and the overall design is really bad! Why must something that WAS functional suddenly become less so, just to make things "pretty"??? Bring back the old forum software! Paul

You might be bettter off using a Lua routine and programming delays into the implementation of the FSX reverse thrust functions (F1, F2, F3) Here is what I did for the A2A B-377. I just use one of the detent switches on my dual throttle quads to implement the reverse thrust function. I pull all four throttles back to detent so they are at minimum and one of the switches triggers the action. My FSUIPC.ini entries pertaining to this discussion: [JoyNames] A=Saitek Pro Flight Quadrant . . . D=Saitek Pro Flight Yoke [LuaFiles] 1=B377_exit_revers 2=B377_reverse [Buttons.Boeing Stratocruiser] .. .. .. 16=PA,8,CL2:R,0 ;//REVERSE THRUST ON 17=UA,8,CL1:R,0 ;//REVERSE THRUST OFF The lines above call Lua the Lua routines below when the Saitek Pro throttle quad detent switch is activated and released. ------------------Lua files -------------- B377_reverse.lua file i = 0 ipc.keypress(112) ipc.sleep(250) while i < 14 do ipc.keypress(113) ipc.keypress(113) ipc.keypress(113) ipc.sleep(50) i = i + 1 end --------------------------------- B377_exit_revers.lua file i = 0 while i < 15 do ipc.keypress(114) ipc.sleep(50) ipc.keypress(114) ipc.sleep(50) i = i + 1 end I have done similar things with other aircraft. Lua gives you the ability to set the delays between subsequent programmed keystrokes so you can control the rate at which some events occur. This was probably one of my first uses of Lua plugins and I chose to use two files. In later programming implementations I combined several functions in a single file and used the FSUIPC user definable offsets (66C0 and up) to "trigger" various functions. Paul

Ah....I saw both posts in this forum. Sorry for the misunderstanding. Paul

Well, he did make this post within a few hours of another with the same subject line. That rather seemed to indicated a certain amount of impatience to me. Paul

Did you not see the note at the top of this forum that Pete is away until April 8th? Paul

According to your advanced user guide it says Error 19 is "The C.r K or M needed for Control,Key or Macro is missing" is that saying then that button 4 on joy 1 is missing? Sorry I keep bugging you with this, still trying to learn how to use FSUIPC. I believe the problem is that the command offsets ( 65751 and 66240 ) require a "C" preceding them. 19=CP(+1,4)1,8,C65751,0 20=CP(+1,4)1,9,C66240,0 Try that. Paul

You might want to read the "FSUIPC4 for Advanced Users" PDF file as that will explain a lot of the features which will allow you to expand the capabilities of your joystick switches and buttons. A couple of sections are of particular interest to anyone wishing to have multiple functions from a single switch or button. "Adding Offset Conditions" starting at the bottom of Page 18 "Appendix" on Page 42 Also refer to "List of FSX controls.pdf" I have a Saitek Pro Yoke with dual throttle quadrants and have set up the 6 double throw switches (12 switches functionally ) to provide me with 70 discrete actions in one particular aircraft specific situation. I used two of the switches to increment and decrement a value in the user-defined offset "66C0". The value contained in offset "66C0" determines what function any of the other 10 switches perform. Think of it as defining a number of "control sets", similar to the "Mode switch" on some sticks or the "pinky switch" to give a "shifted function". Here is an excerpt from my FSUIPC.ini file that defines the functions to be performed by the same two switches on one of my throttle quadrants. The switches are identified as #14 and #15 on joystick 3. The first number is merely a line number. The "B66C0=0" part indicates that the following code is executed only when location "66C0" contains a value of "0". "P3,14" indicates a button PRESSED on joy 3, button 14. The remainder of the line indicates the function to be executed. The first entry here says to send a value of "0" to the variable "19" in the MACRO file number 4. 0=B66C0=0 P3,14,CM4:19,0 ;//APU Start, on PRESS of button 14 1=B66C0=0 U3,14,CM4:19,2 ;//APU GEN ON, on release of button 14 2=B66C0=0 P3,15,CM4:19,1 ;//APU OFF on PRESS of button 15 . . 20=B66C0=1 P3,14,C66363,0 ;//GEN 1 Here a press of button 14 sends a "0" to offset 66363, Toggle GEN 1 21=B66C0=1 P3,15,C66364,0 ;//GEN 2 Here a press of button 15 sends a "0" to offset 66364, Toggle GEN 2 . . 30=B66C0=2 P3,14,C65580,0 ;//AUTOPILOT MASTER Here button 14 toggles thw AP Master switch 31=B66C0=2 P3,15,C65726,0 ;//ALTITUDE HOLD Here button 15 toggles the ALT HOLD function . . 50=B66C0=3 P3,14,CM4:21,0 ;//RADAR ALTIMETER 1 ON/OFF Here again a MACRO file is referenced, entry 21 receives a "0" 51=B66C0=3 P3,15,CM4:22,0 ;//RADAR ALTIMETER 1 RANGE SWITCH The same MACRO file, entry 22 receives a "0" Note that the value contained in "66C0" is what determines how a given switch functions. You can have as many different functions as you wish by simply dedicating one switch/button to change the value in "66C0". So after all this, the answer to your question is "yes". There is a method to test the condition of one button in order to change the function of another. mThat is in the section "COMPOUND BUTTON CONDITIONS" on page 16 of the Advanced Users files. I merely demonstrated a means to carry this to extreme with another method :) Paul

Thank you ALOT for those new features, Pete! I'll be adding the changes to my Lua plugins later tonight! Paul

It should auto-expand vertically to suit the number of lines you send. That is FS's doing, not mine. The width, though, is subject to user setting. Yes, it does auto-expand vertically but that is not the issue. I would like to get the default horizontal size to increase. You shouldn't need to add it manually. I thought FS saved it in any case. The FSUIPC autosave does include the Lua display parameters. The FSX save from the menu does not. I added it to that FLT file in hopes that the window would be the desired size when I loaded that saved flight. Alas, it was not. I don't know. Certainly not in anything of mine. FSUIPC simply calls FS routines for all this stuff. What FS version are you using? I'll have to do some experiments. The same mechanism is also used for the Radar Contact window and the applications window facility used via the FSUIPC offsets -- that's it, 3 separately named FS windows which FSUIPC can handle at present. Have you tried the undocked window? That saves separate size details in the FLT file I think. Regards Pete I am using FSX Accelleration with the latest rev of FSUIPC ( registered ) on WinXP Pro. I am hoping not to have to use the undocked feature as I want the display to disappear after the 10 second time in the display statement. This window is a "reminder" as to which controls are currently mapped to my Saitek dual throttle quadrant switches. I'll try specifying "undocked" as a test, however. I have 7 different sets of assignments so I need the "cheat sheet display". I use the FSUIPC logging function to display location 66C0 in the title bar. When I hit my incr/decr "Control Set" switches, I change the value in 66C0. This is my index for the 7 sets of control mappings. Thanks for including the capability to display a variable in the title bar!! :) Paul

Hello Pete, Using the "ipc.display" function in my Lua programs to display a multi-line meassage, I find I have to resize the Lua display window every time I load a flight in FSX. Even though there is a section in my saved FLT files that I assumed related to the position and size of the Lua display window created by the "ipc.display" statement, the window always begins at some default size which defeats my formatting...2 lines listing various control functions and a single line showing which control set is being displayed. A sample of one of my Lua plugin lines: ipc.display("MAGNETO INC 1 _ 2 _ 3 _ 4 _ INVERTER ON\nMAGNETO DEC 1 _ 2 _ 3 _ 4 _ INVERTER OFF\nControl Set = "..conset, 10) Which should display as: MAGNETO INC 1 _ 2 _ 3 _ 4 _ INVERTER ON MAGNETO DEC 1 _ 2 _ 3 _ 4 _ INVERTER OFF Control Set = 3 But instead displays as: MAGNETO INC 1 _ 2 _ 3 _ 4 _ INVERTER ON MAGNETO DEC 1 _ 2 _ 3 _ 4 _ INVERTER OFF Control Set = 3 When I resize the window it, of course, remains OK for the duration of the flight but reverts to the default on the next flight. Here are the sections of a couple of my saved flight FLT files: FLT file saved from the FSX dropdown menu with this section added by me: [LUA display] Undocked=False ScreenUniCoords=3674, 923, 3347, 578 UndocCoords=0, 0, 0, 0 FLT file autosaved by FSUIPC with the section included in the save by FSUIPC: [LUA display] Undocked=False ScreenUniCoords=3674, 923, 3603, 461 UndocCoords=0, 0, 0, 0 Is there somewhere else that the default window size is specified? Paul

Hello Dirk, I haven't looked at the 2D panel issues with FSX/TrackIR since I only fly aircraft with full, operational VC's. When FSX first came out I was very disappointed that they had neutered the 2D environment by eliminating all views but straight forward. In FS9 I was a "2D cockpit" flyer. All I can say is just get used to using mapped "pause" and "center" buttons for TrackIR and when going to the 2D panel just look straight ahead and "pause/center". I'm not sure if there is anything else available but you might check the TrackIR site, if you haven't already done so. Paul

Ah, I see the source of confusion I think. In my haste I didn't complete the entire name "HotKeySelect=" in the reference to the FSX feature. You append the "HotKeySelect=n" statement to the CameraDefinition.xxx sections of the aircraft.cfg file. When the key/switch/button assigned to key number "n" is pressed that CameraDefinition is activated. The key number, 0-9, corresponds to the FSX "View Camera x" entries in the Controls, Buttons/Keys menu. There you can assign a key/switch/button to Cameras 0, 4 - 9. So, to select a Camera Definition you link that definition in the aircraft.cfg file to the desired FSX "View Camera x" by (1)assigning it a number in the "HotKeySelect=" statement. You then (2) assign a key/switch/button to that "View Camera x" entry in the FSX menu. Likewise, you can assign that key/button/switch in FSUIPC. You still need to do step (1). To answer your TrackIR question, yes, I use it and wouldn't do without it now! :) I have a couple of keys on my X-45 set mto toggle the "enable" function and to activate the "center" function. I find that these are essential for being able to fly from the VC and be able to see all parts of the cockpit and activate those controls with tiny click-spot areas :) It is just a natural sequence for me now when I want to look beyond the 'limits' of the TIR view range to look momentarily in the OPPOSITE direction, hit the "Center" button and then look to where I wanted to be. When done, look straight at the screen and hit "Center" again. So to look further down, look UP, Center, and then look down. You can also "Pause" TIR and on any CameraDefiniton that has the "SnapPbhAdjust=" and "PanPbhAdjust =" set to "Swivel" and pan your view using the normal view hat switch to move your view around. I have an X-45 stick and throttle attached with the throttle axis disabled and a Saitek Pro yoke with two throttle quadrants with the yoke axis disabled. I use the X-45 stick to fly and use the throttles on the Pro quadrants. I use the switches and buttons on the stick the X-45 throttle and the two Pro quadrants. The yoke hangs on the side of my hutch, serving only as a connection point for the throttle quads :) Paul

Dirk, use the FSX "Hotkey=" feature and assign a hotkey to the CameraDefinition views you want to access instantaneously. In all my VC aircraft I have CameraDefinition.001 to .003 assigned to hotkeys and those hotkeys ( view switches ) mapped to my #2 hat on my X-45 stick. A flick of my thumb takes me to the right seat, the overhead view, the console view or back to the left set. Currently I do this through the FSX Controls menu. The "View Camera Select" assignments. This can also be done in FSX by using offsets 66851 through 66860. "VIEW_CAMERA_SELECT_0" through 9. In the aircraft.cfg file you can add a "HotKeySelect=n" statement at the end of each CameraDefinition.xxx" sections where "n" is the number of the camera view. So, if you assign CameraDefinition.001 to HotKey 5 by adding the HotKey statement, in FSUIPC you would assign a button/hat position/switch to "VIEW_CAMERA_SELECT_5", offset 66855. Hope this isn't too confusing. Paul

FWIW, I have a Saitek Pro Yoke and two throttle quadrants plus an X-45 stick and throttle attached to my system all the time. No conflicts. I use FSUIPC to assign the various axis and the switches on the dual quadrants. I don't use the yoke but it must be attached so that the quadrant that has the proprietary cable can be connected. I use the X-45 stick for flying but have the throttle axis disabled since my throttles are mapped to the Pro throttles. I use the old Saitek X-45 software to load a 'basic' profile that maps the various switches and buttons on the X-45 to things like gear up, flaps, etc. I do NOT use the Saitek software for the Pro setup since it can not co-exist with the X-45 version. ( I had the X-45 long before I bought the Pro stuff, thus all the basic stuff was programmed to the X-45 and I saw no need to change it ). You can use FSUIPC to create different profiles that map the various axis and switches as you desire for various aircraft. Use the yoke on those aircraft with yokes. Use the X-52 stick for aircraft that use a stick. Use the buttons and switches on both for all aircraft. It's just up to you how you want to configure any given setup. Read the FSUIPC documentation thoroughly to get a better understanding of what can be accomplished. As a side note, one can enable/disable various axis in the FSX controls menu but you would have to do that each time you wanted to change, where FSUIPC lets you do it more or less automatically. The same is true of the button and switch assignments and programming. Paul

That is the way reverse pitch is implemented on the Constellation. The red reverse pitch levers on the throttles are pulled back and then the throttles are advanced to increase RPM with the props in the reverse pitch region. On the B-377 it is entered by pulling the throttles back through the idle into the reverse zone. So, it is a case of "one size doesn't fit all" :) Paul