Is there a way to protect settings from being overwritten each time an (auto)update has been performed? Or is there a way to disable automatic updates? 

Thanks.

Updates are not automatic.  

The settings file for FS2Crew FBW A22NX is is here:

 

C:\Users*YOUR USER NAME***\AppData\Roaming\FS2Crew A32NX Project

I suggest just making a manual back of it.

Then restoring the original after updating should you want to keep your settings.

As I mentioned to you before, when people install, we want everything to be original and fresh, and that also means restoring the user settings file.

This is way is the user settings file somehow gets corrupt (it can happen), re-installing will fix it for the user.

 

Edited December 13, 20214 yr by byork

16 minutes ago, byork said:

As I mentioned to you before, when people install, we want everything to be original and fresh, and that also means restoring the user settings file.

This is way is the user settings file somehow gets corrupt (it can happen), re-installing will fix it for the user.

Thanks. I will make a manual backup of the file.

Fs2Crew is the only developer with this strange "policy". It is very uncommon that users should every time an update has been performed reset their settings. Normally settings are saved in a settings.cfg file (or something alike) which won't be affected by any update or upgrade. Only in cases that such a file is getting corrupt, the user will have to re-enter settings. Not every darn time an update was performed.

Have a good one.

6 minutes ago, hvw said:

Thanks. I will make a manual backup of the file.

Fs2Crew is the only developer with this strange "policy". It is very uncommon that users should every time an update has been performed reset their settings. Normally settings are saved in a settings.cfg file (or something alike) which won't be affected by any update or upgrade. Only in cases that such a file is getting corrupt, the user will have to re-enter settings. Not every darn time an update was performed.

Have a good one.

Other developers do this as well.

The PMDG panel.cfg files, and the panel.cfg files for other aircraft, for example, are often restored when you do updates.

We know from 15 years experience making FS addons that sometimes users setting files can get corrupted.  It's possible and it's happened.

Then we spend hours trying to figure out what went wrong for the user.

A fresh reinstall with files restored makes trouble shooting much easier and faster.

45 minutes ago, byork said:

Other developers do this as well.

I have a different opinion about this. (But I only have 35+ years of experience as an ITC system's engineer) 

Guys, We will try to improve this, so every time, you get an update doesn't erase your actual settings. As Bryan said, sometimes the XML file gets corrupted, but, I also understand, we will try to improve this to avoid you to enter all over and over again.

Cheers,

Manuel

Edited December 13, 20214 yr by Manuel82

That would be excellent. Thanks.

We just made some changes to FBW and PBE, so if tests goes fine, your settings should be kept intact on the next update.

Cheers,

Manuel

Hans, you owe Manuel a beer 😉  I would never have thought about the Manuel's code change 😉
 

 

6 hours ago, Manuel82 said:

We just made some changes to FBW and PBE, so if tests goes fine, your settings should be kept intact on the next update.

Cheers,

Manuel

Thanks a lot, Manolo, that is great news.

11 hours ago, hvw said:

Thanks a lot, Manolo, that is great news.

No problem :) 

Cheers,

Manuel

Hi Bryan and Manuel,

Did you implement this already in version 1.1.6? If so, it didn't work, the existing FS2CrewA32NXProjext.xml was overwritten by updating to version 1.1.6 😞 

Hey Hans,

Yes, then something went wrong with the setup, I'm checking what happened and upload a hot fix to the setup.

Cheers,

Manuel

2 minutes ago, Manuel82 said:

Hey Hans,

Yes, then something went wrong with the setup, I'm checking what happened and upload a hot fix to the setup.

Cheers,

Manuel

No problem, Manuel. Take your time. Thanks a lot for looking into this.

And the new activation after every update? I must new activation every time after the update.

Sorry for my english.

best regards

Jörg