I never do and upgrades work right for me from the beginning.

Cheers, Ed

While I accept that they work for you Ed, they may not work right 100% or work in an optimal manner. For the first time in a while, I deleted and allowed P3D to rebuild my Prepar3D.cfg file and noted there were a few new and/or altered items compared to my previous version (which I saved so I would be able restore all my configuration settings accurately).

 

Now I'm not saying your wrong, but it is possible you're only getting 99.9% of the experience that 3.4.9 has to offer! ;-)

While I accept that they work for you Ed, they may not work right 100% or work in an optimal manner. For the first time in a while, I deleted and allowed P3D to rebuild my Prepar3D.cfg file and noted there were a few new and/or altered items compared to my previous version (which I saved so I would be able restore all my configuration settings accurately).

 

What the P3D Client installer do is to add all necessary entries for the upgraded version to your existing Prepar3D.CFG file, and it will not delete anything (I wonder if it will not delete entries that could cause trouble for the upgraded version, I don't really know) so I still guess it's not necessary to allow Prepar3D to build a totally new file as it would represent to you the loss of pre-existing fixes or additions you've made for the previous version or an extra-time to you for the comparison between the new and the old files.

Cheers, Ed

If I deleted my P3D.cfg file after the update, would I loose my controller settings? I use saitek and have customised my buttons. Would hate to have to set that up again. I understand that I would have to reconfigure P3D settings.

Someone correct me if I'm wrong but IIRC your controls and key assignments are stored separately. You can also export your control settings and then import them.

If I deleted my P3D.cfg file after the update, would I loose my controller settings? I use saitek and have customised my buttons. Would hate to have to set that up again. I understand that I would have to reconfigure P3D settings.

 

You just need to check your calibration and sensitivities, dead zones, etc., from within P3D.

Cheers, Ed

What the P3D Client installer do is to add all necessary entries for the upgraded version to your existing Prepar3D.CFG file, and it will not delete anything (I wonder if it will not delete entries that could cause trouble for the upgraded version, I don't really know) so I still guess it's not necessary to allow Prepar3D to build a totally new file as it would represent to you the loss of pre-existing fixes or additions you've made for the previous version or an extra-time to you for the comparison between the new and the old files.

Cheers, Ed

In that case... deleting the cfg was a complete waste of effort! Live and learn!

You just need to check your calibration and sensitivities, dead zones, etc., from within P3D.

Cheers, Ed

Thanks. So I understand my Saitek axis, button assignments, etc would remain as I have configured them?

Thanks. So I understand my Saitek axis, button assignments, etc would remain as I have configured them?

 

Hi, yes, I think they will.

Cheers, Ed

Thanks. So I understand my Saitek axis, button assignments, etc would remain as I have configured them?

Going from v3.3.5 to v3.4.9 my yoke buttons survived but on other occasions they didn't. Backup "%appdata%\Lockheed Martin\Prepar3D v3\Controls" to save the headache.

Going from v3.3.5 to v3.4.9 my yoke buttons survived but on other occasions they didn't. Backup "%appdata%\Lockheed Martin\Prepar3D v3\Controls" to save the headache.

Thanks. Will do.

Thanks. So I understand my Saitek axis, button assignments, etc would remain as I have configured them?

Mine did.

Mine did.

This was after deleting you P3D.cfg file and allowing it to regenerate?

For what it's worth, after each P3D minor version update, I delete all my files in AppData\Roaming\Lockheed Martin\Prepar3D v3\Controls and let P3D re-create defaults then go thru the tedious process of manual re-assignment.  A little time consuming but ensures no controller issues (I have a lot of controllers).  I do this as a "pre-caution", especially when I know LM work has been done regarding controllers.

 

Cheers, Rob.

This was after deleting you P3D.cfg file and allowing it to regenerate?

Correct.

 

I also deleted Cameras.cfg FWIW because an Oculus cockpit view got added which I was forced to scroll through every time i cycled through views... which supports Rob's approach of clearing out everything,

For what it's worth, after each P3D minor version update, I delete all my files in AppData\Roaming\Lockheed Martin\Prepar3D v3\Controls and let P3D re-create defaults then go thru the tedious process of manual re-assignment.  A little time consuming but ensures no controller issues (I have a lot of controllers).  I do this as a "pre-caution", especially when I know LM work has been done regarding controllers.

 

Cheers, Rob.

Ok...since I only have the Saitek Yoke, throttle quadrant and rudders, this sounds like a good option. Thanks. The reason I'm asking is that I've never deleted my .cfg file and have been updating P3D v3 since initial release. I have read it is worthwhile to delete this file and allow it to regenerate but was unsure of the consequences. Thanks all for the info.