There's some good advice found over on the Avsim Forum worthy of reading from a member of the Lockheed Martin technical support team.https://www.avsim.com/forums/topic/5126 ... tallation/
It's of particular importance to consider these comments made by the Avsim Posting Author.
1] Lockheed Martin has provided guidance to developers via their Software Developers Kit (SDK, for short) that explains very specifically that all code elements and modeling elements used within Prepar3D v4 should be exported using the SDK tools that ship with Prepar3D. This means that simply moving an FSX/Prepar3D v3 scenery into Prepar3D v4 will put your simulator at risk of becoming unstable, or working irregularly. (Airplanes generally aren’t a drag-and-drop factor here because they need to be recompiled in x64.)
2] With this in mind, it is incumbent upon developers to not simply “re-wrap” existing products to make them “installable” within the Prepar3D v4 environment without ALSO taking the time to re-export the code and model elements using the Prepar3D v4 SDK tools. If a developer simply updates their installer to allow you to install in the Prepar3D v4 environment without also taking the time to re-export the code and model elements- your sim is at risk of becoming unstable, just as if you had drag-and-dropped a non Prepar3D v4 product.
3] Tools that allow users to alias older, Prepar3D v3, FSX, FSX-SE scenery and utilities into Prepar3D v4 are a sure-fire way to make your simulation unstable.
THINGS YOU MUST STOP AND CONSIDER:
1] Prepar3D v4 is stable. It is probably one of the more stable simulation releases we have seen in years.
2] Prepar3D v4 is not v3. It is not FSX. It is not FSX-SE. (And I know how XPL users hate being left out, so no, it isn’t XPL either. :laugh:)
With those things, considered- here are some rules to live by:
1] Do NOT install aircraft, scenery, utilities into Prepar3D v4 that were not designed using the Prepar3D v4 SDK. (Re-read that sentence it is important!)
2] Do NOT force Prepar3D v4 to utilize scenery that you previously had installed for Prepar3D v3, FSX, FSX-SE (or yes… XPL! :cool:)
3] Do NOT use utilities designed to allow you to “unify” your installations by feeding non-Prepar3D v4 scenery/utilities into Prepar3D v4.
The most important piece of knowledge you can have to maintain stability of Prepar3D v4:Before you install ANYTHING into Prepar3D v4, you should take the time to research whether the developer merely adjusted their installer to account for Prepar3D v4, or whether the developer actually took the time to re-export BOTH the code elements AND the model elements of a product using the developer/SDK tools that were provided by Lockheed Martin for use with Prepar3D v4.
Also you might need to consider the following comments from the Avsim Posting that the "Lockheed Martin technical support team is able to clear a significant number of CTD issues within Prepar3D v4 by simply removing aliased and non-compliant scenery and utilities." Users need to be mindful that Prepar3D v4 is a unique platform, and just because an old favorite scenery will load does not mean that it will run without undesired side effects.
Also take note of the Author's Avsim posting regarding BONUS MATERIAL:
The following list is a trouble shooting checklist we have found that helps users to identify and self-resolve reports of FPS and performance loss when using our products. I’m tacking it on here free-of-charge in hopes that it helps you to see the methodical ways you can self-diagnose performance issues within Prepar3D v4:
1] Are you running the latest GPU drivers?
2] Are you using PMDG’s product at a legacy airport (FSX/FSX-SE/Prepar3D v3 scenery imported by drag-and-drop or aliasing tool), if so, you should check with the scenery developer for a version of the scenery that was recompiled specifically for Prepar3D v4 using the Prepar3D v4 SDK tools.
3] What are your Anti-Aliasing settings? SGSS causes pretty hard FPS drops while MSAA up to 4x does not impact too much. MSAA 8x has a small impact but is manageable on most machines.
4] Are you running both Dynamic Lighting and Dynamic Reflections? There have been reports on LM beta forum saying that Dynamic Reflections on high while also using dynamic lighting together will eat FPS performance significantly. With PMDG products its recommended that Dynamic Reflections be turned off completely unless you find the performance hit to be acceptable.
5] If you are receiving odd CTDs or performance loss, look carefully through the tools, utilities, scenery, add-ons that you have installed and make certain that they are actually Prepar3D v4 compatible.
When In doubt, ask your tool/utility/scenery/add-on developer the following question: “Was this product exported using only the Prepar3D v4 SDK tools?” If the answer is anything other than “yes” then it COULD be a problem within the sim.
Hope this is helpful to the NZ Flight Sim community who maybe considering a future prepar3d v4 installation.