Button Flag Toggle (C1005) problem

[varadero129]

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

[Pete Dowson]

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).

By "constantly pressing" do you just mean "pressed" or "on", or pressing repeatedly, as in "on off on off ... etc"?

Now what I am trying to achieve is using the 3 way mode selector switch as toggling flags

Do you just mean using its position as a conditional to select different functions on others?

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).

What is the siginificance of the emboldening here?

And why use flags when, if the mode buttons are held on, or pressed, you can just use the button state itself as the condition? seems more complicated to use flags.

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.

Now I'm completely lost I'm afraid. Are you saying that in addition to the three modes selected by the 3-way mode sleector (buttons 23-25) you want other buttons or knobs to also act as mode selectors? Multiplying 3 x n different uses?

I looked at the log but I'm none the wiser. I can see that you have the "F" for flag set in all of your conditions -- which surely isn't needed if the selecting buttons stay pressed or on. I also see you using button 16's flag BUT you seem to also be manipulating it directly, as here:

27=P0,16,C1005,16 -- OKAY, it toggles Flag 16

This is a rather odd thing to do, considering that pressing 0,16 toggles its flag in any case. You want to toggle it twice? Usually the Button Flag controls are used for extra flags, on buttons you don't actually have (out of the 512 possibles). You never really want to use them for buttons you actually do have unless you never want to use those buttons. as the documentation says, here:

For every possible “normal” button (16 joysticks x 32 buttons = 512 buttons) FSUIPC4 maintains a “Flag” (F). Each time any button is pressed (goes from off to on) FSUIPC4 toggles its flag. This makes the buttons flag a sort of “latching” switch.

From those parts of what you say I think I understand, I think you only really want to make conditions based on the state of a button or switch, in which case you should use its Flag, just the button itself (+ for on, - for off).

Regards

Pete

[varadero129]

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).

By "constantly pressing" do you just mean "pressed" or "on", or pressing repeatedly, as in "on off on off ... etc"?

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

Do you just mean using its position as a conditional to select different functions on others?

Yes, using the mode select switch's AND any other secondary button's flag combination.

What is the siginificance of the emboldening here?

Just tried to point out this strange conditional issue.

And why use flags when, if the mode buttons are held on, or pressed, you can just use the button state itself as the condition? seems more complicated to use flags.

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 :)

I looked at the log but I'm none the wiser. I can see that you have the "F" for flag set in all of your conditions -- which surely isn't needed if the selecting buttons stay pressed or on. I also see you using button 16's flag BUT you seem to also be manipulating it directly, as here:

27=P0,16,C1005,16 -- OKAY, it toggles Flag 16

This is a rather odd thing to do, considering that pressing 0,16 toggles its flag in any case. You want to toggle it twice? Usually the Button Flag controls are used for extra flags, on buttons you don't actually have (out of the 512 possibles). You never really want to use them for buttons you actually do have unless you never want to use those buttons. as the documentation says, here:

From those parts of what you say I think I understand, I think you only really want to make conditions based on the state of a button or switch, in which case you should use its Flag, just the button itself (+ for on, - for off).

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

[Pete Dowson]

... 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.

Ah, so the "middle" button is used only when one of the 3 main modes is selected, so giving you a toal of 4 sets, not 3 or 6?

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).

If it's intended as a mode selection, than of course that is exactly what you want. Each of its three positions is "pressing" (turning "on" is a better notion) a particular button. As long as it isn't constantly turning it on and off, that's fine.

First I tried in FSUIPC.ini to make conditions like n=CP(+0,25)0,14,... but I realized that it didn't work.

Why wouldn't it work. The condition "(+0,25)" is TRUE if button 25 is on, or pressed.

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.

Now it gets confused again. Are you meaning that when you say

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).

as you did just above, that the button press of 23, 24 or 25 is momentary? You seem to be contradicting yourself.

I must have made some mistake, because now, according to your advice, I tried it again without using flags, and works perfectly with this:

The mistake of assuming "momentary" when, as you stated, it is anything but?

In your Button assignments:

Why have you still got a Flag value here instead of the simple button pressed state? A 'true' (+) flag value will only operate on every other time you set 24, because the button flags toggle on every press (press = change from off to on).

5=CP(F+0,24)0,15,C65615,0

6=CP(F+0,24)0,14,C65607,0

And what on Earth are all these flag toggling controls for when you aren't using button 0's flag anywhere?

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

If buttons 16 and 19 are real buttons which you press, why are you using flags here? Are you wanting alternate actions each time they are pressed and released?

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

Just tried to point out this strange conditional issue.

What strange conditional issue? Sorry, you've lost me again.

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

Er, no. That is really nonsense, sorry. If the parameter is 0 then it toggles the button flag for joystick 0 button 0. The computation 256*j + b is so you can get the parameter correct to operate that particular button flag. How would the C1005 command know which button flag to operate if you didn't give it a proper parameter?

I am happy that you pointed out that I overcomplicated this issue, and now I managed to get it work.

But it works DESPITE these lines

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

which will do nothing whatsoever for you if you have no conditions testing button 0! All those are toggling button 0's flag, nothing else at all!

You seem to have not read the part of the manual I even quoted to you in my last message, espevially the part I deliberately put in red! I'll repeat it here:

For every possible “normal” button (16 joysticks x 32 buttons = 512 buttons) FSUIPC4 maintains a “Flag” (F). Each time any button is pressed (goes from off to on) FSUIPC4 toggles its flag. This makes the buttons flag a sort of “latching” switch.

Please please please READ this again. What do you not understand? The button flags operate AUTOMATICALLY every time you press the relevant button. You do NOT need to control them. The only time you need to control button flags are when you need flags NOT operated by real buttons!!!

Hope this also help the others.

Actually, I'm rather hoping they read further and not get as confused as you! ;-)

Regards

Pete

[varadero129]

The mistake of assuming "momentary" when, as you stated, it is anything but?

Yes, I made a false assumption and started to go on the wrong way.

Ah, so the "middle" button is used only when one of the 3 main modes is selected, so giving you a toal of 4 sets, not 3 or 6?

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

In your Button assignments:

Why have you still got a Flag value here instead of the simple button pressed state? A 'true' (+) flag value will only operate on every other time you set 24, because the button flags toggle on every press (press = change from off to on).

5=CP(F+0,24)0,15,C65615,0

6=CP(F+0,24)0,14,C65607,0

I left it there unintentionally. Have corredted.

And what on Earth are all these flag toggling controls for when you aren't using button 0's flag anywhere?

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

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?

If buttons 16 and 19 are real buttons which you press, why are you using flags here? Are you wanting alternate actions each time they are pressed and released?

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 :))

For every possible “normal” button (16 joysticks x 32 buttons = 512 buttons) FSUIPC4 maintains a “Flag” (F). Each time any button is pressed (goes from off to on) FSUIPC4 toggles its flag. This makes the buttons flag a sort of “latching” switch.

Please please please READ this again. What do you not understand? The button flags operate AUTOMATICALLY every time you press the relevant button. You do NOT need to control them. The only time you need to control button flags are when you need flags NOT operated by real buttons!!!

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

[buttons]

...

13=CP(+0,24)(F-0,20)(F-0,21)(F-0,22)0,5,C65758,0 ; flaps_inc

14=CP(+0,24)(F-0,20)(F-0,21)(F-0,22)0,4,C65759,0 ; flaps_dec

15=CP(+0,24)(F-0,20)(F-0,21)(F-0,22)0,6,C66244,0 ; dec_cowl_flaps

16=CP(+0,24)(F-0,20)(F-0,21)(F-0,22)0,7,C66243,0 ; inc_cowl_flaps

17=CP(+0,24)(F-0,20)(F-0,21)(F-0,22)0,15,C65615,0 ; elev_trim_up

18=CP(+0,24)(F-0,20)(F-0,21)(F-0,22)0,14,C65607,0 ; elev_trim_dn

...

[Profile.Egymotoros kisgépek]

1=Cessna Skylane 182S Paint2

[buttons.Egymotoros kisgépek]

...

4=CP(+0,25)(F-0,20)(F-0,21)(F-0,22)0,4,C65750,0 ; panel_lights_toggle

5=CP(+0,25)(F-0,20)(F-0,21)(F-0,22)0,5,C66237,0 ; fuel_pump

6=CP(+0,25)(F-0,20)(F-0,21)(F-0,22)0,6,C66239,0 ; toggle_beacon_lights

7=CP(+0,25)(F-0,20)(F-0,21)(F-0,22)0,7,C65858,0 ; pitot_heat_toggle

8=CP(+0,24)(F-0,20)(F-0,21)(F+0,22)0,4,C66379,0 ; toggle_nav_lights

9=CP(+0,24)(F-0,20)(F-0,21)(F+0,22)0,5,C66240,0 ; toggle_taxi_lights

10=CP(+0,24)(F-0,20)(F-0,21)(F+0,22)0,6,C65751,0 ; landing_lights_toggle

Regards,

Tamas

[varadero129]

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.

418333 System time = 28/11/2010 20:49:00, FS2004 time = 20:48:54 (19:48Z)

418333 WeatherOptions set, now 605CB70D (timer=0)

423637 Button changed: bRef=0, Joy=0, Btn=5, Pressed

423637 [buttons.Cessna Skylane 182S Paint2] 5=CP(+0,25)(F-0,20)(F-0,21)(F-0,22)0,5,C66237,0

423637 .... Condition (+0,25) = FALSE

423637 [buttons.Cessna Skylane 182S Paint2] 9=CP(F-0,20)(F-0,21)(F+0,22)0,5,C66240,0

423637 .... Condition (F-0,20) = TRUE

423637 .... Condition (F-0,21) = TRUE

423637 .... Condition (F+0,22) = FALSE

423793 Button changed: bRef=0, Joy=0, Btn=5, Released

425306 Button changed: bRef=0, Joy=0, Btn=7, Pressed

425306 [buttons.Cessna Skylane 182S Paint2] 7=CP(+0,25)(F-0,20)(F-0,21)(F-0,22)0,7,C65858,0

425306 .... Condition (+0,25) = FALSE

425477 Button changed: bRef=0, Joy=0, Btn=7, Released

426148 Button changed: bRef=0, Joy=0, Btn=5, Pressed

426148 [buttons.Cessna Skylane 182S Paint2] 5=CP(+0,25)(F-0,20)(F-0,21)(F-0,22)0,5,C66237,0

426148 .... Condition (+0,25) = FALSE

426148 [buttons.Cessna Skylane 182S Paint2] 9=CP(F-0,20)(F-0,21)(F+0,22)0,5,C66240,0

426148 .... Condition (F-0,20) = TRUE

426148 .... Condition (F-0,21) = TRUE

426148 .... Condition (F+0,22) = FALSE

426273 Button changed: bRef=0, Joy=0, Btn=5, Released

426554 Button changed: bRef=0, Joy=0, Btn=7, Pressed

426554 [buttons.Cessna Skylane 182S Paint2] 7=CP(+0,25)(F-0,20)(F-0,21)(F-0,22)0,7,C65858,0

426554 .... Condition (+0,25) = FALSE

426710 Button changed: bRef=0, Joy=0, Btn=7, Released

427162 Button changed: bRef=0, Joy=0, Btn=4, Pressed

427162 [buttons.Cessna Skylane 182S Paint2] 4=CP(+0,25)(F-0,20)(F-0,21)(F-0,22)0,4,C65750,0

427162 .... Condition (+0,25) = FALSE

427162 [buttons.Cessna Skylane 182S Paint2] 8=CP(F-0,20)(F-0,21)(F+0,22)0,4,C66379,0

427162 .... Condition (F-0,20) = TRUE

427162 .... Condition (F-0,21) = TRUE

427162 .... Condition (F+0,22) = FALSE

427365 Button changed: bRef=0, Joy=0, Btn=4, Released

427552 Button changed: bRef=0, Joy=0, Btn=6, Pressed

427552 [buttons.Cessna Skylane 182S Paint2] 6=CP(+0,25)(F-0,20)(F-0,21)(F-0,22)0,6,C66239,0

427552 .... Condition (+0,25) = FALSE

427552 [buttons.Cessna Skylane 182S Paint2] 10=CP(F-0,20)(F-0,21)(F+0,22)0,6,C65751,0

427552 .... Condition (F-0,20) = TRUE

427552 .... Condition (F-0,21) = TRUE

427552 .... Condition (F+0,22) = FALSE

427724 Button changed: bRef=0, Joy=0, Btn=6, Released

427958 Button changed: bRef=0, Joy=0, Btn=4, Pressed

427958 [buttons.Cessna Skylane 182S Paint2] 4=CP(+0,25)(F-0,20)(F-0,21)(F-0,22)0,4,C65750,0

427958 .... Condition (+0,25) = FALSE

427958 [buttons.Cessna Skylane 182S Paint2] 8=CP(F-0,20)(F-0,21)(F+0,22)0,4,C66379,0

427958 .... Condition (F-0,20) = TRUE

427958 .... Condition (F-0,21) = TRUE

427958 .... Condition (F+0,22) = FALSE

428114 Button changed: bRef=0, Joy=0, Btn=4, Released

428395 Button changed: bRef=0, Joy=0, Btn=6, Pressed

428395 [buttons.Cessna Skylane 182S Paint2] 6=CP(+0,25)(F-0,20)(F-0,21)(F-0,22)0,6,C66239,0

428395 .... Condition (+0,25) = FALSE

428395 [buttons.Cessna Skylane 182S Paint2] 10=CP(F-0,20)(F-0,21)(F+0,22)0,6,C65751,0

428395 .... Condition (F-0,20) = TRUE

428395 .... Condition (F-0,21) = TRUE

428395 .... Condition (F+0,22) = FALSE

428566 Button changed: bRef=0, Joy=0, Btn=6, Released

[varadero129]

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

[Pete Dowson]

Okay, about flags. Is that correct, that if I press real buttons, its flag is being toggled from false to true and vica versa?

Yes. That's what this says, isn't it?

Each time any button is pressed (goes from off to on) FSUIPC4 toggles its flag. (third time! ;-) )

So, as you mentioned, I don't need to set anything like I tried (e.g. n=P0,20,C1005,0).

Not if you only want to use the button flag owned by that button, else it would be done twice and you'd get odd results of course. Besides which, using the parameter of 0 with control C1005 would toggle button 0 flag which you aren't using in any case! As I already explained.

Setting flags manually is for simulating if another button would be pressed, right?

It's for setting something which you can test elsewhere, like a memory. That's what flags are for.

That's right. I prefer not to hold them while pressing the other button.

But your main mode buttons are actually held "pressed" ("on" is a better term for such switches) by virtue of the switch position, right? So no need for flags there. I assume you are talking about button 16?

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 is clearly stated in the documentation too (in the main User Guide in fact). Aircraft or Profile specific assignments for the same buttons or keys take precedence over generic assignments when that aircraft is loaded or a profile is in operation. It would be rather stupid for them not to, causing all sorts of confusion with double actions, don't you see?

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

Sorry, what IS the problem? You forgot to say ...

In your later post:

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.

"Workaround"? Workaround for what? You still haven't described a problem! :-(

If you want things to operate for all aircraft you put them in the generic section. Anything in a Profile will override assignments for the same buttons in the generic section. Think about it -- there's no other way it can work.

Pete

[varadero129]

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

[Pete Dowson]

Can you please suggest a good existing topic for joystick calibration issues or I should create a new one?

All new questions should be in their own thread. These aren't "topics" but "threads" -- exchanges between usually two people, maybe others jumping in to help or confirm things. But adding you own queries to an existing thread which may or may not have some similarity is just confusing. Sometimes people have added something to a long dead (months or even years old) thread saying basically "me too" to a problem that was long fixed.

It's okay to look for similar threads to see if you can find the answers, but if not then there's unlikely to be anyone else with exactly your question in any case.

The documentation does actually contain a LOT of information on joystick calibrations, so you should not have any problems or questions in any case. Everything you mention should be a doddle.

Pete

[varadero129]

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

Tamas