Thanks for the tip. I will do that and hopefully save alot of time NOT reinstalling uk2000,FSDT and Flightbeam airports and all my FTX regions. What about EZCA and FSUIPC. Do they stay intact in the folders after uninstall of 2.3? Uninstall via Windows control panel right?

 

Thanks Michael

I didn't port over EZCA to P3D, but yes...ANYTHING you had up and running, and you could access in the ADD-ON drop-down menu, will be there for you in  V2.4 as per my instructions.  Yeppers!

Hi everyone

 

I have just noticed that Rob says copy the files SimConnect.cfg and Simconnect.ini back to the documents folder

 

For some reason I cannot see those entries at all

 

Also I do not have the SimConnect.XML file that he says is in the roaming\Lockheed Martin\prepar3Dv2 folder 

 

Any ideas?

 

 

Paul

Hi everyone

 

I have just noticed that Rob says copy the files SimConnect.cfg and Simconnect.ini back to the documents folder

 

For some reason I cannot see those entries at all

 

Also I do not have the SimConnect.XML file that he says is in the roaming\Lockheed Martin\prepar3Dv2 folder 

 

Any ideas?

 

 

Paul

 

I have read that you won't have those files if you don't have an addon that uses them.  So just ignore that step.

 

Ryan

Mitch is on to something, though. I did the patch according to Rob' instructions and I do have 2.4, but the F22 Raptor is broken. That must be the only difference.

Thanks Ryan

 

Ok I have applied the patch and it has updated to 2.4 successfully

 

Do I copy back all of the files (which I backed up) that aren't in the newly created folders  as well as the files Rob has indicated to copy back?

 

Paul

Followed Rob's patch instructions and everything went perfectly.

 

Russ

The patch worked fine here. (v2.4.11570.0) The install went smoothly and was easy as pie.

@Paul_...just copy the files specified by Rob, and you should be fine. Hold on to your backups, just in case you need them.

 

 Jazz

Mitch is on to something, though. I did the patch according to Rob' instructions and I do have 2.4, but the F22 Raptor is broken. That must be the only difference.

Jab, with the full update, my Default plane now is the A35 Lightning. So, there are changes to the scripts....and I know that I did feel better knowing that it was a true virgin v2.4 install, and not a v2.4 'layer' over v2.3's files.  It only took me about in total---1/2 hour beyond the time it takes the full installer to do its thing. I lost nothing, except a few minutes re running Global,Vector, OpenLC Europe, and bringing my saved REX4 Direct theme back to the now, v2.4

Anybody tried FSGRW with V2.4??

Jab, with the full update, my Default plane now is the A35 Lightning.

What gets broken in the patch is the default flight. The two aircraft work fine after that.

 

EDIT. The more I thought about this, I wonder if the patch doesn't replace the 2.3 default flight file under some circumstances. LM seems to modify the flight file format with each release and this could account for some of problems that I experienced initially with the default flight in 2.4.

I know that I did feel better knowing that it was a true virgin v2.4 install, and not a v2.4 'layer' over v2.3's files.

 

If you follow Rob's guide shouldn't it be exactly the same as installing it from scratch? Can someone confirm this for me? I am on the verge of updating and I need to choose whether to patch or to clean install 2.4.

 

Digitally speaking, will there be a difference or is it exactly the same once patched properly. 

Hi everyone

 

Just to let you know ... everything went very well indeed and it's patched perfectly .... and all my addons are in and having no issues  ...

 

I did take a look at the new cfg file and made a couple of added entries from my old cfg ...

 

Thanks for you help fellas

 

Paul

Patched to v2.4 per Rob's instructions .... perfect. Thanks, Rob.

Everything working, except ASN.

To my eyes, I'm not sure what's improved, as v2.3 was doing great, but it's good to keep up with the patches.

Onward and upward...

I know this is really obvious but...

 

You must follow Rob's instructions EXACTLY. I checked and double checked each folder I was backing up. Started a new folder called LOCKHEED MARTIN BACKUP FILES then with each folder I used the "copy address as text" option and renamed each folder as I backed them up to show the full PC address location

 

ie with C:\Users\Rob\AppData\Roaming\Lockheed Martin\Prepar3D v2

 

my new backup folder would be renamed CUsersRobAppDataRoamingLockheed MartinPrepar3D v2 (folder renaming does not allow the \)

 

Then you are sure to replace the correct files from each folder in the new V2.4 install.

 

Worked for me.

 

And I've double-checked I have v2.4

 

Hope this helps

I have just completed the patch update process, and I seem to have avoided any "spontaneous P3D combustion" on my PC. The default F22 flight seems to load properly, and I tested my saved RealAir Beechcraft Duke startup flight. That also loaded without incident. I think I may just have dodged that bullet I mentioned :smile:

 

I can confirm that my Prepar3d.exe file is version 2.4.11570.0.