I have installed v1.30 to P3D yesterday and I didn't see any problems. My OpenLC works good, Vector seems to bo OK as well (but that was a quick look).

 

In some other posts you wrote that you made some uncommon reinstallation of your P3D.

Could it that be, that this process destroyed something in your orbx installations?

What you refer to was when I went from v2.3 to v2.4. I then completely formatted my P3D hard drive..and did a virgin install of v2.3    I can't see that that had anything that might have produced such lousy graphics after the Global 1.30 install into P3D.  Into FSX, it was a win-win.  I went back to Global 1.20 the same way that placed 1.30 into P3D, and going back gave me no gas.  Dunno...but all is good, for I have always liked what v1.20 produced. I'm good with that for P3D.  Thanks for your thoughts upon the matter!

 

Mitch

Hi Mitch,

 

Seems you are having a few issues with recent updates.

 

Did you also install the new Orbx libraries?

 

Did you check that the scenery library insertion point for Orbx products was still correct?

 

I think you have to have the OpenLC entries BELOW Addon Scenery, and the FTX Regions above Addon Scenery.

 

I've had no problems with the 1.30 Global update in P3D 2.4. I did have an issue a few weeks ago with my lclookup.bgl file but a replacement was provided when I raised the issue on the Orbx forums - it was my fault - I accidentally overwrote the original file!

 

Daz

Very interesting.....v1.30 fabulous...in use with FSX! Nothing of the kind...to what you see in P3D v2.x In fact...I would not hesitate to recommend, hand's down..that if you want to run Global 1.30 in FSX...(probably the graphics are truly designed to run in this platform only...truly...)

 

To be honest Mitch some of the stuff you're spouting in crazy... your 'yay this is great posts' are kind of amusing, but the sort of misinformation your coming out with now is not helpful at all.

 

You don't seem to have a clue what your doing, and blaming everyone but yourself for the mess you get in.

 

FTX Global is not 'truly' designed to run in FSX only, or is somehow better on that platform, and to suggest so is utter BS.

Having just installed Global 1.3 its important to check the scenery library order. Installing the 1.3 patch puts all the LC entries to the top of the library.

 

It needs to be re arranged as per the following guide:

 

http://www.orbxsystems.com/forum/topic/81831-setting-your-openlc-entries/

For the record, no issues at all here in FSX or P3D once the library was sorted.

Having just installed Global 1.3 its important to check the scenery library order. Installing the 1.3 patch puts all the LC entries to the top of the library.

 

It needs to be re arranged as per the following guide:

 

http://www.orbxsystems.com/forum/topic/81831-setting-your-openlc-entries/

For the record, no issues at all here in FSX or P3D once the library was sorted.

I do not have FTX region or airports, so it's good to have the openLC entries to the top, right?

I do not have FTX region or airports, so it's good to have the openLC entries to the top, right?

 

Put your OpenLC entries just below your Addon Scenery entry.

 

Any subsequent airport / scenery installations should be above Addon Scenery entry (and probably will be by default).

 

This also ensures that any 3rd party scenery addons that use the Addon Scenery folder will be layered correctly with respect to OpenLC.

 

Daz

Just finished installing and testing FTXG 1.30 and have zero issues, in combination with OpenLC/Regions and Airports. My FTXG insertion points are as they should be, with no need to make manual changes.

 

Its all looking and running mighty fine here B)

Ive just finished a clean install of P3D v2 and FSX with Global1.3 + Vector + LC + Europe. If you inspect the Scenery Config using the fs-sceditor downloadable from Sourceforge (it wont let me post a link) it identifies path errors in the P3Dv2 Scenery Config which Ive had to manually correct several times. The errors sometimes appear if you open FTX Central for P3DV2 and make changes

 

No such problem with the equivalent FSX installation. Maybe its just my system.

 

 

Just finished installing and testing FTXG 1.30 and have zero issues, in combination with OpenLC/Regions and Airports. My FTXG insertion points are as they should be, with no need to make manual changes.

 

Did you have Open L/C or any other Orbx add-ons?  Di you uninstall the 1.2 and reinstall 1.3 or install over top? thx

Did you have Open L/C or any other Orbx add-ons?  Di you uninstall the 1.2 and reinstall 1.3 or install over top? thx

 

 

I have OpenLC all the currently available triple installer Regions for v2, along with a selection of FTX airfields.

 

I installed over the top of FTXG 1.20 setting FTX Central to Global with Hybrid un-ticked.

Did you have Open L/C or any other Orbx add-ons?  Di you uninstall the 1.2 and reinstall 1.3 or install over top? thx

 

I installed over the top - no problems

What I usually do, when looking at the size of overwrite installations, is simply a complete fresh install. Maybe I am just the odd one out, but I run a pretty lean P3D. I have the ability to be picky with my addons, and REX, Orbx, Majestic, Aerosoft, ASN, FSUIPC are pretty much the only things I have.

 

Complete reinstalls have always worked better for me. 

What I usually do, when looking at the size of overwrite installations, is simply a complete fresh install. Maybe I am just the odd one out, but I run a pretty lean P3D. I have the ability to be picky with my addons, and REX, Orbx, Majestic, Aerosoft, ASN, FSUIPC are pretty much the only things I have.

 

Complete reinstalls have always worked better for me. 

 

Same here. I always do a complete reinstall of P3D whenever there is an update and I also always only install the addons I actually use.

"Complete reinstalls"

 

Same here actually this is the first time I have tried it and worked great - but I had a very lean P3D install - otherwise I would have done a fresh install - as I only had global and vector installed was worth the try and made no difference

If you're careful and follow the instructions, the patches seem to work just as well as a full install.

 

This goes for both P3D and for all my add-ons (FTX Global, Vector, FS2010 mesh, all the NA regions, and several small Orbx airports (and all the freeware airport packs), NA AI Traffic, plus ASN, and 3 A2A aircraft, and a few misc add-ons).

 

I haven't done a full install since v.2.0 and P3D is running just fine for me.