Button assignments?

[von]

My FSUIPC ver 3.74 and ver 3.75 do the same thing here.

from the FSUIPC.ini file.

I have three (32 bit) Level-D liveries. I asigned the same yoke buttons for

all three and they work good. The first three beolw.

[buttons.Level D Simulations B767-300ER]

0=P2,6,K68,11

1=P2,7,K87,11

2=P2,1,K80,10

[buttons.Level D Simulations B767-300ER - UPS2]

0=P2,6,K68,11

1=P2,7,K87,11

2=P2,1,K80,10

[buttons.Level D Simulations B767-300ER - Hawaiian Airlines]

0=P2,6,K68,11

1=P2,1,K80,10

2=P2,7,K87,11

[buttons.[DXT3] Level D Simulations B767-300ER -

American_Airlines_N327AA_DXT3]

0=P2,6,K68,11

[buttons.[DXT3] Level D Simulations B767-300ER -

American_Airlines_N327AA_DXT3]

1=P2,7,K87,11

[buttons.[DXT3] Level D Simulations B767-300ER -

American_Airlines_N327AA_DXT3]

2=P2,1,K80,10

I added an American Airlines DXT-3 repaint and assigned the same yoke

buttons.

This does not work.

There are more [ ] in the American and the layout is different between the

32bit repaints (first three) and the DXT-3 repaint.

I cannot figure out to get the button assignments working on the American

repaint.

[Pete Dowson]

I have three (32 bit) Level-D liveries. I asigned the same yoke buttons for all three and they work good.

As described in the FSUIPC documentation (Advanced Users), it would be much easier for you if you just kept the first such section in the INI file and changed the "ShortAircraftNameOk" parameter to "Yes". This would work because all of those aircraft start with "Level D Simulations B767-300ER".

However, this name will NOT work:

[DXT3] Level D Simulations B767-300ER -

American_Airlines_N327AA_DXT3]

for two reasons:

1) The name contains [ ] characters which confuses the section naming in the INI, and

2) The name as shown above contains a more than one line! The Windows INI system cannot handle multiple lines in names.

Or is the latter problem a result of your formatting in this message?

If you want the same buttons for all variants of "Level D Simulations B767-300ER" then just keep the one section with that name, deleting all the others, then set "ShortAircraftNameOK=Substring".

Regards

Pete

[von]

Pete,

Thanks for the reply.

After 4 hours trying my self I gave up and posted.

The above name was all on one line in the ini file. My cut and paste messed it up a bit.

I figured the [ ] brackets could be the cause .. I renamed the repaint "like" the ones that worked but still had problems in the end.

I did search for the solution .. no luck, so grateful for your information.

In the end I will have (hopefully) all DXT-3 repaints and they all share the same naming problem.

I will give you solution a go and also put a stickie on my FSUIPC notes.

Thanks again Pete, really appreciated.

[von]

To Pete:

I changed the FSUIPC ini file to this:

ShortAircraftNameOk=Yes

Only kept one set of button assignments:

[buttons.Level D Simulations B767-300ER]

0=P2,6,K68,11

1=P2,7,K87,11

2=P2,1,K80,10

Level-D aircraft.cfg file:

From this (incorrect one)

title=[DXT3] Level D Simulations B767-300ER - Delta Air Lines (Old Livery)]

To this:

title=Level D Simulations B767-300ER - Delta Air Lines (Old Livery)

Now all five of my Level-D aircraft load with the same FSUIPC (yoke) button assignments.

Great!

I got it going but I do not know if it is the correct way!

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

But when I select "specific aircraft" in FSUIPC to verify all the button assignments, they all come up with the

same name in the FSUIPC title bar:

Level D Simulations B767-300ER

I expected to see:

Level D Simulations B767-300ER - Delta Air Lines (Old Livery)

..............................

So I guess the short name is everything before the second "-" in the line above.

Can there be mutiple occurances of eg.

ShortAircraftNameOk= in the FSUIPC ini file, like for your example for Airbus and Boeing?

Would it be this sequence:

ShortAircraftNameOk=Yes

ShortAircraftNameOk=Airbus

ShortAircraftNameOk=Boeing

Or, is it one occurance of

ShortAircraftNameOk=Yes

or

several lines to specify

ShortAircraftNameOk=Airbus

ShortAircraftNameOk=Boeing

etc.

But you cannot mix them?

Are there any examples of the usages?

[Pete Dowson]

I changed the FSUIPC ini file to this:

ShortAircraftNameOk=Yes

Only kept one set of button assignments:

...

Okay, but:

Level-D aircraft.cfg file:

From this (incorrect one)

title=[DXT3] Level D Simulations B767-300ER - Delta Air Lines (Old Livery)]

To this:

title=Level D Simulations B767-300ER - Delta Air Lines (Old Livery)

as I said you could have left that and simply set the ShortAircraftNameOk to "Substring", so it would have found the name after the [DXT3] part in any case.

But when I select "specific aircraft" in FSUIPC to verify all the button assignments, they all come up with the

same name in the FSUIPC title bar:

Level D Simulations B767-300ER

Of course, because you've told it to accept that short name for all of those.

So I guess the short name is everything before the second "-" in the line above.

No, the short name is whatever you have in the INI file. If the only entry in the INI file shows [buttons.Level D] then you'd match everything starting "Level D" and that's what you would see!

Please do refer to the description of this facility in the documentation.

If you set the ShortAircraftNameOk to "substring", then you could have "767" instead and it would match anything with "767" in the title.

Can there be mutiple occurances of eg.

ShortAircraftNameOk= in the FSUIPC ini file, like for your example for Airbus and Boeing?

No!!! It is either "No", "Yes" or "Substring". That parameter doesn't dictate the part of the name, the name part of the [buttons.] title does! You can have any number of those, with different names. All the "ShortAircraftNameOk" parameter does is tell FSUIPC not to check ALL of the name, only part of it!

PLEASE read the documentation, which explains it! I shouldn't have to repeat it here!

:-(

Pete

[von]

Pete,

Thanks again for your time and the detailed reply.

Now I "know" what "substring" means and how it is used.

I won't go looking into aircraft cfg files ...

Non-programmer here but I really do try hard!