Sign in to follow this  
Rob Ainscough

How to Update P3DV2.2 to P3DV2.3

Recommended Posts

If you run the patch you need to be at 2.2.10437  (not 2.2.10438 - that's the hot fix).

 

You will need lots of free space on for wherever your OS stores Temp files and/or where your package cache is located ... if you are short on disk space on C: (I believe 20GB free should be ok, but less than that might be a problem), you'll need to make room.

 

You need to make sure you backup 3 directories and delete 4 directories before you applying the patch.

 

BACKUP these three directories:

C:\ProgramData\Lockheed Martin\Prepar3D v2
C:\Users\Rob\AppData\Roaming\Lockheed Martin\Prepar3D v2
C:\Users\Rob\Documents\Prepar3D v2 Files

 

Now delete these -- Example (your account name will differ obviously):

C:\ProgramData\Lockheed Martin\Prepar3D v2
C:\Users\Rob\AppData\Local\Lockheed Martin\Prepar3D v2
C:\Users\Rob\AppData\Roaming\Lockheed Martin\Prepar3D v2
C:\Users\Rob\Documents\Prepar3D v2 Files

 

Key files are:

 

%PROGRAMDATA%\Lockheed Martin\Prepar3D v2
C:\ProgramData\Lockheed Martin\Prepar3D v2
                - Scenery.cfg

 

%APPDATA%\Lockheed Martin\Prepar3D v2

C:\Users\Rob\AppData\Roaming\Lockheed Martin\Prepar3D v2
                - DLL.XML
                - EXE.XML
                - SimConnect.xml
                - /Controls/*.xml  (joystick/device controller configurations)

 

%USERPROFILE%\Documents\Prepar3D v2 Files

C:\Users\Rob\Documents\Prepar3D v2 Files
                - Saved Flights (not critical)
                - SimConnect.INI (logging SimConnect)

 

Do NOT copy over your old v2.2 Prepar3d.cfg.

 

Personally, I prefer to start from a FULL install, but that isn't "required", it can be patched.

 

Cheers, Rob.

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Hi Rob,

 

I decided it would be best to have this information pinned instead of buried in a large post. Hope you do not mine.

 

Best regards,

Share this post


Link to post

"If you run the patch you need to be at 2.2.10437  (not 2.2.10438 - that's the hot fix)."

 

So what do those of us that are using 10438 do?

Share this post


Link to post

I was wondering where this post went. Great idea pinning this, Firehawk44.

 

 Cheers, Jazz

Share this post


Link to post

Crap!! Didn't read this till after i applied the patch! Dang!

 

Will see what happens! Gulp!!

Share this post


Link to post

Thanks for the heads-up Rob.  I patched P3D, deleted the Modules (FSUIPC) folder to avoid the reported CTD's and used your settings... http://www.robainscough.com/P3D_V2.php

 

All I have to day is wow!!  The latest v2.3 has been vastly improved.  I am not experiencing any screen tearing and the sim is silky smooth.  This is going to be a winner.

 

Thanks again,

 

Rob

Share this post


Link to post

 

 


I decided it would be best to have this information pinned instead of buried in a large post. Hope you do not mine.

 

Thanks for doing all that Jim ... and closing my other thread.

 

 

 


So what do those of us that are using 10438 do?

 

Locate your original Setup.exe for 2.2.10437 and run it, select repair button.  After it completes (may take some time) Now go to your P3D directory and right click and select properties on the Prepar3d.exe ... details tab, look at the file version ... it should read 2.2.10437.  Now apply the patch (make sure you have deleted the 4 directions I mentioned above).

 

LM recommend you do a complete wipe and full install of V2.3.  But try the patch process first and see if it works for you.   If you do patch be aware that you will need updates from some 3rd party product like FSUIPC (Pete), Virtuali, Orbx ... but if you patch correctly you will not have any EXE.XML or DLL.XML ... you will have to re-add those back and disable entries that are not compatible with v2.3.

 

Here is an example of my EXE.XML - as you can see Virtuali Add-On Manager is disabled until Virtuali release and update, however GoFlight and Saitek entries work fine with 2.3 as is:

 

<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>exe.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  
  <!-- Virtuali Add-On Manager -->
  <Launch.Addon>
    <Name>Couatl</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>fsdreamteam\couatl\couatl.exe</Path>
    <CommandLine>--mode=prepar3dv2</CommandLine>
  </Launch.Addon>
  
  <!-- GoFlight Modules -->
  <Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>GoFlight Hardware Interface</Name>
    <Path>V:\GoFlight\GFDevP3D.exe</Path>
    <CommandLine></CommandLine>
  </Launch.Addon>
  
  <!-- Saitek Panels -->
  <Launch.Addon>
    <Name>Saitek DirectOutput RadioStack</Name>
    <Disabled>False</Disabled>
    <Path>C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanels.exe</Path>
    <CommandLine>-run</CommandLine>
  </Launch.Addon>

</SimBase.Document>

 
Here is an example of my DLL.XML:
 
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>True</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>

<!-- FSUIPC -->
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>True</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>

<!-- Virtuali Add-On Manager -->
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>

<!-- Captain Sim 777 -->
<Launch.Addon>
<Name>Captain Sim Sound</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Captain_Sim\bin\cs.sound.dll</Path>
</Launch.Addon>

<!-- ORBX Generic Object Flow Library -->
<Launch.Addon>
<Name>ObjectFlow</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>V:\Lockheed Martin\Prepar3D v2\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll</Path>
</Launch.Addon>

<Launch.Addon>
<Name>ObjectFlow_11S_P3D</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>V:\Lockheed Martin\Prepar3D v2\ORBX\FTX_NA\FTX_AA_11S\scenery\ObjectFlow_11S_P3D.dll</Path>
</Launch.Addon>

<Launch.Addon>
<Name>ObjectFlow_EGPB_P3D</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>V:\Lockheed Martin\Prepar3D v2\ORBX\FTX_EU\FTX_AA_EGPB\scenery\ObjectFlow_EGPB_P3D.dll</Path>
</Launch.Addon>

<Launch.Addon>
<Name>ObjectFlow_05S_P3D</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>V:\Lockheed Martin\Prepar3D v2\ORBX\FTX_NA\FTX_AA_05S\scenery\ObjectFlow_05S_P3D.dll</Path>
</Launch.Addon>

<Launch.Addon>
<Name>ObjectFlow_PAYA_P3D</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>V:\Lockheed Martin\Prepar3D v2\ORBX\FTX_NA\FTX_AA_PAYA\scenery\ObjectFlow_PAYA_P3D.dll</Path>
</Launch.Addon>

<Launch.Addon>
<Name>ObjectFlow_CYSE_P3D</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>V:\Lockheed Martin\Prepar3D v2\ORBX\FTX_NA\FTX_AA_CYSE\scenery\ObjectFlow_CYSE_P3D.dll</Path>
</Launch.Addon>

<Launch.Addon>
<Name>ObjectFlow_SAK_P3D</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>V:\Lockheed Martin\Prepar3D v2\ORBX\FTX_NA\FTX_NA_SAK05_SCENERY\scenery\ObjectFlow_SAK_P3D.dll</Path>
</Launch.Addon>

<Launch.Addon>
<Name>ObjectFlow_KMRY_P3D</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>V:\Lockheed Martin\Prepar3D v2\ORBX\FTX_NA\FTX_AA_KMRY\scenery\ObjectFlow_KMRY_P3D.dll</Path>
</Launch.Addon>

<!-- Aerosoft Twin Otter Extended -->
<Launch.Addon>
<Name>Flight Recorder</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>
</Launch.Addon>

<!-- Carenado Piper Seneca V -->
<Launch.Addon>
<Name>CMeteoXml</Name>
<Disabled>False</Disabled>
<Path>.\CMeteoXml.dll</Path>
</Launch.Addon>

</SimBase.Document>

I'm certain most of these 3rd party products will have updates coming out shortly (if not already).

 

Cheers, Rob.

Share this post


Link to post

renamed the modules folder and P3D works now. 

 

The patchy triangle textures are still there, guess i'll have to roll back my drivers or wait until nvidia updates theirs. :-\

 

HDR looks brighter now, and a smoother sim experience!

Share this post


Link to post

Thanks Rob!  Saved me hours.  I was on .10438.  I backed up the folders you recommended, and then deleted the folders you recommended, ran the patch, and I am up and running great.  I had to copy back in the DLL (and disable Objectflow as well as FSUIPC), and also the dll entry or ASN.  TrackIR is working fine.  Thanks again Rob.  We should connect sometime and fly multiplayer.  I live the Bay Area and fly Cessna's out of RHV.

 

Best regards.

 

Jim

Share this post


Link to post

Hey Rob,

 

From my other post i didn't follow the directions as saw them too late... everything seems to work fine except for the FSUIPC thing but the sim is up and running fine... interestingly my exe and dll.xml files are fine and didn't need replacing.. they are still there...

 

Should i just go with it and be happy or have i stuffed up somewhere and will reap dire results down the track?

Share this post


Link to post

Good info, though it is a shame LM can't get their act together and do a simple procedure like a patch update without causing so many issues.it seems they don't have the ability like other companies do.

Its a bit late for me now as I just followed advice from one of LMs admins and was not told to do any of the above.

It seems LM are incapable of learning from past updates where similar issues arose.

Oh well here's hoping the whole thing aint completely screwed and I have to start from scratch.

Very poor service.

Share this post


Link to post

I just have to repeat that I haven't had any problems with patching (and, yes, I have had the hotfix applied)

 

 

In my opinion, the key is in peoples DLL.xml or EXE.xml.

Be sure to disable all entries and try running P3D v2.3

 

If it's running enable step by step.

 

 

FSUIPC is "fixed" with 4.934f

 

ASN crashes the sim also currently, I'm sure a solution will be provided fast (error clr.dll)

Share this post


Link to post

Locate your original Setup.exe for 2.2.10437 and run it, select repair button.  After it completes (may take some time) Now go to your P3D directory and right click and select properties on the Prepar3d.exe ... details tab, look at the file version ... it should read 2.2.10437.  Now apply the patch (make sure you have deleted the 4 directions I mentioned above).

 

I'm very surprised with this amateur procedure concerning the 2.3 update. It doesn't sound like a professionnal product I acquired.

 

- The hotfix 10438 comes from the editor of P3D isn't and we have to rollback to 10437. Where is the setup.exe I have "to locate" ? The 10437 seems not available anymore on my LM account.

 

- We are advised/recommanded to make again a full (re)install. It was the case with the previous updates. Will the game continues until end and users will have to re-install all their addos again and again every 3 months ?

Share this post


Link to post

Locate your original Setup.exe for 2.2.10437 and run it, select repair button. After it completes (may take some time) Now go to your P3D directory and right click and select properties on the Prepar3d.exe ... details tab, look at the file version ... it should read 2.2.10437. Now apply the patch (make sure you have deleted the 4 directions I mentioned above).

 

 

 

Even though this brings you back to .10437, I would not recommend doing this because this might also screw up some of the installed add-ons. For example, running the repair option of P3D will replace all FTX Global textures with the default ones, so that you have to reinstall FTX Global. Or: If you have disabled the default traffic dlls in scenery/world/scenery because you have installed an AI add-on then the repair routine will put a new traffic bgl in that folder which might mess with your AI add-on. Running a repair is not advisable from my point of view. If you cannot patch 10438 then you should rather do a full install. Or wait for some solution that LM might offer...

Share this post


Link to post

I seem to have a successful install beginning with uninstalling, backing up a few things that were left over, and then cleaning out the P3D2 folder entirely. It costs me around $100 USD in bandwidth to download the full 10+ Gb installer so I've been patching the original v2.0 release since it's initial release. My P3D installation was a bit of a mess with all the betas and development junk all over the place so I resolved a month ago to do a fresh install when 2.3 was finally released. Here's the process I used in case anyone else is "bandwidth challenged" and going the patch route:

 

Run the original v2.0 Prepar3D.msi, select the uninstall option

delete the 4 recommended program-generated folders (See Rob's first post, I backed up my saved flights, haven't put any back yet, deleted everything else)

reboot the PC

run the original v2.0 Prepar3D.msi again, install into the same folder

run the sim, close

 

delete the 4 recommended program-generated folders again

run the v2.1 patch installer (Prepar3D_v2_Academic_2.0.9448.0_to_2.1.9936.0_Patch.msp)

run the sim, verify version 2.1.9936.0, close

 

delete the 4 recommended program-generated folders again

run the v2.2 patch installer (Prepar3D_v2_Academic_2.1.9936.0_to_2.2.10437.0_Patch.msp)

run the sim, verify version 2.2.10437.0, close

 

delete the 4 recommended program-generated folders again

run the v2.3 patch installer (Prepar3D_v2_Academic_2.2.10437.0_to_2.3.11345.0_Patch.msp)

run the sim, verify version 2.3.11345.0, fly

 

I see no problems after an initial 30 min flight in the Raptor, no crashes, very smooth at 1100 kts, no blurries, bumped up some of the settings and everything looks good. I should have all my addons restored in about a week :smile:

Share this post


Link to post

You know im not one to point things out negativly, or vocalize my complaints very much, but I have to say I just dont get all this childish talk about the headaches of installing p3d particularly is it prevalent in the previous thread that was locked.  Maybe reflect back on what we had, and what we thought we were stuck with forever. 

 

I havnt installed 2.3 just yet as was actually due for a wipe so it will be a clean full install, but heck even with a screwed up patched install, sort it out. Im just thankful we are making some leaps and bounds off the coattails of FSX which we figured would never happen.  Now this 2.3 sounds pretty fantastic and surely a far cry from where we once were with ooms and instability.  With all the work that Rob A has done here as well as the many other beta testers and the devs at LM, lets show a little more appreciation for this and what its done for our hobby.

 

A little patience, and all the little addons will have updated installers. Like last few times. Just relax. :)

Share this post


Link to post

I figured it was time after the last several years since P3Dv1.4 to give it a full wipe.  Was already working on it... new larger 256GB SSD for the OS so that's getting a fresh install and now re-formatting my 512GB SSD just for P3D.  Already copied a backup of v2.2 in it's entirety so I can pick and choose what custom files I may want to use.  But this way I will have fresh defaults of 2.3 that I will make a back-up as well.

 

Looking forward to some great simming!

 

Clutch

Share this post


Link to post

I learned a lesson once the hard way; don't let your new guys make the installation sets - ever.  You don't need a train wreck where everything is supposed to be coming together.  But I don't have sympathy for anyone on this forum, since exposure to this forum may cause you to be conscripted into gamma (guinea-pig) testing.  Just keep wheeking and chattering about around here - you're asking for it.  :)    Me too, I almost peed my pants when I saw the post.


I decided to do a clean install.  I'm too bleary eyed at this hour.  I don't really have too much to replace yet.  Thanks be to Rob though for being in the trenches on this.

Share this post


Link to post

I just patched my 2.2.10438 to 2.3. Works absolutely fine. So there is no need to do a repair to revert back to 10437!

 

I deleted all the directories as advised, ran the patch and then inserted the relevant modules back into the newly built exe.xml and dll.xml one by one. This way you can make sure that you identify those modules that need updates and you can exclude them for now.

 

Just for information: Umberto has already uploaded the new Coutl version...

Share this post


Link to post

Hello everyone i have been waiting for quite some time to purchase p3d . now that 2.3 is out i guess its time to do it . But first i have a couple questions . firstly , if i purchase p3d today will it give me the option to install 2.3 right away or am i gonna have to install 2.2 then upgrade to 2.3 manually . second of all I heard that p3d must be installed to your os drive and then manually sent to another drive . can someone give me a link to a topic that discusses this issue and how to do it 

cheers

Share this post


Link to post

I'm pretty shure that purchasing Prepar3D today you will get the v2.3 installer.

 

And no, you don't need to install P3D on the OS drive. I did a clean install direct to my SSD H:\.

Share this post


Link to post

Three of us chatting last night while we were installing 2.3 on our machines.  The upgrade did not work for me or MartyB, so we each ran the full install on clean SSDs and had no issues.  Runs like butter.  Our third friend ran the updater without deleting files, etc. and his patched fine from 2.2 to 2.3.  I seriously think your success at running the upgrade has a lot to do with what add-ons and other factors make your individual setup unique (i.e. hardware, drivers, etc.)

 

Will be working on getting all the add-ons installed tonight.  So far it's noticeably better.  Will test multi-player out as well.

Share this post


Link to post

Guys... need some advice.... i patched my install to 2.3 WITHOUT first deleting all those folders etc...

 

I fear that i cannot now do the correct procedure just by deleting the folders and re-patching... is this possible? Everything is working OK but from reading the posts i should have done this properly... that will teach me for being hasty eh!

 

Can i do the above of no go?

 

Thanks guys

 

Doug

Share this post


Link to post

You have to go into your P3D main folder and take a look at the P3D.exe and right click and select Properties and see if it updated to the latest version. Mine did not (after following Rob's instructions) and I ended up uninstalling everything then downloading and installing the complete version.

 

Best regards,

Share this post


Link to post

This seems a bit de ja vu concerning the 2.3 patch process and needing to delete those folders and having to wait for other 3rd party patch updates including waiting for Pete to return from vacation - God bless him! :-)

 

Amid the frustration for those having trouble I encourage you to take a step back and know that these details will be worked out. 2.3 is here and we've had great insight as to what it brings. Cheers!

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this