Ver 1.4 All Over Again.

falcon409

falcon409

Moderator
Staff member
Anyone who remembers the problems I had last year when I tried version 1.4 will remember that despite being on two different HDD, P3D trashed my FSX setup. . .basically rewrote my scenery.cfg file and dumped all my addon scenery from the library among other problems I had. It's baaaack!

I was going to try to fly in the RTW this year and so was hoping to use P3D. So far it looks like that isn't allowed due to the lack of a weather engine which the irritating little program called "Duenna" requires. So I decided to fire up FSX, which I haven't used since installing P3D Ver2. What I found was that my aircraft selections were back to the default, the tweaks made by the last run I did with NVidiaInspector were gone and my scenery library had been wiped out.

So I went to the FSX folder that houses the fsx.cfg file and took a look. What I found was the P3D.cfg file as well as the FSX.cfg file. . .so I deleted the P3D.cfg file, left the folder open and fired up P3D. . .sure enough, when it started to load, it generated a new P3D.cfg file. I also looked in the P3D folder and found the same instance of an FSX.cfg file in there. . .delete it, fire up FSX and low and behold, it generates a new FSX.cfg file. So just like a year or more ago, when I said the two are talking back and forth to each other and no one else was having this problem. . . .yea, it does happen. If it weren't for the fact that P3D isn't allowed for the RTW currently, I'd uninstall FSX completely and be done with the problem.

Any suggestions?
 
"Something else" is in your system and causing your problem(s). I don't use any migration tools or other such utility programs at all.

Both FSX/A and P3Dv2 remain isolated to their respective folders, as do the scenery.cfg files.

L:\Users\Bill\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.CFG
L:\Users\Bill\AppData\Roaming\Microsoft\FSX\fsx.CFG

I've read elsewhere that the Estonia Migration Tool can and has caused such problems as you've described.
 
Which is what I've been using. . .so it's gone as of this instant. I had also noticed that deleting the FSX.cfg file in Prepar3D also deletes it in the FSX folder. Thanks for the information.

NOTE: The one saving grace to all this is that the Migration Tool saved the original folders for backups, so deleting the current folders and renaming the originals brought things back to normal. I'll stick with manually moving aircraft and scenery for now.
 
Last edited:
I was going to say, the migration tool would probably be something that might cause this to happen.

Sorry Ed.

Do you have backups of these files? I thought you were the one that started keeping backups of your various configs for each simulator.
 
I've used the Migration tool myself. I don't have FSX installed, but I'm wondering if you disable virtual FSX via the tool prior, if that would solve the problem of nuking the config and scenery files?
 
I had FSX, P3D 1.4 and 2.0 all running once with their separate folders and separate scenery, all separate from each other. No problems at all. Since then the only sim I now have running is P3D 2.0. I've learnt, keep it all separate and these migration tools.... well, I stay away from them and wait for proper installers to my favorite addons to materialize.
May sound neglecting but it saves me from boring and tedious fiddeling.

Best regards
Dag
 
You must log in or register to reply here.
Back
Top