FSUIPC Setting Won't Save

[tcm1707]

I keep on assigning Axes and Buttons to a standard profile for the PMDG 737, but every time I load the aircraft again the settings haven't saved and I have to reassign everything again. I've looked in the manual but can't find what it is I need to do to get it to save. Can anyone point me in the right direction please?

[John Dowson]

This can only occur (sometimes) if you have installed FSUIPC7 in a windows-protected folder, such as under Documents or Program Files. If that is the case, re-install into a non windows-protected folder.

However, for most reports of this issue, it is either due to:
  1. A different variant/livery of an aircraft being loaded that is not covered by the name in the existing profile. If this is the case, you can add the new variant to the same profile, or better to edit your FSUIPC7.ini to give a substring to the aircraft names in the [Profile.xxx] section so that they match all variants (and no others).
  2. A misunderstanding of how the button assignments work with profiles. With axis assignments, you will only see the axes assigned in the current profile, and the profile name will appear in the window title bar. For button and key assignments, this is not the case. To see your profile button/key assignments, you need to manually check the 'profile specific' check-box before pressing the button/key, or only the general assignments will show. This is because it is possible to add general button/key assignments to an aircraft that uses a profile, but not for axes assignments.

Any further issues, please show me/attach your FSUIPC7.ini and FSUIPC7.log files.

John

[tcm1707]

Thanks John. I'm not sure what I did to fix it but it seems to be working now. I think the liveries hadn't been added to the FSUIPC.ini file. Cheers.

[John Dowson]

13 hours ago, tcm1707 said:

I think the liveries hadn't been added to the FSUIPC.ini file.

As I said, it is better to edit the [Profile.xxx] to specify a substring that will match all variants/liveries, rather than adding the aircraft to a profile each time you use a new livery.

John

[tcm1707]

What would you suggest for the substring?

[tcm1707]

I'm still having issues. When I load a new livery, I open the FSUIPC window to select the PMDG 737 profile I created. But it seems to just wipe the previously saved settings I had created for another livery and I have to start from scratch. 

FSUIPC7.log FSUIPC7.ini

[John Dowson]

First, you are using an old and unsupported version of FSUIPC7 (7.3.12) - only the latest version is supported, which is version 7.3.16. Please update.

1 hour ago, tcm1707 said:

But it seems to just wipe the previously saved settings I had created for another livery and I have to start from scratch. 

What is it 'wiping'? I cannot see how this can occur, but if you think this is happening then I need to see your ini both before this wipe and after. together with the log from the session where this occurred. So, make a backup/copy of your ini file before you make any changes. Your current ini only shows one key assignment and 3 button assignments, all profile specific. Note that as they are profile specific, you need to check the profile specific checkbox to see these assignments.

1 hour ago, tcm1707 said:

What would you suggest for the substring?

Change your [Profile.PMDG 737] section to the following:

Quote

[Profile.PMDG 737]
1=PMDG 737-800
2=Airbus A310-300

John

[tcm1707]

Okay I'll update and change the substring when I get home. 

When I load a new livery for the first time I go into FSUIPC and under the Axis menu I click profile specific and select the PMDG 737 preset. This seems to make the unassigned Axes on the new livery save to the PMDG preset. And therefore wipes the settings from all the other liveries too. 

[John Dowson]

1 minute ago, tcm1707 said:

This seems to make the unassigned Axes on the new livery save to the PMDG preset. And therefore wipes the settings from all the other liveries too. 

It doesn't...that just adds the aircraft with the new livery to the profile section. As I said, you only have assignments to keys and buttons in the profile. To see these in the buttons and keys windows, you have to then manually check the profile specific checkbox before you press the button/key- this is not checked by default in buttons and keys, only in axes, as it is possible to add general button/key assignments even when using a profile for the loaded aircraft (as general assignments to buttons and keys are inherited, if not overwritten).

This does cause some confusion. I will look into updating so that the buttons/keys will register a profile-specific assignment when a button/key is pressed even if the profile-specific checkbox isn't ticked - and automatically tick the checkbox to show that it is a profile specific assignment.

John