INI file backup problem, Fsuipc

[AleItalia]

Hi guys, I made a backup of the INI file, of the Fsuipc, where I have all the settings, in the previous PC with windows 10 and MSFS 2020, I bought the new PC, with windows 11 and always MSFS 2020, I installed the FSUIPC, I inserted the INI file of the backup, only it does not work, in the left, the name of the plane appears with the profile, only that the settings have all disappeared, is this normal?

 

 Alessandro

[John Dowson]

If you have changed your PC, the GUIDs of your controllers will have changed (assuming that you are using the same controllers) and your FSUIPC7.ini file will need updating to use the new GUIDs otherwise your controllers will be recognised as new devices (as they have new GUIDs). If you can attach your FSUIPC7.ini and an FSUIPC7.log file I can take a look and do this for you.

John

[AleItalia]

Ok thanks, I attach ini files, the controllers are always the same.

 

  Alessandro

FSUIPC7.ini

[John Dowson]

I need to see an FSUIPC7.log file as well, as I said...
However, looking at your ini, there are no missing devices. Did you also copy across your FSUIPC7.key file or re-register?
If you are using an unregistered version, your controllers (i.e. the [JoyNames] section of your ini) will not be re-written and no assignments will be available.
So, first check that you are actually using a registered version, and then show me both your FSUIPC7.ini file and a FSUIPC7.log files.

Note that you are also using an old and unsupported version of FSUIPC7 - 7.3.12. The latest and only supported version is 7.3.14 - please update.

John

[AleItalia]

Initially, I copied, the INI file, only realizing that it didn't work, I uninstalled Fsuipc and reinstalled, yes it is registered, as far as the log file is concerned. I can send it later, because I had to bring the PC to assistance for a technical problem, where I just bought it, I update you.

 

   Alessandro

[John Dowson]

Then how did you provide the FSUIPC7.ini file? I need to see that from your new PC, not the old one.
The old one will just have the GUIDs from your old PC. I need to see both of these files from your new PC, and once updated by running FSUIPC7 on the new PC.
Ince you have those it is a simple change - you just need to replace/update the GUIDs for the letter assignments in the [JoyNames] section, so, for example:

Quote

[JoyNames]
A=Flight Yoke System
A.GUID={E74A8930-E0EF-11EC-8003-444553540000}
...

you would replace that GUID (which is from your old PC) with the new/updated one from your new PC. This will be listed (in the same section) with a joyId or number - just use the number where the name matches and update the letter GUID to match the one listed with the number, so this one:

Quote

0=Flight Yoke System
0.GUID={E74A8930-E0EF-11EC-8003-444553540000}
 

 Of course, the GUID there is the same (as from the same PC), but it will be different on your new one.

John

[AleItalia]

The Ini file, I made a backup on an external hard drive, the pc is in service, the external hard drive is with me, I did not know that the log file was also needed, otherwise I would have made the backup and I would have sent you too , so I have to wait for the new pc to be returned to me, I hope in a few hours.
 

Alessandro 

[John Dowson]

The log file is just for confirmation of joystick ids acquired, and there corresponding GUIDs. However, any new devices/GUIDs should also be in the updated FSUIPC7.ini. The ini you posted only shows the original GUIDs - so either they haven't changed or that ini has not been re-written by the new PC. As it is from a backup, I suspect the latter...
Anyway, show me both files from the new PC, and after you have updated FSUIPC to the latest (and only supported) version, and ran FSUIPC7 once and then exit - no need to run MSFS.

John

[AleItalia]

Hi John, I'm attaching the ini file, and I'm also attaching a screenshot, because I can't figure out which is the.log file?

 

 Alessandro

FSUIPC7.ini

[John Dowson]

You cannot see the log file as you have windows explorer set  to hide the extension of known file types. Change your Windows Explorer options to see the extensions correctly - see the Addendum Identifying Files in Windows Explorer in the Installing and Registering FSUIPC document if you require further details.

Note also that you only have assignments in FSUIPC for one aircraft - the Fenix A320, so you will have no assignments with any other aircraft. Also, the name/title of the aircraft loaded must contain the string FenixA320 for your assignments to be loaded. Your controllers are recognised ok, so looks like the GUIDs haven't changed, and so I suspect your issue is that you just don't have any asignments defined for the aircraft that you are using. Again, the FSUIPC7.log file would tell us this...

John

[AleItalia]

Hi John, I am attaching the Fsuipc.log file, what I want to understand, will there be the possibility of inserting the backup ini file of the previous pc, so as not to have to reset all the planes?

 

 Alessandro

FSUIPC7.log

[John Dowson]

14 minutes ago, AleItalia said:

what I want to understand, will there be the possibility of inserting the backup ini file of the previous pc, so as not to have to reset all the planes?

Yes of course you can...and that is what I thought you have already done. You said that you have done this but your settings no longer work.
The GUIDs in the log you attached match those in your ini, so really everything should be working ok. I do not understand what your problem actually is...

The log file shows one issue:

Quote

   946422  [ERROR]: Error setting Client Data Calculator Code: '0 (>L:S_OH_INT_LT_DOME)'

This is from this assignment:
    6=PB,135,CPFNX320_LIGHT_DOME_OFF,0     -{Preset Control}-
That failed as you tried to send this (i.e. pressed button 135 on your X-56 Rhino Throttle) before everything (e.g. WASM/WAPI) was ready. You need to wait for a few seconds after the aircraft is loaded and ready-to-fly before trying to control.

I am getting confused, as well as wasting time, on this thread/issue. Do you actually have any problems, and if so can you please explain clearly what they are. Also, attach a log file with appropriate logging activated for your issue. So, if you have a button assignment that is not working, activate logging for Buttons & Keys and Events, generate a log file showing the problem (i.e. button pressed, no event sent) and show me that, together with your FSUIPC7.ini file. If the issue is with an axis assignment, activate logging for Axis Controls (as well as Events) and generate a log file showing that issue. Always attach both your FSUIPC7.ini and FSUIPC7.log files from the same session.

[AleItalia]

When I insert the Fsuipc.ini backup with the settings of the previous pc, in the new pc, it doesn't load the settings, in fact if I open the fsuipc window in the buttons section, and press a button on the plane, nothing appears

 

  Alessandro

[John Dowson]

1 hour ago, AleItalia said:

When I insert the Fsuipc.ini backup with the settings of the previous pc, in the new pc, it doesn't load the settings,

How do you know this?

1 hour ago, AleItalia said:

In fact if I open the fsuipc window in the buttons section, and press a button on the plane, nothing appears

Well, as you have no general button assignments (i.e. for all aircraft), nothing will show in the button assignment window unless you have the Fenix loaded AND you check the Profile specific? checkbox. Button assignments (as well as key assignments) are inherited (unless overwritten) and you always have the possibility of adding a button or key assignments to the general section or the profile specific section. You need to manually check/uncheck that checkbox to switch between the two. Axes assignments work differently - if the aircraft is in a profile, the profile specific will be checked and inoperative (i.e. you cannot uncheck it),

If you still think you have a problem, show me the files as advised.

John