bakayoyo

Both 2.5 and 3.0 are fully running on SSD. I'm just making an assumption that because 3.0 loads 600MB less VAS objects, it only seems to load objects when it needs them. Therefore 3.0 loads up scenarios more quickly. On the other hand 2.5 preloads a ton of object that it may or may not use, but when it does need them they have already been preloaded whereas 3.0 will always need to load new objects that it hasn't used yet.

That's a great overview of the new P3D v3.0 features. I've done some testing myself yesterday comparing performance and VAS usage between 3.0 and 2.5 with this result: My understanding of the behavior in the video is that P3D v3.0 only loads scenery that it needs therefore the VAS usage is much lower but it also means that it needs to do more scenery loading in-flight. When moving slowly at airports P3D v3.0 has higher FPS, but over extreemly crowded scenery FPS is a bit lower than P3D v2.5.

No missed that, been out of the loop for a while, going to check on that. edit: that's working now as well, only Active Sky Next doesn't seem to recognize the latest v3 yet.

Don't forget to backup your Prepar3d_v2 directories in local, roaming and program data before deinstalling v2. Always useful to have after a new install.

Remember that you're not just paying for new features in v3 but also for about 2 years of updates to that version. If you've already spent $2000+ on add-ons and hardware like me than supporting LM a bit more is a no brainer. Alternatively you could also entrust your investments to Dovetail and wait for them to develop the platform further. I'll stick with Prepar3d.

Looks pretty normal to me. My default file looks quite similar. Note that in P3Dv2.5 SimObject entries are now located as a seperate file in progdata.

A display port connection is the way to go with Ultrawide 3440x1440 panels. HDMI/DVI can't do 60Hz at maximum resolution, only display port can. I have a 34UM95 with a GTX 970, P3D and FSX run beautifully, absolutely worth the investment, so many games support ultrawide screen now.

My first impression is very positive. Using P3Dv2 got 20FPS on the runway in PMDG 737. Scenery max setting, auto gen normal. Running a 3770K with GTX970. Running FTX australia, global, vector, active sky and Ultimate Traffic 2. Not even tried the low-res pack yet. The frame rate compares well to other airports on my machine when running with UT2. VAS decreases most looking towards Sydney center, but very impressed how well VAS is released after clearing the airport. This is often the biggest problem with other scenery but works very well here. Still had enough VAS on arrival at Cairns to use GSX to deboard.

I've done a comparison video myself to see the difference before and after installing HDTrees coming from FTX Global. https://www.youtube.com/watch?v=aiW5i-HNUcQ The difference goes from barely noticeable to a marked improvement in definition of the treelines. In most cases the color is more natural looking. There's no noticeable difference in performance. I would say if you enjoy flying low over wooded hills you'll get your money's worth.

Thank you for the response. I understand the frustration, I think pretty much everyone gets that from time to time managing flghtsim software. I'm not sure Dovetail is going to work wonders on FSX judging from the lack of substantial development on their train simulator. P3D failing to start is often related to problems in the dll.xml and exe.dll. Restoring the config in %APPDATA%\Lockheed Martin\Prepar3D v2 could have introduced those issues. At least that would be the first place I'd look to correct such problems. There isn't really "a one size fits all" approach to migrating P3D installations to 2.5, it's always going to require some adaptation to each unique situation. But alternative options are of course starting from a clean install or sticking with 2.4. nothing wrong with that too.

It does work for some people. You couldn't start P3D at step 4? At that point you should have a clean untouched 2.5 install.

don't worry I didn't actually type all that, I keep my installation files in a directory. Yes, uninstalling all of that and then starting from scratch would be a nightmare for me too (this doesn't even list all the freeware I run). And not to mention the amount of tweaks (APX.bgl's, FTX Vector to resolve layer/elevation issues), aircraft merges etc. I've applied. I've updated Step 7 a bit, to keep the updated 2.5 default aircraft from reverting to 2.4: Step 7 Select all subdirectories in "Prepar3d v2.bak" except: propdefs, redist, ShadersHLSL, uires (<-So NOT these) move them into the new Prepar3d v2 directory. DO overwrite existing files. Note: I would also advice to copy the new 2.5 effects, fonts, gauges, simobjects and sound directories, and paste them over the backup 2.4 directories before moving them to the 2.5 directory.

That's true, I just happen to have a personal dislike of symbolic links especially when they span volumes. In my experience only Orbx FTX products modify terrain.cfg and they will eventually release installers that can find the new location themselves. So for me I don't really see the need arising for installing a legacy product that uses terrain.cfg in 2.5.

That's one way to do it, you could also copy the terrain.cfg back to the root whenever you install something and then copy it back to the programdata once it's done installing. My addons? a2a - accu-feel, a2a - C182 skylane bundle, a2a - Cessna 172 trainer Aerosoft - Airbus Extended X, Aerosoft - Airport Enhancement Services, Aerosoft - Antartica X, Aerosoft - Ayers Rock, Aerosoft - Bronco X, Aerosoft - Deutschland X Nord, Aerosoft - Dutch Airports, Aerosoft - German Airports 2 2012, Aerosoft - German Airports 3 2012, Aerosoft - German Regional Airports, Aerosoft - Gibraltar X, Aerosoft - Keflavik X, Aerosoft - Los Angeles X, Aerosoft - Lukla X, Aerosoft - Madeira X, Aerosoft - Mega Aiport Frankfurt X, Aerosoft - Mega Airport Amsterdam FSX, Aerosoft - Mega Airport Brussels X, Aerosoft - Mega Airport Dusseldorf, Aerosoft - Mega Airport Helsinki X, Aerosoft - Mega Airport Munich, Aerosoft - Tahiti X, Aerosoft - Twin Otter X, Aerosoft - US Cities X - Las Vegas, Aerosoft - VFR Germany 2010, Aerosoft - VFR Germany Ost, Aerosoft - VFR London X, Aerosoft - Yekaterinburg X, Alabeo - Waco YMF-5 Ants Airplanes - Eaglet Light Sport Aircraft Captain Sim - 707 Captain, Captain Sim - 767 Captain, Captain Sim - 777 Captain, Captain Sim - C130 Carenado - Cessna C337H Skymaster, Carenado - Cessna Grand Caravan FeelThere - EJET v2, FeelThere - Embraer Regional Jets V2 Flight 1 - BN-2 Islander, Flight 1 - OpusFSX, Flight 1 - Ultimate Traffic 2 Flight Store - FSUIPC FlyTampa - Hong Kong, FlyTampa - Montreal X FRANCEVFR - Alsace, FRANCEVFR - Lille Lesquin LFQQ, FranceVFR - Midi-Pyrenees.vol2, FRANCEVFR - NORD PAS DE CALAIS FSX, FranceVFR - Paris FS2Crew - PMDG 737 FSCaptain FSDT - GSX, FSDT - Honolulu Hawaii, FSDT - KLAX, FSDT - New York JFK FSGenesis - NextMap GSNext - Gifu Airbase Just Flight - 747 200-300, Just Flight - Air Hauler, Just Flight - MD81-82, Just Flight - Traffic 360, Just Flight - Tristar, Just Flight - VFR Real Scenery LatinVFR - KSAN San Diego Lionheart - Epic Victory LT, Lionheart - Quest Kodiak Majestic Software - Dash 8 MegaSceneryEarth - Switzerland Milviz - 737B, Milviz - Beechcraft Baron 55, Milviz - F15E OpenVFR - Germany OrbX - Australia, OrbX - EGHI - Southampton, OrbX - EU England, OrbX - EU Scotland, OrbX - EU Wales, OrbX - FTX AU Traffic, OrbX - FTX Global, OrbX - FTX Global Vector, Orbx - FTX Jacksons, Orbx - FTX KRDD, OrbX - FTX NA Gold NCA, OrbX - FTX OpenLC EU, OrbX - North Island NZNI, OrbX - NZMF - Milford Sound, Orbx - Pacific North West, OrbX - Queenstown ,OrbX - Shoreham, OrbX - South Island NZSI, OrbX - YBAS - Alice Springs, OrbX - YBBN - Brisbane, OrbX - YBCS - Cairns, OrbX - YHBA - Hervey Bay, OrbX - YSCH - Coffs Harbour Pacific Island Simulation - Marshall Islands, PacSim - Chubu international, PacSim - Jeju International, PacSim - Manila, PacSim - Nagasaki International ,PacSim - Xiamen Gaoqi International PMDG - PMDG 737 NGX, PMDG - PMDG 777-200 QualityWings - The Ultimate 146 Collection, QualityWings - Ultimate 757 collection RealAir - Lancair Legacy, Realair - Scout, RealAir - Turbine Duke REX Studios - Real Environment Xtreme, REX Studios - REXessentials ScanSim - Copenhagen Kastrup X Scenerybox - 57 Moselle LD Technobrain - Naha FSAC ROAH Thai Creation - Namaste Nepal UK2000 - Birmingham, UK2000 - Edinburgh, UK2000 - Gatwick, UK2000 - Heathrow, UK2000 - London City, UK2000 - Manchester UK2000 - VFR Airfields vol.1 Virtavia - C-17 Globemaster, Virtavia - Sea King Virtualcol - Embraer 170-175 VRInsight - M-Panel I don't have VoxATC so can't say anything about that. For OrbX I disabled the ObjectFlow.dll in dll.xml For Ultimate Traffic 2 I edited the simobjects.cfg For FSUICP I installed the latest version For FSDreamteam I installed the latest addonmanager No major issues so far, I use older weather engines, REX Essential Plus Overdrive and OPUSFSX, they both insert weather, although it seems to be at a significant performance hit with lots of clouds around.

As it seems unlikely we'll have updated installers soon, I wrote down my installation "method" steps to share with others. Step 1 Rename the directory of Prepar3d 2.4. Eg. "Prepar3d v2.bak" Step 2 Backup these directories then delete the originals. %PROGRAMDATA%\Lockheed Martin\Prepar3D v2 %APPDATA%\Lockheed Martin\Prepar3D v2 Also delete these directories (backup flights if you want) %LOCALAPPDATA%\Lockheed Martin\Prepar3D v2 %USERPROFILE%\Documents\Prepar3D v2 Files Step 3 Uninstall Prepar3d 2.4 Step 4 Install Prepar3d 2.5 to same location where Prepar3d 2.4 was before. Then run Prepar3d 2.5 once to generate its configuration files. Step 5 Restore configuration files, overwrite existing files. %PROGRAMDATA%\Lockheed Martin\Prepar3D v2 %APPDATA%\Lockheed Martin\Prepar3D v2 Note: Prepar3d.cfg has changed so you may want to keep the 2.5 file, but the 2.4 file will work ok. Step 6 Select all files in your "Prepar3d v2.bak" directory copy & paste them into the new Prepar3d v2 directory. DO NOT overwrite existing files. Step 7 Select all subdirectories in "Prepar3d v2.bak" except: propdefs, redist, ShadersHLSL, uires (So NOT these) move them into the new Prepar3d v2 directory. DO overwrite existing files. Note: this will overwrite included P3D updated aircraft, if you want the keep these, first copy the new simobjects directory over the backup simobjects, then move it. Step 8 Find the file "terrain.cfg" in your Prepar3d v2 directory. Copy that file to this configuration directory: %PROGRAMDATA%\Lockheed Martin\Prepar3D v2 Step 9 (optional) Prepar3d v2 2.5 has a new file for SimObjectPaths. To fix issues examine your Prepar3d.cfg file in %APPDATA%\Lockheed Martin\Prepar3D v2 and find eg. SimObjectPaths.9=SimObjects\UT2 Aircraft Now find the file "simobjects.cfg" in %PROGRAMDATA%\Lockheed Martin\Prepar3D v2 Create an extra entry for all missing Simobject eg.: [Entry.9] Path=SimObjects\UT2 Aircraft Step 10 Enjoy using all your add-ons in Prepar3d v2 2.5