Hi everyone

 

I decided to install P3D v2.2 from a complete re-format of my Hard Disk Drive

 

Everything went well .. no stutters etc etc

 

Anyway .. I spent the next 6 hours installing my addons using the latest updated FS Estonia Migration tool making sure I ran each addon before I installed the next ...

 

Everything was going very well until I came to add an Aerosoft Airport via the migration tool   .....

 

As soon as I ran P3D it crashed with a message saying P3D has stopped working and will close ... it didn't even get to the user interface screen

 

I then uninstalled the Aerosoft product from the control panel (uninstall a program)

 

Started P3D and still it crashed

 

My only option was to do a system restore back to before I added the airport

 

That went well and thank goodness P3D started fine

 

I then went to the scenery library in P3D only to find that all the sceneries etc etc I had loaded were gone  ... Arggghhhhhhhh

 

So I spent all day getting back to where it all went wrong

 

So beware of this  ... or maybe someone else has had this problem and knows the answer 

 

I think the problem lies with the Migration Tool update because it worked fine with Aerosoft products in v2.1 

 

Maybe I should notify them of this

 

Look forward to any comments

 

Cheers

 

Paul

Hi Paul,

 

which airport exactly caused the crash? i installed various aerosoft airports with EMT no problem. Then when i installed Frankfurt update, it caused problems. So had to remove the update and the airport, then just installed frankfurt without the update and it worked fine.

 

Regards,

The Migration tools runs like a charm. I have only P3D v2.2 installed so I set the tool to enable virtual FSX (can't remember if it's the actual name) and forget about it. EVERYTHING installs in the \prepar3d v2 folder.

 

I strongly believe that where the problems arise is when addons need to install their own versions of DirectX or other Windows-based software that conflicts the the sim's version.

 

I always hold my breath when O install an addon that requires this extra stuff - and often enough, Prepar3d will crash, but on the next attempt will open properly. I certainly cannot put the fault P3D..

 

I wish there was a standard for prerequisites for all addons but that is simply dreaming in color.

Hi

 

Yes I am pretty sure you are right that it is not P3D at fault

 

I installed Aerosoft airports into v2.1 with the older EMT and they went in fine .. so I am sure it is the update for EMT at fault

 

Well ... I added Nice and then Balearics but stupidly I didn't try Nice Airport before adding Balearics Airports so I am not sure which was the culprit  but my guess P3D would of crashed with either 

I decided not to use EMT with v2.2. Had bought it for 1.4, and used it for a while, but with v2.2 I will install only native stuff or anything that accepts at most a fake FSX.exe and the registry entries of FSX tweaked by that well known FSX registry fixer available from a few sources...

So do you think I ought to try installing one of the Aerosoft airports without EMT into P3D v2.2?

 

I could just point it to where P3D is installed

 

Trouble is I am so worried that I might screw it all up again ... Decisions decisions 

So do you think I ought to try installing one of the Aerosoft airports without EMT into P3D v2.2?

 

 

 

I could just point it to where P3D is installed

 

 

 

Trouble is I am so worried that I might screw it all up again ... Decisions decisions

 

Make an image of your disk - that's what I always do before trying something that could drive me into bigger problems.... Not only a restore point! An Image!

I use Acronis True Image, but threre are hundreds of apps available.

 

I didn't install any of the only two sceneries I have, from Aerosoft, in P3Dv2.2, but I did install A2A's C172, which expects an FSX install.

 

1) I created a fake FSX.exe in the P3Dv2.2 main folder. I actually made a copy of the prepar3d.exe and renamed it FSX.exe

2) I used the fsx/ fs9 registry repair tool found  here to set the registry entries for FSX pointing to my Prepar3d folder.

 

With p3dv1.4 I had used an even more "sophisticated" approach, to be able to install more complex add-ons, that included creating a few symbolic links, but I am not going to

do the same with P3Dv2.2 - I will wait for proper installers!

 

Every 3pd will, eventually, adhere to what is by far the reference now in terms of civil flight simulation for those who are FSX or even FS9 hardcore users ...

Ok .. thank you for that

 

I'll take a look at what you have suggested 

 

Cheers