Compound Btn Condition - Doesn't appear to function in FS9

[ptwaugh]

Hi,

After reading alot in this forum, and reading the user docs and adv user docs, I began really playing with things.

In FS9, with FSUIPC 3.129:

I am attempting to setup [buttons] to change the view forward twice by sending two (2) 's' keypresses, so that the user can push a joystick btn and change easily from the VC view to the spot view and back.

This worked:

[buttons]

0=R0,7,C1001,0

1=U0,7,C1002,0

2=P0,0,K83,8

3=P0,0,K83,8

4=U0,0,K83,9

5=U0,0,K83,9

with the user holding the 'trigger' (j0, b0), and then I wanted to try a toggle like this:

[buttons]

0=R0,7,C1001,0

1=U0,7,C1002,0

2=CP(-j0,b1)0,0,K83,8

3=CP(-j0,b1)0,0,K83,8

4=CP(+j2,b1),0,K83,9

5=CP(+j2,b1)0,0,K83,9

which also seemed to function properly (but now I see an error). I was using this to have the btn b1 function as a 'control' on the 'direction' (forward with 's', backward with shift 's')

However, when I then advance to try this:

[buttons]

0=R0,7,C1001,0

1=U0,7,C1002,0

2=CP(+j0,b1)0,0,K83,8

3=CP(+j0,b1)0,0,K83,8

so that pressing the 'trigger' will only provide the view switch when the joy0 btn1 is held, it functions regardless of the btn1.

What am I doing wrong?

Patrick

[Pete Dowson]

2=CP(+j0,b1)0,0,K83,8

3=CP(+j0,b1)0,0,K83,8

so that pressing the 'trigger' will only provide the view switch when the joy0 btn1 is held, it functions regardless of the btn1.

What am I doing wrong?

What are the "j" and "b" letters doing in there? There's none of that in the documentation I provide. They were just placeholders for the numbers, as x and y might be in an algebraic equation. See the examples in there. Try

2=CP(+0,1)0,0,K83,8

3=CP(+0,1)0,0,K83,8

Regards,

Pete

[ptwaugh]

Actually, this is what is on page 17 of FSUIPC for Advanced Users, and where I got the idea I had to have the letters:

COMPOUND BUTTON CONDITIONS

Facilities are included to allow you to specify actions for one button which are dependent on the state of another button (or more likely, switch). This by using what I call “Compound” button programming—though it could equally be “Conditional” or “Co-operative”. Anyhow, I use the letter C in the definitions, as follows:

n=CP(+j2,b2)j,b, ....

n=CU(+j2,b2)j,b, ...

n=CP(–j2,b2)j,b, ...

n=CU(–j2,b2)j,b, ...

but now I see that they are more like j subscript 2, and I understand.

Works as documented (of course). I knew it was a DEU (defective end user, ie. me).

Now, the only thing I notice is that whatever is assigned the j0,b0 by FS (in my case cutting the mixture to shutdown a chopper) gets processed although I'm intending on only the function assigned.

However, having now understood your excellent manual, I de-assigned the joystick button in FS, and then setup FSUIPC.ini like this:

[buttons]

0=R0,7,C1001,0

1=U0,7,C1002,0

2=CP(+0,1)0,0,K83,8

3=CP(+0,1)0,0,K83,8

4=CP(-0,1)0,0,K112,11

which then does the trick.

After having read all the docs, I can't believe everything this program of yours does, and am even more happy I registered it right away.

I only wish I had read the manual more thoroughly to begin with, hehe.

Thanks, Patrick

[/b]

[Pete Dowson]

Actually, this is what is on page 17 of FSUIPC for Advanced Users, and where I got the idea I had to have the letters

...

Ah, yes, but of course it doesn't stop there. It goes on to explain what "j2" and "b2" stand for (and the "j" and "b" also for that matter), and provides examples further on. But I see you got that now :)

After having read all the docs, I can't believe everything this program of yours does, and am even more happy I registered it right away.

Okay. I'm pleased. Thank you.

Regards,

Pete