Does Ezdok, Aivlasoft EFB working well with v2.5?

 

Do we need an update for the Estonia migration tool as well for 2.5? - Just asking, since I am hearing there has been changes in folder structure

Ad-don folder within P3D works a treat... installed 2 freeware addon scenery's and the entries are added automatically in the scenery.cfg so no hassle there!

 

Good stuff once you get your head around it!

Before I uninstall all addons, then I uninstall P3D 2.4.

Then I install P3D 2.5 ... and then? I install the new ORBXLibs and, only later, FTXGlobal etc.?

 

I did this by first uninstalling all my addons and the last uninstallation was p3d 2.4 which ended with error 1316. I tried some other ways, searched the internet for a solution but I could not uninstall p3d. So I gave up, renamed my old p3d-folder to something else and rebooted.

 

After this a clean install of 2.5. All went smooth with the final indication, that 2.5 was installed successfully. However, to my big surprise, nothing at all was installed, the new folder for 2.5 was absolutely empty.

 

I repeated this two or three time and finally gave up by completely restoring  my PC from a recent backup, tested p3d (it worked fine) and then began again with the uninstall procedure by starting with p3d 2.4 first and thereafter all my addons. Everything went smooth and also the installation of the new 2.5 was ok and it worked also very nice.

 

From this experience my hint: Start by uninstalling p3d first!

 

By the way, since it was late last night I only tested IVAO Ivap (it worked fine and I could see other aircraft after copying the MTL folder and adding the link), Vatsim vPilot (I could not see other aircraft because there were no others ;-) ) as well as FSUIPC and FSC. They were all fine despite the fact that I did not uninstall them but left them as they were.

 

Today the installation of all my addons will start, this will bring me a busy day and I sincerely hope that LM will spare us in future updates this ordeal.

Hi

Ezdok works with no problems that i can see

i used the migration tool to install and deleted the second prepar3d folder in the root file afterwards.

 

   steve

If you have NVidia it is always best to start with a fresh CP profile after P3D is updated, and if you ever install a new GPU driver. Lots of shimmering objects can be caused by an old NVidia profile.

 

 

 

 

I brought Nvidia CP to default before installing P3D 2.5. Then I put my parameters.

I will try to reinstall the drivers.

I brought Nvidia CP to default before installing P3D 2.5. Then I put my parameters.

I will try to reinstall the drivers.

Create a fresh profile *after* installing new drivers.

Create a fresh profile *after* installing new drivers.

Steve, I always do a clean installation of the driver, I think goes well.

I'm talking about the NVidia control panel, manage 3D settings, choose profile, press Restore, Apply. EVEN IF the Restore button is disabled, make a change, Apply, and then use the Restore button on that. Seems like a waste of time, but I had one PC BSOD-ing, and another with glittering artefacts, until I created a profile then restored to defaults.

A quick note about ASN:  When the Error! Message comes up, don't click OK.  You can then still use "ActiveSky weather theme" in the Weather Settings to make something much more realistic looking than default P3D.  

 

In previous P3D versions, if you didn't click away the Error! Message ASN would still bring in local live weather (when ASN was not current with the new realease of P3D).  This doesn't seem to be the case this time.

I'm talking about the NVidia control panel, manage 3D settings, choose profile, press Restore, Apply. EVEN IF the Restore button is disabled, make a change, Apply, and then use the Restore button on that. Seems like a waste of time, but I had one PC BSOD-ing, and another with glittering artefacts, until I created a profile then restored to defaults.

OK, thanks.

 The same thing happened to me - the installer said that it was finished but it did nothing!  I just tried again (after uninstalling what it didn't install in the first place) and it worked.  I never had that happen before with any program.

 

Well the third time was the charm. The only thing that seemed to work was running the install from the .msi installer file. That did it for me.. That was rather strange to say the least.. But my arse didn't release its wasted funding anyway....   :rolleyes:

 

Pivot

But my arse didn't release its wasted funding

 

:huh:

C:\Windows\System32\cmd.exe /c start "Prepar3d 2.5" /High "P:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe"

 

 

Thank you Denali, will capture this info for future use...

 

Pivot

I just installed 2.5 and run it completely vanilla, no tweaks, addons or anything. I get significant stutters regardless of ingame settings. However I might be an extreme case, some part(s) of my hardware just hates P3D it seems. I will try different tweaks when I get in the mood for it. 

 

It loads faster than before though. 

 

Yeah that was pretty much my experience after a very quick test flight before going to bed last night. It felt like what it did on previous versions when there was no AffinityMask entry on the config file. So I'll most likely put that one back in.

 

Ad-don folder within P3D works a treat... installed 2 freeware addon scenery's and the entries are added automatically in the scenery.cfg so no hassle there!

 

Which begs the question....why did they remove it in the first place?