Button Programming

[hm]

Hi Pete,

Welcome back; hope you enjoyed your holydays.

I have some questions regardingbutton programming: first of all. How do I specify that a button programming section is valid for all paints because something strange is happening: for some airplanes I have to specify them, for other I don't have to do it.

Next, I have to repeat the whole programming for the planes that I have defined a section. Would it not possible that in the future a section could be defined as being common to all planes, and that the sections devoted to certain planes could contain additions, modifications or deletions of some "common" rules:

Something like this:

[buttons.Common]

0=CP......

1=CR......

2=CP......

.

.

.

29=CP....

[buttons.CS727 *] valid for all paints

2=CP...... modification of rule 2

3= deletion of rule 3

30=CR..... addition of rules

31=CR.....

[buttons.Mig-21 paint1] only valid for Mig-21 with paint 1

30=CR....

31=CR....

etc.

I know, I am a nuisance...

Hugo

[Pete Dowson]

I have some questions regardingbutton programming: first of all. How do I specify that a button programming section is valid for all paints because something strange is happening: for some airplanes I have to specify them, for other I don't have to do it.

If a button is programmed for a specific aircraft, it is programmed for that aircraft and this overrides any general programming for that button. If you don't program for specific aircraft then the programming applies to all. It is very very simple. Look in your FSUIPC.INI file. The [buttons] secion are the general ones and apply to all aircraft UNLESS overridden by something in the [buttons.aircraft] section for the current aircraft.

Also you can't program a button PRESS and RELEASE separately in different sections -- obviously that would be chaotic.

Next, I have to repeat the whole programming for the planes that I have defined a section. Would it not possible that in the future a section could be defined as being common to all planes, and that the sections devoted to certain planes could contain additions, modifications or deletions

Well, apart from "deletions" that is EXACTLY how it works, and how I thought I had documented it. You did refer to the documentation, didn't you?

I don't see any point in providing local deletions. If you don't want to use a button don't use it, or assign it to something completely useless or innocuous.

Your "[buttons.Common]" is the "[buttons] section already there.

I don't want to get into this: "[buttons.CS727 *] valid for all paints", That's horrible. Why on Earth would you want your controls to be different just because the colour outside is different?

If you want to have hundreds of planes with minor variations just cut-and-paste the sections in FSUIPC.INI. Isn't that easy enough? I don't want to make the User Interface any more complex than it already is. Sorry.

HmmmI knew it was a mistake going this far .. :o

Regards,

Pete

[hm]

Hi,

Maybe I am an irritating person, but I didn't need to ask this questions if it was documented! But it isn't !!! Not in the "FSUIPC Users Manual" nor in the "FSUIPC for Advanced Users" manual.

hm

[Pete Dowson]

Maybe I am an irritating person

Are you irriatating? Not here you haven't been! :)

but I didn't need to ask this questions if it was documented! But it isn't !!! Not in the "FSUIPC Users Manual" nor in the "FSUIPC for Advanced Users" manual.

What is this then?

"The actions can be programmed differently for different aircraft. Just check the box “aircraft specific” and then everything you program will operate for the currently loaded aircraft only. Anything programmed without that checkbox selected will also be available, unless overridden by an aircraft-specific assignment." (User Guide).

and:

"The button programming is saved in sections in the INI file. For globally operative buttons this is called [buttons]. For aircraft-specific buttons it is [buttons.]." (Advanced User Guide).

Maybe you are looking at older editions? The documentation is updated for each release in the ZIP.

Regards,

Pete

[hm]

Hi Pete,

Well I did some test and "programmed" a button via the FSUIPC interface in FS 9. This is the result: FSUIPC creates for some airplanes button programming sections that are only valid for a certain paint.

[buttons.CS F-104 Starfighter]

0=P0,4,C65668,0

[buttons.CS Boeing 727-100]

0=P0,4,C65668,0

[buttons.CS Boeing 727-200 paint4]

0=P0,4,C65668,0

[buttons.Utva 75 Astra]

0=P0,4,C65668,0

[buttons.SIAI-Marchetti SF.260 Belgian Camo]

0=P0,4,C65667,0

[buttons.CS Yak-3 Paint1]

0=P0,4,C65666,0

[buttons.MiG-21UM]

0=P0,4,C66039,0

hm

[Pete Dowson]

Well I did some test and "programmed" a button via the FSUIPC interface in FS 9. This is the result: FSUIPC creates for some airplanes button programming sections that are only valid for a certain paint.

Yes, of course. Exactly right. Well done. If you program buttons in non-aircraft specific mode they will appear in the [buttons] section. no need for a [buttons.Common], as you suggested. It's already there and has been for a long time! :wink:

Your term "paint" is my term "aircraft name". It is the only way I know how to distinguish different aircraft. Why do you use the term "paint" instead? Each aircraft listed with a different name is a different aircraft.

Regards,

Pete