Profile recognition

[airernie]

I'm trying to determine if this is normal operation, or not.

 

I am using "UseProfiles=Files" and have successfully created and used several profiles. 

 

When I am in the 'Options and Settings' dialog and select the 'Axis Assignment' tab, the title bar immediately displays  the profile for the aircraft I am in. (example "FSUIPC Options and Settings - iFly_737") and selects the 'Profile Specific' checkbox..

 

However, if I am in the 'Buttons' tab and press a button, no profile is displayed and the 'Profile Specific' checkbox is blank. 

 

I have to click on the 'Profile Specific'  checkbox to select the profile, even though I have previously assigned the selected button to the current aircraft.

 

This makes me wonder if perhaps the same thing is occurring because sometimes clicking on an assigned button doesn't seem to work.

 

How can I validate, during flight that FSUIPC4 is actually using the correct profile when I click on a button?

 

Thanks,

Ernie

 

 

[Pete Dowson]

When I am in the 'Options and Settings' dialog and select the 'Axis Assignment' tab, the title bar immediately displays  the profile for the aircraft I am in. (example "FSUIPC Options and Settings - iFly_737") and selects the 'Profile Specific' checkbox..

 

However, if I am in the 'Buttons' tab and press a button, no profile is displayed and the 'Profile Specific' checkbox is blank. 

 

I have to click on the 'Profile Specific'  checkbox to select the profile, even though I have previously assigned the selected button to the current aircraft.

 

This makes me wonder if perhaps the same thing is occurring because sometimes clicking on an assigned button doesn't seem to work.

 

It is perfectly correct behaviour. 

 

Button and Key assignments can be both Generic and Profile-specific. All that happens is that the Profile-specific assignment overrides any generic assignments for the same button or keypress. This allows the majority of common controls (Gear, Lights, etc etc) to be made just once and apply to all aircraft whilst those switches and options specific to the aircraft can vary.

 

Axes and Joystick Calibrations are either generic or profile specific. They cannot be mixed, because axes are effectivey active all the time, whereas buttons and eyes only do something when you press them.

 

This is written up in the documentation somewhere.

 

 

How can I validate, during flight that FSUIPC4 is actually using the correct profile when I click on a button?

 

I think if you log buttons/switches (an option in FSUIPC's Logging tab) it will show in the log. But of course you can simply click the button and see.

 

Pete

[airernie]

Thanks, that helps..