[Axes.xx] vs [Axes] section in .ini file

[kaha]

If I change an axis assignment which is not profile specific it gets updated in the [Axis] section. I then have to update all [Axes.xx] sections with manually in the .ini file? Or is there another way to do it from the GUI?

Karl

[John Dowson]

Yes - to change an axis assignment (in the GUI) for a profile, you need to load an aircraft that uses that profile first.

[kaha]

2 minutes ago, John Dowson said:

Yes - to change an axis assignment (in the GUI) for a profile, you need to load an aircraft that uses that profile first.

Yes, but the other way, if I want to change an axis assignment that is not profile specific, I have to load an aircraft that does not have any profile specific axis assingments.

Then I change the axis assignment and it goes to the [AXIS] section.

 

Now, all aircraft that do have profile specific axis assignments will not see the change, I have to manually update all [Axis.xx] sections in the .ini file.

[John Dowson]

1 minute ago, kaha said:

if I want to change an axis assignment that is not profile specific, I have to load an aircraft that does not have any profile specific axis assingments.

Then I change the axis assignment and it goes to the [AXIS] section.

Yes, of course....

1 minute ago, kaha said:

Now, all aircraft that do have profile specific axis assignments will not see the change

Of course not, as they are using profile-specific axis assignments. This is the point of a profile-specific assignment section...

The whole idea behind profiles is that the assignments are different for different aircraft. It makes no sense at all to update/change a profile-specific axis section when updating the general axis section, as this would override the specific assignments for that profile.

If you want to use the general axis assignments for an aircraft, then don't add a profile-specific axis section.

I think you are missing the point of what a profile is....

[kaha]

I understand that. but please let me explain. It works differently for axes and buttons.

This is part of my .ini file:

[Axes]
PollInterval=10
RangeRepeatRate=10
0=BS,256,F,66162,66163,66164,66165	-{ TO SIM: COWLFLAP1_SET, COWLFLAP2_SET, COWLFLAP3_SET, COWLFLAP4_SET }-
1=CZ,256,F,x020025F2,0,0,0	-{ FSUIPC: offset word set, offset 25F2 }-

[Buttons]
PollInterval=25
ButtonRepeat=20,10
18=P72,19,C66080,0 	-{GEAR_DOWN}-
19=P72,18,C66079,0 	-{GEAR_UP}-

I now make profile specific assignments for button and an axis for a specific aircraft. After that I have:

[Axes]
PollInterval=10
RangeRepeatRate=10
0=BS,256,F,66162,66163,66164,66165	-{ TO SIM: COWLFLAP1_SET, COWLFLAP2_SET, COWLFLAP3_SET, COWLFLAP4_SET }-
1=CZ,256,F,x020025F2,0,0,0	-{ FSUIPC: offset word set, offset 25F2 }-

[Buttons]
PollInterval=25
ButtonRepeat=20,10
18=P72,19,C66080,0 	-{GEAR_DOWN}-
19=P72,18,C66079,0 	-{GEAR_UP}-

[Axes.Beaver]
RangeRepeatRate=10
0=BS,256,F,66162,66163,66164,66165	-{ TO SIM: COWLFLAP1_SET, COWLFLAP2_SET, COWLFLAP3_SET, COWLFLAP4_SET }-
1=CZ,256,F,x020025F2,0,0,0	-{ FSUIPC: offset word set, offset 25F2 }-
2=KR,R0,F,67011,0,0,0	-{ TO SIM: ANTI_ICE_GRADUAL_SET }-

[Buttons.Beaver]
1=PC,11,CL30:R,1 	-{Lua Beav_TankSelect}-
7=PC,15,CL31:R,0 	-{Lua Beav_FuelPump}-

All the default axis assignments go into the Beaver axis section (which I don't want), but none of the default button assignments go to the Beaver button assignments.

Now I change the default axis assignment from offset 25F2 to 25F4 and the button for gear down also changes from 19 to 13:

[Axes]
PollInterval=10
RangeRepeatRate=10
0=BS,256,F,66162,66163,66164,66165	-{ TO SIM: COWLFLAP1_SET, COWLFLAP2_SET, COWLFLAP3_SET, COWLFLAP4_SET }-
1=CZ,256,F,x020025F2,0,0,0	-{ FSUIPC: offset word set, offset 25F4 }-

[Buttons]
PollInterval=25
ButtonRepeat=20,10
18=P72,13,C66080,0 	-{GEAR_DOWN}-
19=P72,18,C66079,0 	-{GEAR_UP}-

[Axes.Beaver]
RangeRepeatRate=10
0=BS,256,F,66162,66163,66164,66165	-{ TO SIM: COWLFLAP1_SET, COWLFLAP2_SET, COWLFLAP3_SET, COWLFLAP4_SET }-
1=CZ,256,F,x020025F2,0,0,0	-{ FSUIPC: offset word set, offset 25F2 }-
2=KR,R0,F,67011,0,0,0	-{ TO SIM: ANTI_ICE_GRADUAL_SET }-

[Buttons.Beaver]
1=PC,11,CL30:R,1 	-{Lua Beav_TankSelect}-
7=PC,15,CL31:R,0 	-{Lua Beav_FuelPump}-

Now gear down still works for all aircraft. If I would want to have a different button for a specific aircraft I would assign it profile specific.

The axis that now goes to offset 25F4 only works for aircraft that do not have profile specific axes assignments.

 

I think the way it works for buttons is the better one.

[kaha]

For buttons I can always add non profile specific entries to the [Buttons] section and all aircraft will utilize it.

If I do that for an axis in the [Axes] section only aircraft that have no profile specific section will know about it.

[John Dowson]

36 minutes ago, kaha said:

It works differently for axes and buttons.

Yes, the general button section is inherited in profiles, but not for axes. This is explained in the user guide. It works this way for technical reasons and cannot be changed. It has been like this for 15+ years.

If you want to use the general axis assignments, delete the profile specific sections. When you create a profile-specific axis section, you are asked if you would like to import the general axis assignments - this is done only when you initially create the profile specific axis section. After that, it is up to you to update this section if needed when you change the general axis section.

[kaha]

Ok, thank you.