4 hours ago, DJ_Chaos said:

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

Sorry for my english.

best regards

Jörg

No, you don't need to re-activate after every update.

But should you ever have a license problem, just send us a support ticket via FS2Crew.com so we can sort it for you.

Cheers,

Bryan and Manuel,

Just for your information, also in version 1.1.7 the settings file gets overwritten.

Cheers,

6 hours ago, hvw said:

Bryan and Manuel,

Just for your information, also in version 1.1.7 the settings file gets overwritten.

Cheers,

Which specific setting are you trying to save?

 

Did you close the settings panel via the X after changing the option on the Settings panel?

After doing that, please open the XML file below to visually confirm the change was in fact saved to the XML file.
 

The XML saved settings file is located here:

 

C:\Users\***your user name****\AppData\Roaming\FS2Crew A32NX Project\FS2Crew A32NX Project.xml

 

The installer should not be over-writing that XML file (assuming you're using 1.1.7).


You can also test this way (note: V1.1.7 must be running, and not an earlier version).

 

We think we know what happened....

There was an issue in 1.1.6 and I think the problem happened because you were still at 1.1.6 when you saved your old setting.

 

Please do this:

1. Change setting in FS2Crew.

2. Exit Sim.

3. Go to this folder:

C:\Program Files (x86)\FS2Crew FBW A32NX

Delete the FS2Crew FBW A32NX Project .EXE file located in Program Files X86,

4. Re-run the Product Manager.  Since the FS2Crew FBW EXE is gone, it will allow you to re-install FS2Crew FBW.

 

Your old setting should still be there.

 

 

Cheers,

 

 

Edited December 18, 20214 yr by byork

12 minutes ago, byork said:

Which specific setting are you trying to save?

 

Did you close the settings panel via the X after changing the option on the Settings panel?

After doing that, please open the XML file below to visually confirm the change was in fact saved to the XML file.
 

The XML saved settings file is located here:

 

C:\Users\***your user name****\AppData\Roaming\FS2Crew A32NX Project\FS2Crew A32NX Project.xml

 

The installer should not be over-writing that XML file (assuming you're using 1.1.7).

 

Cheers,

 

 

Trying to save all settings, i.e. the ones in the \FS2Crew A32NX Project\FS2Crew A32NX Project.xml file.

The installer should not overwrite this file, but it sure does overwrite it. For the time being I will just overwrite the latest installed file, installed by the installer, with my backup file. And yes, I am using version 1.1.7 as stated in my previous note.

7 minutes ago, hvw said:

Trying to save all settings, i.e. the ones in the \FS2Crew A32NX Project\FS2Crew A32NX Project.xml file.

The installer should not overwrite this file, but it sure does overwrite it. For the time being I will just overwrite the latest installed file, installed by the installer, with my backup file. And yes, I am using version 1.1.7 as stated in my previous note.

I'll send you a message and you can show me via a remote desktop.  But I still think the problem is you were going from 1.6 to 1.7.  1.6 had an issue.

Edited December 18, 20214 yr by byork

2 minutes ago, byork said:

I'll send you a message and you can show me via a remote desktop.  But I still think the problem is you were going from 1.6 to 1.7.  1.6 had an issue.

No, I am not comfortable with a remote desktop session. And why should it be a problem going from one version to another, in this case 1.6 to 1.7? If this would be a problem, any update from a version to a newer one could be problematic.

4 minutes ago, hvw said:

No, I am not comfortable with a remote desktop session. And why should it be a problem going from one version to another, in this case 1.6 to 1.7? If this would be a problem, any update from a version to a newer one could be problematic.

Because there was a problem in the 1.6 uninstaller.

When the Product Manager uninstalled 1.6 by triggering the 1.6 uninstaller, it would have deleted your XML saved settings file.  It shouldn't have done that, but it would have.

So when you transitioned from 1.6 to 1.7, the settings file would not appear to have kept your old settings.

However, 1.7 to 1.8 (whenever we release 1.8) should not have this problem.

 

 

Edited December 18, 20214 yr by byork

When I transferred from 1.6 to 1.7 the settings file at that time was correct as it was an used backup file. I deleted the file installed by 1.6 and used my backup instead.
I will just await what the future will bring and continue using the backup file, I am quite happy doing so rather than every time a new version has been released filling out the "questioaire" again 🙂

 

 

11 minutes ago, hvw said:

When I transferred from 1.6 to 1.7 the settings file at that time was correct as it was an used backup file. I deleted the file installed by 1.6 and used my backup instead.
I will just await what the future will bring and continue using the backup file, I am quite happy doing so rather than every time a new version has been released filling out the "questioaire" again 🙂

 

 

Hey Hans, no worries, the problem was that the 1.1.6 setup was deleting the current XML file, and actually the Products Manager calls to uninstall the current version , that by the time, was 1.1.6, then it would also delete the existing XML and when the 1.1.7 was downloaded by the Products manager, it sees there is no XML (because the uninstaller in 1.1.6 deleted previously), it would then paste a default XML, that's the behaivor on all setups equal or below 1.1.6. We noticed that and fixed on 1.1.7 setup, so basicly when products' manager updates to the next version (from 1.1.7 to next), it must be kept intact. I know you said you will paste your backup XML in place on every update, but before doing so, could you just check the XML's content to cross check it didn't replaced with the default?, this way we can confirm that infact it's fixed. I physically tested the 1.1.7 setup yesterday and it keeps the XML once you uninstall 1.1.7 from your system.

Cheers,

Manuel

Hi Manual,

Thank you very much for your explanation. What you wrote makes sense. But I am sorry, I have already spent way too much time in trying to find ways around, let's call it, undocumented features. I just don't want to spend anymore time in doing so. I am an end-user who paid for this product and was unilaterally assigned beta tester. I never volunteered to be one, but just wanted to give FS2Crew my $0.02 worth in trying to help out. 

Why doesn't FS2Crew have a pool of dedicated beta testers that do test a new version before it is ready to be released, rather than have end-users act as beta testers? Oh well, it is as it is 🙂

Have a nice weekend,