I want to assign one of my CH Throttle quadrant toogle switches to increase and decrease QNH, but I did not find the QNH Incr adn QNH decr in the FSUIPC menu items, how can I set it up. ThanksJuan

I want to assign one of my CH Throttle quadrant toogle switches to increase and decrease QNH, but I did not find the QNH Incr adn QNH decr in the FSUIPC menu items, how can I set it up. ThanksJuan

HelloUse Kohlsman inc and Kohlsman dec

Does FSUIPC have all assignments for fs2004? What if you want to assign a let's say: Ctrl + tab for something, does it let you do this?

Thank Mad Dog, I had no idea what Kohlsman was.Yes Boeingsta, FSUIPC can do that and much more, read the manual and the advanced guide.RegardsJuan

Does FSUIPC have all assignments for fs2004? What if you want to assign a let's say: Ctrl + tab for something, does it let you do this?

HelloDownload the FSCONTROLS doc from http://www.schiratti.com/dowson.htmlIt lists all of the FScontrols accessible from fsuipc, many more than are available through the sims key assignment page.CTL+TAB is not able to be used, but pretty much any other key combination is OK.Download the Fsuipc documentation and read it though,it is very good.If you are at all interested in key and button programming then Fsuipc is all you need but that is only scratching the surface of what it can do.Mouse macros - conditional button programming - Lua Scripts - weather smoothing - axis programming the list is endless.All of that in 280k of code, amazing stuff

Yea it looks amazing, but what i mean is, will it configure for payware aircraft like PMDG and PSS panels? Like when you assign controls via FSUIPC does it work for the payware aircraft or do you have to reassign it for those aircraft via their assigning methods (PSS hasit's own configuration thing that doesn't work via FS2004 commands i think, you must program using the PSS method for joystick things to work i think...).

Yea it looks amazing, but what i mean is, will it configure for payware aircraft like PMDG and PSS panels? Like when you assign controls via FSUIPC does it work for the payware aircraft or do you have to reassign it for those aircraft via their assigning methods (PSS hasit's own configuration thing that doesn't work via FS2004 commands i think, you must program using the PSS method for joystick things to work i think...).

HelloUsing the PSS 757 as an example,the PSS keymapping tool assign key presses to panel actionsnot to joysticks. For example lets take the LNav function and assign it to CTL+NNow when you press CTL+N LNav is selected on the panel.This is where Fsuipc comes in, it allows you to program a joystick button to send CTL+N which then selects LNav on the panel.Notice in this pic I have selected the Profile specific? checkbox, this makes the programming specific to the loaded aircraft and the assignments will be automatically loaded every time that aircraft is loaded into the Sim.I have pressed a button in this example on one of my goflight units and Fsuipc shows joy#174 button 6#.On the right I have selected the send keypress checkbox and filled in CTL+N in the box.Now when I press that button Fsuipc will send CTL+N to the PSS panel and activate LNav.This is just one of the reasons we use Fsuipc.Hope that helps make things clearer.The Keymapping tools in for example the PMDG 737 and PSS aircraft allow you to program panel functions to key combinations not joystick buttons, we need a way to translate these key presses into button presses.

HelloUsing the PSS 757 as an example,the PSS keymapping tool assign key presses to panel actionsnot to joysticks. For example lets take the LNav function and assign it to CTL+NNow when you press CTL+N LNav is selected on the panel.This is where Fsuipc comes in, it allows you to program a joystick button to send CTL+N which then selects LNav on the panel.Notice in this pic I have selected the Profile specific? checkbox, this makes the programming specific to the loaded aircraft and the assignments will be automatically loaded every time that aircraft is loaded into the Sim.I have pressed a button in this example on one of my goflight units and Fsuipc shows joy#174 button 6#.On the right I have selected the send keypress checkbox and filled in CTL+N in the box.Now when I press that button Fsuipc will send CTL+N to the PSS panel and activate LNav.This is just one of the reasons we use Fsuipc.Hope that helps make things clearer.The Keymapping tools in for example the PMDG 737 and PSS aircraft allow you to program panel functions to key combinations not joystick buttons, we need a way to translate these key presses into button presses.

Wonderful answer mad dog! Just what i needed! Got my queries sorted (most of them anyways). With the help of pics it makes it alot easier to understand.Thanks!:(

If you are short of joystick buttons you can via a licensed FSUIPC use buttons in combination to other buttons to increase the number of commands you can give:By example: a joystick with 8 buttons -> 8 commands1 button in combination with 7 -> 14 commands: - button off in combination with the one of the 7 others, - button on in combination with one of the seven others,2 buttons in combination with 6 -> 24 commands: - 2 buttons off in combination of the 6 others, - button 1 on, button 2 off in combination with one of the 6, - button 1 off, button 2 on ... - button 1 on, button 2 on ...3 buttons in combination with 5 -> 40 commands 4 buttons in combination with 4 -> 64 commands!The last two combinations aren't practical ;-)Hugo

If you are short of joystick buttons you can via a licensed FSUIPC use buttons in combination to other buttons to increase the number of commands you can give:By example: a joystick with 8 buttons -> 8 commands1 button in combination with 7 -> 14 commands: - button off in combination with the one of the 7 others, - button on in combination with one of the seven others,2 buttons in combination with 6 -> 24 commands: - 2 buttons off in combination of the 6 others, - button 1 on, button 2 off in combination with one of the 6, - button 1 off, button 2 on ... - button 1 on, button 2 on ...3 buttons in combination with 5 -> 40 commands 4 buttons in combination with 4 -> 64 commands!The last two combinations aren't practical ;-)Hugo

Yo, um...I dont get that maths :(. How are those possible?

Ok, here we goI am using a MS Sidewinder Force Feedback 2 joystick with 8 buttons and I am using the two extreme left buttons (button 6 and 7) in combination to the other 6. You have 4 states for the combination of button 6 and 7 (6 up and 7 up, 6 pushed and 7 up, 6 up and 7 pushed, 6 pushed and 7 pushed) Each state in combination with one of the other buttons can now be programmed to give a particular command so you can have 4x6=24 commands. (with FSUIPC you could even give 48 commands, a command when the button goes down, and an other when the button goes up, which could be interesting in some situations, but I don't use that)Now comes the trick, this programming has to be done in the FSUIPC.INI it self with "notepad" by example, it can't be done via the FSUIPC interface: As specified in the “Advanced Users Manual”, two kinds of commands can be generated: use the button combination to simulate a hit of a key combination on the keyboard or use the joystick button combination to generate an “internal” FS command. A list of all the possibilities for these commands can be found in the “FS2004Controls” document. Let us take a few rules out of a button programming as examples:3=CP(-0,6)(-0,7)0,3,C65615,0 . .9=CP(+0,6)(-0,7)0,3,C65769,0In these both cases the active button (the button that is generating the command) is button 3. In the first case the command “65615” is generated when button 6 and 7 are up and button 3 is going down. C65615 will generate an “Elevator Trim Up”, the same command as the default joystick button programming. The “CP” syntax defines that the command will be only executed once, even if the button 3 is down.However, by holding down the “6” button and activating button 3, FSUIPC will generate a “65769, Propeller Pitch Increment”, command. This command is not a default joystick button command, but a command that, if it was not programmed that way, had to be entered by a button combination on the keyboard. By defining the button combination with a “CR”, the command will be repeated until the action button is released again, which is in our application more advantageous. And in fact, the repeat function is used on both commands:2=CR(-0,6)(-0,7)0,2,C65607,03=CR(-0,6)(-0,7)0,3,C65615,0 . .8=CR(+0,6)(-0,7)0,2,C65771,09=CR(+0,6)(-0,7)0,3,C65769,0The buttons “2” and “3” are used here to trim up/down (rule 2 and 3) with button 6 and 7 up. The same buttons, but now with button 6 activated while button 7 is up, controls the propeller pitch. I assigned another two commands to the same “2” and “3” buttons; also I programmed the combination with the 7 button for “Mixture Incr.” and “Mixture Decr.” in rule 19 and 20: 19=CR(-0,6)(+0,7)0,2,C65775,020=CR(-0,6)(+0,7)0,3,C65777,0I must emphasis here in the case of FSUIPC, the program uses the status (up or down) of the buttons in the compound combinations (+/-j,:((+-j,:( for a condition. But the changes of the button status, in fact “the pushing” or “the releasing” of a joystick button for the activation of the command. And this change is valid for one whole scan, meaning the check of all following button programming rules. This is important to remember.Here is a part of my real Button Programming in FSUIPC.ini:[buttons]ButtonRepeat=20,10PollInterval=50InitialButton=0,7 ; simulate 7 goes down for one scan0=CU(-0,7)0,6,C1003,10 ; 7 is up and 6 goes up, set flag 101=CU(-0,6)0,7,C1003,10 ; 6 is up and 7 goes up2=CP(-0,7)0,6,C1004,10 ; 7 is up and 6 goes down, reset flag 103=CP(-0,7)0,6,C1003,11 ; 7 is up and 6 goes down, set flag 114=CU(F+0,11)0,6,C1004,11 ; flag 11 set and 6 goes up, reset flag 115=CP(-0,6)0,7,C1004,10 ; 6 is up and 7 goes down, reset flag 106=CP(-0,6)0,7,C1003,12 ; 6 up and 7 goes down, set flag 127=CU(F+0,12)0,7,C1004,12 ; flag 12 is set and 7 goes up, reset flag 128=CP(F+0,11)0,7,C1004,11 ; flag 11 is set and 7 goes down, reset flag 119=CP(+0,6)0,7,C1003,13 ; 6 is down and 7 goes down, set flag 1310=CU(F+0,13)0,7,C1004,13 ; flag 13 is set and 7 goes up, reset flag 1311=CP(F+0,12)0,6,C1004,12 ; flag 12 is set and 6 goes down, reset flag 1212=CP(+0,7)0,6,C1003,13 ; 7 is down and 6 goes down set flag 1313=CU(F+0,13)0,6,C1004,13 ; flag 13 set and 6 goes up, reset flag 1314=W0BE8=0 CP(F+0,10)0,0,K32,8 ; If gear up, initialize TrackIR, (SPACE)15=W0BE8 CR(F+0,10)0,0,C65588,0 ; If gear down, break16=CP(F+0,10)0,1,C65570,017=CR(F+0,10)0,2,C65607,018=CR(F+0,10)0,3,C65615,019=CP(F+0,10)0,4,C65758,020=CP(F+0,10)0,5,C65759,021=CP(F+0,11)0,0,C65752,122=CP(F+0,11)0,1,C65751,023=CR(F+0,11)0,2,C65771,024=CR(F+0,11)0,3,C65769,025=CP(F+0,11)0,5,C65589,026=CP(F+0,12)0,1,C65858,027=CR(F+0,12)0,2,C65777,028=CR(F+0,12)0,3,C65775,029=CP(F+0,12)0,4,K83,830=CP(F+0,12)0,5,K83,931=CP(F+0,13)0,0,C1005,3132=CP(F+0,13)(F+0,31)0,0,C66224,033=CP(F+0,13)(F-0,31)0,0,K112,1134=CP(F+0,13)0,1,C66293,035=CP(F+0,13)0,2,C66244,036=CP(F+0,13)0,3,C66243,0[buttons.SD Yak-40]InitialButton=0,714=W0BE8=0 CP(F+0,10)0,0,K32,8 ; Gear Up (Space) for init IR 15=W0BE8 CR(F+0,10)0,0,C65588,0 ; Gear Down Break16=W0366=0 CP(F+0,10)0,1,C65570,0 ; In the air : Gear toggle17=W0366 CR(F+0,10)0,1,K112,8 ; On ground F118=W0366 CR(F+0,10)0,1,K113,8 ; On ground F2 Reverser19=CR(F+0,10)0,2,C65607,020=CR(F+0,10)0,3,C65615,021=CR(F+0,10)0,4,K118,8 ; F7 (Flaps down)22=CR(F+0,10)0,5,K117,8 ; F6 (Flaps up)23=CP(F+0,11)0,0,C65752,1 ; Parking break toggle24=CP(F+0,11)0,1,C65751,0 ; Landing lights25=CR(F+0,11)0,2,C65771,0 ; 26=CR(F+0,11)0,3,C65769,0 ; 27=CP(F+0,11)0,4,K119,8 ; Full flaps28=CP(F+0,11)0,5,K116,8 ; Flaps Up29=CP(F+0,12)0,1,K112,8 ; F130=CP(F+0,12)0,1,K113,8 ; F2 Reverser31=CR(F+0,12)0,2,C65777,032=CR(F+0,12)0,3,C65775,033=CP(F+0,12)0,4,K83,834=CP(F+0,12)0,5,K83,935=CP(F+0,13)0,0,C1005,3136=CP(F+0,13)(F+0,31)0,0,C66224,037=CP(F+0,13)(F-0,31)0,0,K112,1138=CP(F+0,13)0,1,C66293,039=CP(F+0,13)0,2,C66244,040=CP(F+0,13)0,3,C66243,041=CP(F+0,13)0,4,K87,11Hugo