varadero129

Dear Pete, In the users guide in your example you assign axis throttle1 set and axis throttle2 set to the same axis. Then in the section when you write about the 10 ranges for action, you mention gear up and gear down. Having read through these I am not sure how to setup my throttle lever 1 to function as throttle 1 when in the upper range and reverser 1 when in the lower range. Here is how I try it: on the left side I choose send direct to FSUIPC Calibration and I check 2 checkboxes and select Throttle 1 and below Reverser 1. I move the lever about to middle position and on the right side I setup the range 1 function. I click on From, move the lever full up, and click on To. I check Up, and set Control sent when ragne entered Throttle 1 Inc. Okay, now I try to setup reverser 1. Move the lever to the middle, setup range #2, click on From, move the lever fully down, check Down checkbox, and Control sent when range entered.... I cannot find Reverser 1. How to do this correctly? Regards, Tamas

I dissapeared for some days, due to programming my effective 8 buttons wiht the 9 mode button combinations and at present my FSUIPC.INI file is 29kbytes big. I spent many hours on assigning the overhead functions, and your tip helped me. Now I read about the mouse macro, I was able to create some, except for that one with the throttle quadrant. I haven't found a proper command for speedbrake arm/disarm, and flight detent. When I tried to create the mouse macro for this, and pressed TAB to test it, it only swithed that lever up to speadbreak off position. With the mouse it is a little bit difficult, because you have to click and pull the lever down to move it to flight detent position. Can you help me finding the way to program this function to a button press? I will also have a question for the axes configuration, but in another thread. Tamas

Actually, I saw that macro file, viewed it with notepad, but because I planned not to use mouse macros, I omitted reading that part of the documentation. This way it seemed cryptic to me. I will read it and try using the provided mouse macro. Sorry, if this is also mentioned there, but do you think I should be careful with the window size / screen resolution? I mean mouse macros usually use x,y coordinates, and I have a widescreen 1920x1080 monitor. Thanks for the tip. Regards, Tamas

Dear Pete, In PMDG 737NG I would like to find the best solution to toggle the controls of the overhead panel. I found that in the PMDG menu there are key commands e.g. for the MCP and EFIS, but there aren't commands for the overhead panel. I tried a lot of the controls in your controls list document, but except for the lighting commands, the others don't seem to work :( What is the best way to get them working? Regards, Tamas

Okay, thank you! I am very satisfied with your customer support. You are a patient man! :) Tamas

Okay, now I can say I understood how flags work. I just mentioned these again to confirm I understand them correctly. My problem with those buttons where that in the general section I set them up with one condition and in the profile specific section with another condition. I wanted to achieve that if the first condition is true then that would be profile independent, but if other conditions are true then that usage would be profile specific. This is what was impossible to do, but I copy-pasted the conditions from the general section to the profile specific one, and now it works fine. Can you please suggest a good existing topic for joystick calibration issues or I should create a new one? In my case my joystick has 3 throttle axises (basically the black one for throttle, the blue one for prop, and the red one for mixture). For cessna-like aircrafts that's fine, but I also fly PMDH 737NG. In this case I would like to configure them to use the black and blue lever as separate throttle lever for engine 1 and 2 (maybe for B747 I would want it to use for throttle 1-2 for the black and throttle 3-4 for the blue lever) and at the same time setup their lower regions as reversers. I know that there is a joystick calibration issue in the documentation, so probably if I get there (get to setting up yoke for B737) I can deal with the doc and I might have question then. Regards, Tamas

Now I copy-pasted those lines from general section to the profile specific one, and it works. I think it won't cause any problems. This workaround is fine for me. Tamas

And I forgot to copy-paste the log entries. It seems that it ignores the conditions in the general section. When I try to press buttons 4 or 5, 6, 7 my rotary is in middle position (24 is pressed) and 20 AND 21 AND 22 flag is unset. This way I expect flaps_inc, flaps_dec, dec_cowl_flaps, inc_cowl_flaps work, but they don't. Maybe inc_cowl_flaps is because due to InitialButton sequence it is already fully open, but the other three should work.

Yes, I made a false assumption and started to go on the wrong way. Negative, sir. I uploaded a picture of the same kind of yoke as mine, to let you better see my intentions. Please check it: http://bagotamas.hu/Tamas_MAH180.jpg I left it there unintentionally. Have corredted. I think it only is getting clearer for me now. Sorry Pete for being this difficult :) I just need to get over the initial barriers and really understand its mechanism. Okay, about flags. Is that correct, that if I press real buttons, its flag is being toggled from false to true and vica versa? So, as you mentioned, I don't need to set anything like I tried (e.g. n=P0,20,C1005,0). Setting flags manually is for simulating if another button would be pressed, right? That's right. I prefer not to hold them while pressing the other button. Rather I want to use it like CapsLock on the keyboard. When I don't need that flag, I press it again, and the flag clears (now I understand, thanks to you :)) Sorry about that. I really feel shamed, as I'm an IT guy (not programmer but database admin) and I also hate when my users don't read manuals. :) All day today I have been configuring :) and somehow rearranged things, added comments in the .ini file, and now almost everything seems to work fine, except for some buttons. My question is (sorry if it was written in the doc too, I might have not recognized it) that if a button is defined both in the general section and in the profile specific section, in this case is it possible that it only recognizes the button in the profile specific section, and ignore it in the general section? (It seems to be stupid to define it here and there as well, but certainly I mean it under different conditions) I copy-paste here the relevant part. My problem is now with buttons 0,4; 0,5; 0,6 If button 0,24 is pressed AND flag 0,20 is unset AND flag 0,21 is unset AND flag 0,22 is unset Regards, Tamas

I try to explain my intentions better and answer to your questions. My goal is to program the joystick in a way where I can use its buttons to control as many functions as possible, and also to group these functions in some logical way (otherwise I think I wouldn't remember which buttons did I put those funcitons). For this I am trying to use the mode selector switch, and the three buttons in the front panel of the yoke, plus the middle button of the two rotary switches. E.g. If I rotate the mode switch to the right, I would like to use those functions necessary when I startup the engine, make initial settings after contacting ATC (on IVAO via IvAp client) like squawk code, Kohlsman etc. Then if I turn it on the left, I would use functions like setting flaps, autopilot, and after airborne I would turn it in the middle position and this way I would use the rotary buttons for setting trim, or if I want (and toggle another flag of the 8 ones) I can use them for setting ILS freq and course and so on. So I have 8 buttons to use them as secondary or conditional buttons (the three mode switch buttons, the three buttons below, and the two ones in the middle of the rotary buttons) while I have 20 other buttons to operate the funcitons. I planned things to work differently if the mode selector is in one position AND one or two of the other buttons are also pressed (or toggled its flag). Actually, when I first checked it in Windows' control panel / controllers where I can calibrate joystick (or I could, but I want to calibrate it via FSUIPC) it seems that one of buttons 23, 24, 25 is constantly pressed (it is highlighted in Windows' control panel as if you would press a button and hold your finger on that). First I tried in FSUIPC.ini to make conditions like n=CP(+0,25)0,14,... but I realized that it didn't work. Then I checked the advanced user's guide, and I learned that for Controls (when you want FSUIPC to activate an FS control, rather than a keypress) only momentary function is possible. I must have made some mistake, because now, according to your advice, I tried it again without using flags, and works perfectly with this: [buttons] InitialButton=0,26 1=P0,5,C65758,0 2=P0,4,C66237,0 3=P0,6,C66059,0 4=P0,7,C66060,0 5=CP(F+0,24)0,15,C65615,0 6=CP(F+0,24)0,14,C65607,0 ButtonRepeat=20,10 10=P0,22,C1005,0 12=P0,20,C1005,0 19=P0,21,C1005,0 27=P0,16,C1005,0 28=P0,19,C1005,0 29=CP(+0,25)(F-0,16)0,14,C65651,0 30=CP(+0,25)(F+0,16)0,14,C65652,0 31=CP(+0,25)(F-0,16)0,15,C66455,0 32=CP(+0,25)(F+0,16)0,15,C66456,0 33=CP(+0,25)(F-0,19)0,17,C65653,0 34=CP(+0,25)(F+0,19)0,17,C65654,0 35=CP(+0,25)(F-0,19)0,18,C66457,0 36=CP(+0,25)(F+0,19)0,18,C66458,0 Yes, using the mode select switch's AND any other secondary button's flag combination. Just tried to point out this strange conditional issue. This is what helped me. You know, yesterday I was reading the documents for hours, planning my button config and sometimes made so stupid mistakes during the configuration (e.g. using the same sequence numbers in the .ini file after copy-pasting). I was really tired :) This one is an interesting thing. I might misunderstood something in the users guide, I didn't really understand why is it important to tell us the rules how it works (256*j+b rule), and I thought it is necessary to add this value as a parameter if I want to toggle or set a flag like 27=P0,16,C1005,16. But now I know that it isn't how it works, the correct way is n=P0,16,C1005,0 I am happy that you pointed out that I overcomplicated this issue, and now I managed to get it work. Hope this also help the others. Thank you, Pete! Regards, Tamas

Dear Pete, First of all, congratulations for your product. I am amazed how many things can be achieved using FSUIPC. I purchased a CH Eclipse Yoke and registered FSUIPC v3.96. Now I am trying to program the buttons. On this CH Yoke there is a 3 way mode selector switch (constantly pressing button 23 when switched to the left, 24 when center and 25 when on the right position). There are 3 push buttons under this (from left to right buttons 20, 21, 22), and there are two "cessna trim wheel like" buttons, one horizontally, one vertically. Also, these "rotary" buttons have a middle button, so it works like if you rotate the vertical one down, it is joystick button 15, rotating vertical up is button 14 and pressing vertical in the middle is button 16. The horizontal rotary button is like this, left 17, right 18, pressing in the middle is button 19. Now what I am trying to achieve is using the 3 way mode selector switch as toggling flags, to let me assign buttons for different uses. First I am programming it for Cessna 182. I have made a Profile for "Egymotoros kisgépek", this is single prop lightweight aircrafts in Hungarian. On the ground I want to control Master battery alternator, Magnetos, Avionics master and transponder squawk code when the mode selector is turned to the right (constant button 25 is present) The battery, magnetos works fine, and the mode selector dependent flag settings are also perfect. (I am using Button flag set, Button flag clear for this as when I turn the rotary and it constantly presses button 25, flag is set, and when I turn it to another position, upon releasing button 25 it clears the flag. That is working fine). I have problem with using buttons 16 and 19 (the middle button with the horizontal and vertical rotary buttons, so when I don't turn them but press them, I want them to use for Button flag toggle, to let the rotary movement (buttons 14, 15) inc or dec XPNDR 1000 or XPNDR 100 dependent of the state of the flag 16, similarly with rotary 17, 18 should change between inc or dec XPNDR 10 and XPNDR 1 depending on the button 19 flag is on or off. I turned on logging, and would like you to help me achieving this. In this log (I only copy-paste the relevant part, not to be so long) you can see, my joystick number is 0, and there is another functionality for buttons 14, 15 like elevator trim down and up (but this I want to be active only when the mode selector switch is set to button 24). I rather attach it then copy paste, it would be too long. Thanks in advance. Regards, Tamas Tamas_MAH180.txt