Fresh FSX Install - Order Of Addon Installation

I have just freshly rs-installed FSX (w/ Acceleration) and am seeking help with determining the most reliable order of addon installation to ensure immediate and longer term conflicts.

Here are my addons ,,,

1. FreeMesh X 2.0
   
2. FTX Global
   
3. FTX PNG Holgermesh Papua New Guinea
   
4. FTX Portland Cityscape
   
5. UTX Canada 2.0
   
6. UTX USA 2.1
   
7. UTX TAC 2.0
   
8. FTX Regional Packages x2
   
9. FTX Airports x4
   
10. FlyTampa Airports x2
    
11. SimAddons Airports x5
    
12. GSX
    
13. Flightbeam Airport x1
    

Thank all in advance!

 

1. FreeMesh X 2.0
   
2. FTX Global
   
3. FTX PNG Holgermesh Papua New Guinea
   
4. FTX Portland Cityscape
   
5. UTX Canada 2.0
   
6. UTX USA 2.1
   
7. UTX TAC 2.0
   
8. FTX Regional Packages x2
   
9. FTX Airports x4
   
10. FlyTampa Airports x2
    
11. SimAddons Airports x5
    
12. GSX
    
13. Flightbeam Airport x1
    

In my personal opinion, the installation order doesn't matter.

What's important is the ultimate order of the scenery entries in scenery.cfg, to make some packages overrule others in the way they should.

A good document to read is https://flightsimeindhoven.com/2017/07/23/scenery-config-editor-in-practice/

It encourages to use SceneryConfigEditor (links in the above web page).

That said, this is how I would do it.

First : FreeMeshX. Install following their instructions and put their folders just above 1107 Base

Then: ORBX Global, followed by the 2 FTX regional packages and what's left of ORBX.

In FTX Central Settings, choose a correct Library Entry Point. IMO it should be just above the Accel Cities, just above Las Vegas.

Then, what's left, the other addon airports in no matter what order, and finally GSX.

Be aware: some airport addons can have multiple scenery entries.

If not automatic, they sould be added to the scenery database in the correct order. Follow the developer's destructions.

Let FSX rebuild the scenery on regular basis, and do tests with every step.

I skipped UTX, as I have no idea how UTX interacts with ORBX. Others may drop in on how to make them work together.

IMO Holgermesh PNG can be skipped when using FreeMeshX (but again, that's my opinion).

Wim

Hey Wim! Thanks for the detailed reply. It's very much appreciated.

Hopefully someone can advise about the UTX.

I am familiar with SceneryConfigEditor, but your link new and is worthy of a good thorough read.Looks pretty comprehensive.

After installing FTX Global and the three UTX Packages, this is what my scenery.cfg looks like (using SceneryConfigEditor).

The 4 four entries were inserted with FTX Global, the 25 following by UTX.

Referring to the link in Wim's post (#2) , the chart suggests a preferred order of priorities in the hierarchy of the scenery file. I have been following this structure according to the instructions.

Can anyone further suggest where to put the FTX entries (they I believe are landclass related and not Global?), the FTX libraries, and the proper location of the UTX entries?

Hi again,

1) Addon Scenery (now at 31) should always be topmost, at 1.

Scenery BGLs placed in Addon Scenery\scenery must be able to overrule everything.

2) The ORBX insertion point should not be ON TOP.

I'd place it where Addon Scenery is now.

So in FTX Central (on the start screen click the "Settings" button bottom left) :

Where it prompts for "FTX Entries should be inserted below:"

you point it to the scenery entry "UT Exclusions for Default Scenery" (now at 30).

"OpenLC Entries should be inserted below: FTX" is default and stays that way.

Click "Save" and exit FTX Central (or stay there to install additional ORBX stuff).

From now on, ORBX will enter additional packages at the chosen insertion point.

Also, UTX will now overrule ORBX in the regions you own (USA and Canada).

Without knowing/owning UTX, I have a good feeling about this.

Now you can continue installing the other airports, etc. They all go on top, above UTX.

Just remember to reposition "Addon Scenery" topmost after installing something.

Wim