Go Flight

Okay, thanks again Thomas: I tried and it works.
Very useful indeed, e.g. you can toggle on and off all window heating system switches at a time, controlled by single bits, if you happen to have only one hardware switch. This way, you need adding no more lines to the logics file to synchronize the switches in the "soft" way ...

As for driving the various knobs, with 3, 4, 7 o 8 positions, can you please tell me - talking about the Offset Byte Cyclic Increase / Decrease - what's the correct syntaxe of the parameter field ?

I saw there is a x/y format ... what exactly is x and what is y ?

Thanks in advance !

Quote:

---

Originally Posted by eudoniga

Okay, thanks again Thomas: I tried and it works.
Very useful indeed, e.g. you can toggle on and off all window heating system switches at a time, controlled by single bits, if you happen to have only one hardware switch. This way, you need adding no more lines to the logics file to synchronize the switches in the "soft" way ...

As for driving the various knobs, with 3, 4, 7 o 8 positions, can you please tell me - talking about the Offset Byte Cyclic Increase / Decrease - what's the correct syntaxe of the parameter field ?

I saw there is a x/y format ... what exactly is x and what is y ?

Thanks in advance !

---

Byte Cyclic Increase
5/1
increase the Byte by one up to 5, then it starts at 0 again.

Byte Cyclic Decrease
0/1
decrease the Byte by one down to 0.

Quote:

---

Originally Posted by EW321

Byte Cyclic Increase
5/1
increase the Byte by one up to 5, then it starts at 0 again.

Byte Cyclic Decrease
0/1
decrease the Byte by one down to 0.

---

Ah, my documentation evidently leaves something to be desired. Sorry.

If you are editing the FSUIPC INI file, the parameter is:

xAAAABBBB where AAAA is the limit, and BBBB is the increment/decrement.

In the Keys or Buttons tab in FSUIPC options, the same thing would be given by

xBBBB/AAAA in hex (or simply B/A in decimal)

and it doesn't matter whether it is an increment or decrement -- the limit is the value at which it either loops to 0 (for an increment) or from 0 (for a decrement).

So to re-do your examples, Thomas:

Byte Cyclic Increase
1/5 increases the Byte by one up to 5, then it starts at 0 again.

Byte Cyclic Decrease
1/5 decreases the Byte by one down to 0, then it starts at 5 again.


I'm a bit sad that my documentation is no good. Here's the important parts which seem to have been ignored (there's a complete "boxed" part in the User Guide about this):

Quote:

---

<increment value=""> increment value/limit <limit>

---

See ... isn't it clear that it is the opposite way around to your examples?

The decrement example perhaps isn't quite so clear:

Quote:

---

256/–16383 (–16383 being the lower limit).

---

Perhaps what should have been pointed out is that this "limit" is the end of the range for which, in the case of "cyclic" values, is the one which isn't 0. The other end is always 0. There's no point in giving a limit of 0 because that's always assumed as one of the limits, and if both limits are 0 you can get, er, stuck! ;-)

Sorry if it is confusing. It was all meant to be so simple ...

Pete
</limit></increment>