Cannot repair, re-install or uninstall FSX.

Hey Kevin, Prepar3d does run about 99.9% of addons - it uses the same core as FSX (Microsoft selling the ESP code to Lockheed Martin), has an SDK that though being developed still seems to function with most addons requiring it (AES being an excpetion) and has a 3rd party developer that has developed a simple way to avoid registry edits and careful placing of files with a product called "FSX to Prepar3d migration too"l that makes it simple to install your FSX addons with little hassle.

 

A few things to keep in mind, and summarised as there's a heck of a lot of discussion on it - EULA's (end user licensing agreements). In short, P3D is not to be used for entertainment purposes, and a lot of addons are only suppossed to be used for entertainment purposes .... so you can see there's going to be some issues there. But the law is actally far fairer than a lot of people give it credit for. I'm not sure what developer would pursue an EULA infringement, it's more there to protect those developers from being sued for their entertainment product being used for real world training purposes and a deficiency in their product leading to a case for damages. I simply mention it as you start finding out some more detail I'm sure you'll see a lot of this discussion.

 

IMHO Prepar3d is a great product. I use it alongside X-Plane 10 which is also continuing on a development cycle. Many add-on developers/publishers like FSDreamteam and Aerosoft are now making installers that support both FSX and Prepar3d. Folk like FTX are even going back to redo all their past product installers to support both FSX and Prepar3d. There is an awareness in the developer community that FSX is reaching it's EOL, and nothing reflects that like Microsoft stopping support for the product - yet strangely continung to sell it on the GFW site .... Hmmmmm.

 

The other important piece is that Prepar3d V2.0 will come along and introduce DirectX11. You're entitled to upgrades untl that version - they're currently at V1.4 (consider each of these dot releases a service pack) - but it does mean you will have to buy V2.0 in a similar way you had to with the move from FS9 to FSX. When that will actually happen is anyone's guess, but releases happen about every 5 to 6 months and it might be another "service pack" , ie 1.5, or it might be V2.0. Either way the recommendation from Lockheed Martin is a fresh install, which also means reinstallation of all your add-ons as well. Seems a bit painful, but worthwhile to make sure it's fresh as it can be.

 

Should also be mentioned that the needs for performance tweaking have been minimised. Many of the improvements found over the last 6 years by various folk such as *******, Word Not Allowed and NickN are now incorporated in the core code. But some tweaking can still be effective in maximising performance - everyone's PC's is a little different and the programming is still reliant on finding what works for your CPU/BUS speed/storage/RAM/GPU combination.

 

I realise I've written more than usual passing lines, but if you're looking at Monday doing a lengthy and tedious install I've hopefully summarised what you need to think about in relation to Prepar3d alternative to FSX. In short it will require some investment (purchase Prepar3d, the P3Dmigration tool), comes with some legal issues you should ponder to determine if you get either the professional or the academic version (I use the academic version and I'm not using it for commercial purposes), will maybe need another step change down the path to V2.0 (which as we've seen with DX10, even with Steve's fixes, has made some addons not work properly) but I'm happy to be using a product that has an active development team that is producing a product that built on the best of FSX and continues to improve FSX's problems.

 

Enjoy your time with your grandkids and good luck no matter which way you go!

Hey Kevin, Prepar3d does run about 99.9% of addons - it uses the same core as FSX (Microsoft selling the ESP code to Lockheed Martin), has an SDK that though being developed still seems to function with most addons requiring it (AES being an excpetion) and has a 3rd party developer that has developed a simple way to avoid registry edits and careful placing of files with a product called "FSX to Prepar3d migration too"l that makes it simple to install your FSX addons with little hassle.

 

A few things to keep in mind, and summarised as there's a heck of a lot of discussion on it - EULA's (end user licensing agreements). In short, P3D is not to be used for entertainment purposes, and a lot of addons are only suppossed to be used for entertainment purposes .... so you can see there's going to be some issues there. But the law is actally far fairer than a lot of people give it credit for. I'm not sure what developer would pursue an EULA infringement, it's more there to protect those developers from being sued for their entertainment product being used for real world training purposes and a deficiency in their product leading to a case for damages. I simply mention it as you start finding out some more detail I'm sure you'll see a lot of this discussion.

 

IMHO Prepar3d is a great product. I use it alongside X-Plane 10 which is also continuing on a development cycle. Many add-on developers/publishers like FSDreamteam and Aerosoft are now making installers that support both FSX and Prepar3d. Folk like FTX are even going back to redo all their past product installers to support both FSX and Prepar3d. There is an awareness in the developer community that FSX is reaching it's EOL, and nothing reflects that like Microsoft stopping support for the product - yet strangely continung to sell it on the GFW site .... Hmmmmm.

 

The other important piece is that Prepar3d V2.0 will come along and introduce DirectX11. You're entitled to upgrades untl that version - they're currently at V1.4 (consider each of these dot releases a service pack) - but it does mean you will have to buy V2.0 in a similar way you had to with the move from FS9 to FSX. When that will actually happen is anyone's guess, but releases happen about every 5 to 6 months and it might be another "service pack" , ie 1.5, or it might be V2.0. Either way the recommendation from Lockheed Martin is a fresh install, which also means reinstallation of all your add-ons as well. Seems a bit painful, but worthwhile to make sure it's fresh as it can be.

 

Should also be mentioned that the needs for performance tweaking have been minimised. Many of the improvements found over the last 6 years by various folk such as *******, Word Not Allowed and NickN are now incorporated in the core code. But some tweaking can still be effective in maximising performance - everyone's PC's is a little different and the programming is still reliant on finding what works for your CPU/BUS speed/storage/RAM/GPU combination.

 

I realise I've written more than usual passing lines, but if you're looking at Monday doing a lengthy and tedious install I've hopefully summarised what you need to think about in relation to Prepar3d alternative to FSX. In short it will require some investment (purchase Prepar3d, the P3Dmigration tool), comes with some legal issues you should ponder to determine if you get either the professional or the academic version (I use the academic version and I'm not using it for commercial purposes), will maybe need another step change down the path to V2.0 (which as we've seen with DX10, even with Steve's fixes, has made some addons not work properly) but I'm happy to be using a product that has an active development team that is producing a product that built on the best of FSX and continues to improve FSX's problems.

 

Enjoy your time with your grandkids and good luck no matter which way you go!

Wow great info for me as well there thanks. New to P3d, infact still installing all addons from my previous FSX.

The Pro P3d is not really an option as far as i understand $199, academic version is same thing except it has a logo, and costs $40.

As far as i know all folks leaving fsx for p3d are buying academic version.