FSLabs FS2Crew config not saving

[wattie60 0]

Hello,

I've got that problem on the FSLabs version of FS2Crew (version 2.1).

All the settings I change in the config menu (setup, callouts, misc settings) are back to default every time I restart the simulator (I'm using P3D v4.5).

Any idea of what to do to solve this problem.

Thanks in advance.

[wattie60 0]

Edit : sorry wront forum section. Please move it to FS2CREW: FLIGHT SIM LABS AIRBUS if needed. Thanks

[byork 2,260]

The settings are saved to our config file in the AppData folder.

Is P3D shutting down cleanly for you?

If the sim doesn't shut down cleanly, that can cause settings not to save.

Also, if, for whatever reason, your AppData folder doesn't have write permissions (it generally should) that could block writing to our file.

But generally problems like this are associated with P3D not shutting down cleanly on exit.  That could be do to any number of reasons, usually another 3rd party app that doesn't exit properly.

 

 

[wattie60 0]

Thank you byork for your reply.

I have had a look at windows logs and indeed, P3D does not shut down cleanly because of a .dll file 😕

That is probably the reason.

I have also checked the 2 .ini files in C:\Users\"username"\AppData\Roaming\FS2Crew2010\Versions\AirbusLabs\SavedData

Are they the config files you talked about ?

If yes, is there a way to understand what is the meaning of all "RESERVEXX" (XX being a number) and change the options I need to by changing their value ?

It would probably be an hard and unusual way to do but I only have to this once. I don't to make changes often.

Thanks in advance for future answers.

Gregory

[byork 2,260]

Hi Greg,

That would explain the issue if P3D is not shutting down cleanly for you.

Yes, those are the files we save your options in.

Reserved is just reserved.  It has no meaning beyond that.

You would only need to edit the file once.

But you should try to figure out what's causing P3D not to shutdown cleanly.

Look at "Event Viewer" it may be of help.

 

[wattie60 0]

Each numbers means a function in the FS2Crew MCDU config ?

[byork 2,260]

1 hour ago, wattie60 said:

Each numbers means a function in the FS2Crew MCDU config ?

Not sure I follow...

[wattie60 0]

I mean : in the 2 .ini files, does each line which consists of "RESERVED XX = 0 or 1" means one of the setting in the MCDU config section ?

I did a few test and when I randomly changed a value from 0 to 1, it changed an option from "no" to "yes"

Thanks in advance for the help.

Gregory

[byork 2,260]

I'd have took at the code to refresh my memory how I handled the Config file with the reserved names... but you may need to experiment.

Seriously, though, I would focus on solving your exit problem.

If you solve that, you don't need to worry about meddling with config files, etc.

That'd be way easier.

 

[wattie60 0]

Good news, I don't have crash now and the settings saved perfectly.

I deleted the Lockheed Martin folders located in programdata, appdata\roaming and appdata\local

So that removed all tracks of any add-ons, settings, controls...

I activated only FSLabs and FS2crew, and no crash.

I will now activate my add-ons one by one until I find which one caused the crash

If it can help someone in the future, the crash was ucrtbase.dll crash with exception code 0xc0000409

Thanks for all your help, you spotted the right thing on your very first message. You guys are skilled.

Have a nice day/night

[byork 2,260]

Glad you got it sorted!