Question for those running 2.5 :

 

As a temporary fix to get non-working addons like the GTNs and other terrain.cfg and/or scenery.cfg dependent software working, has anyone tried copying then pasting those cfg files into the original location these apps were looking for prior to 2.5?

Question for those running 2.5 :

 

Is it possible for the time being to get non-working addons like the GTNs and other terrain.cfg and/or scenery.cfg dependent software by copying then pasting these cfg files into the original location these apps were looking for?

 

Hi Robert,

 

I've just successfully installed Tongass Fjords X by moving the config files around, so that's not an issue (you just need to remember to move the files back to c:\ProgramData\Lockheed Martin\Prepar3D v2\ afterwards). As regards the GTNs, however, I'm afraid they are tied to specific versions of core DLLs, so we'll need to wait for F1 to release an updated version.

 

Tym

They have clearly stated that we need to wait for the updated Orbxlibs, which contain the new FTX Central. It is FTX Central that manipulates terrain.cfg and scenery.cfg, so no need to update individual regions, airports and other installers.

 

Tym

Let me understand because I'm stupid.

 

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.?

Are the stutters gone for the average user?

Hello Rob said here

http://forum.avsim.net/topic/460387-prepar3d-v25-development-update/?p=3170788

 

that LM would add new settings that would like this:

 

[TERRAIN]

UseGlobalTerrainView=True

 

But when I looked into my P3D.cfg there is under Terrain

 

UseGlobalTerrainView=False

 

Is there a mistake or should I change to True by myself?

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.

No mistake, default value is False to try it change it to True

Are the stutters gone for the average user?

I just did a quick circuit at 4am when I had just finished downloading. Absolutely nothing added, nothing tweaked, flying the default F22, I could not see any stutters.

 

Thanks for that, Umberto. Just re-installing.

No mistake, default value is False to try it change it to True

Or maybe the right value is "false" and he was confused Rob writing it?

I am afraid, low fps, stutters, blurries and all the ugly stuff will retun. I recall, initial reports on pre-2.5 versions were very optimistic, too. The reporters were certainly right. I doubt it was the new version, though, but just a clean install.

 

I experienced this several times: Even moving prepar3d.cfg, dll.xml, and exe.dll out of the way made a completely new simulator. Hassle started after adding addons again. Which we certainly will not dispense of.

 

Kind regards, Michael

The value LM chose as the default value is 'False' this makes no changes to the way the sim operates and is therefore logical. In order to help with blurries on some systems you have the option to change it to 'True'

 

I think the confusion is that the default value is 'False' and rob wrote it as True so you could try it. So your both right.

The value LM chose as the default value is 'False' this makes no changes to the way the sim operates and is therefore logical. In order to help with blurries on some systems you have the option to change it to 'True'

 

I think the confusion is that the default value is 'False' and rob wrote it as True so you could try it. So your both right.

Then another trick that you have to know?

It seems strange, Rob is a beta tester and if he wrote that they added "UseGlobalTerrainView=True", why the final product is different?

Then another trick that you have to know?

It seems strange, Rob is a beta tester and if he wrote that they added "UseGlobalTerrainView=True", why the final product is different?

The trick is, he wrote something like... To try it yourself add this line... UseGlobalTerrainView=True

If he'd have written UseGlobalTerrainView=false and then change it to true it would have been more words and even more confusing than this is getting lol

The trick is, he wrote something like... To try it yourself add this line... UseGlobalTerrainView=True

If he'd have written UseGlobalTerrainView=false and then change it to true it would have been more words and even more confusing than this is getting lol

No, the confusion now is that we do not know what this need and that we do not know which is correct.

Yeah this Situation is little bit confusing and I think it is a missunderstanding.

I now changed it to True and it performs in my first flight better.

But I will test more.