why is everyone rushing to install their 3rd party stuff minutes after installing 2.5?  why not wait for the 2.5 installers/patches to release.

 

This is one of the reasons why I will not be installing 2.5 immediately. There are other reasons, but this one will do for now :smile:

I'm just flying my 777.  Installed FSUIPC and enjoying my flight.

 

You think the worlds gonna end tomorrow if every addon is not installed right now.

 

Ya'll have fun I'm flying. 

 

 

PS  I didn't realize the default desert looked so much better than FTX Global

Anyone...??? 

can  tell me how install Ivao  to use the MTL (using Vpilot) I am trying to install the last version Ivao but it says cant find P3d....any Idea?

Thanks

Pedro

Doesnt have to be Ivao..I just need IA packages suggestions to recognize match models in Vpilot ( vatsim)???

Any suggestions will be appreciated.....

Thanks guys

This is one of the reasons why I will not be installing 2.5 immediately. There are other reasons, but this one will do for now :smile:

 

+1. And there's no guarantee that LM won't release another patch near future. I might have to wait until 2.6.

+1. And there's no guarantee that LM won't release another patch near future. I might have to wait until 2.6.

 And you could very well run into the same situation with 2.6. this is what we're facing with a platform that is in a state of constant development. No development gives you a stable platform because you don't have to worry about changes breaking something else. A developing platform can be improving but you have to live with the constant updating of your addons.

 

You think the worlds gonna end tomorrow if every addon is not installed right now.

 

I don't use default scenery, so installing all of my addons is mandatory.

Installed, but with default stuff it is really difficult to determine any performance/quality gains. Need ORBX! 

Do the 2.4 Carenado planes install correctly?  

 

Bob

 And you could very well run into the same situation with 2.6. this is what we're facing with a platform that is in a state of constant development. No development gives you a stable platform because you don't have to worry about changes breaking something else. A developing platform can be improving but you have to live with the constant updating of your addons.

 

True. But, it's not just a regular update. With 2.5 LM is changing basic structure. So, it'll take time for developers to modify their addons for new structure. I guess 2.6 update will be lot easier. I could skip this one and wait until 2.6 like I skipped 2.3 and jumped from 2.2 to 2.4. 

 

 

And does not it seem strange that something so important was not included in the final version?

 

It's in the Learning Center .chm documentation ... I'm sure you read the documentation? 

 

Cheers, Rob.

What gets me is this all or nothing thing when it come to reinstalling addons.

Just take it easy, I generally just put in one aircraft and two airports then add another airport for the next flight.

It's a great excuse for a tour around my European payware airports and by the time i am back home in EGGW I have everything installed nicely without having to sit for hours running installers.

 

 

And there's no guarantee that LM won't release another patch near future. I might have to wait until 2.6.

 

Any future patches will be based on a clean v2.5 install, there will be NO v2.4 ---> v2.6 patch or v2.3 ---> v2.6 patch.  There would only be a v2.5 ---> v2.6 patch.  This is why the restructuring is being done now for v2.5.

 

Cheers, Rob. 

 

 

Hi Rob any idea why Ivao install (just o get the MTL and use with Vpilot ) is not recognizing P3d?

 

No sorry, I don't use IVAO ... best talk to them.

 

Cheers, Rob.

 

 

This to confirm the updated Addon Manager, which supports P3D 2.5, is available on our site.

 

Excellent, glad you see your team is on top of this Umberto, very responsive.

 

Cheers, Rob.

Would be nice in future LM could make an autoupdater so no need of more installing from zero.. so if you have other texture files it would ask you before installing. Something is done in xplane.

 

 

has anyone tried copying then pasting those cfg files into the original location these apps were looking for prior to 2.5?

 

Yes, that's exactly what I did ... and then copy them out of their original locations after they were updated back to the ProgramData folder.

 

Cheers, Rob.

Yes, that's exactly what I did ... and then copy them out of their original locations after they were updated back to the ProgramData folder.

 

Cheers, Rob.

 

Thanks Rob - and thanks too for all the videos you've published and advice re 2.4/2.5. Appreciated.

Concerning FTX Central. It will crash!!

 

Try this on your own risk!!!!!!! FTX Central is looking for the terrain.cfg. In v2.4 it was in the main sim folder in v2.5 LM moved the terrain.cfg into this folder C:\Users\Rob\AppData\Roaming\Lockheed Martin\Prepar3D v2 All you have to do is copy the terrain.cfg to the main sim folder. Install all your ORBX addons and copy the terrain.cfg back to C:\Users\Rob\AppData\Roaming\Lockheed Martin\Prepar3D v2 thats it

Thanks Mickey. I'll do that.

This to confirm the updated Addon Manager, which supports P3D 2.5, is available on our site.

 

No need to re-download the full installers (GSX or FSDT sceneries), as long they were compatible with 2.4, they will still work in 2.5 and will download the updated Addon Manager .DLL which is needed to support P3D 2.5 when they are run.

 

So, if you reinstalled P3D 2.5 from scratch, and your FSDT installers already supported P3D 2.4, there's no need to download any new installer: just run the installers you have after installing P3D 2.5, with no need to download anything else.

 

If, instead, you get an error message from any FSDT installer about the P3D version being not recognized, it means THAT installer you had was still a pre-2.4 version, so it will have to be downloaded again.

 

As usual, the updates will continue to be entirely free, and we support FS9 ( when the products supports it), FSX, FSX:SE and P3D 1.x and 2.x, always with the SAME LICENSE.

Thanks for this.