Hmmm ok.
You say Tongass as an Add-on. So then it is loaded directly by the sim. (No scenery.cfg entries).
In that case you must specify a Layer # for both the higher and lower to match your ORBX entries in the scenery.cfg.
In the xml for Tongass you have two add two layer lines- on for the Higher entry and one in the Lower entry in the xml to force it
in between the Orbx LC entries and the ORBX regions/airports.
The layer # is a count up from the bottom. (Always work bottom up, not top down!).
Here is my Tongass xml. I also use addon.xml to fire it up. (No entries in the scenery.cfg).
But when I fire Tongass, it fires up defined it in my xml: So my Tongass Lower piece goes in at level at 152, and higher goes next up at 153. (152/153 matches in my system). Again have to work bottom up from the bottom of the displayed scenery lib in your sim (or top down in the scenery.cfg)
-------------------------------------------------------------------------------------------------
Here is my Tongass addon.xml file:
<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
<AddOn.Name>Tongass Fjords X Scenery Package (FSADDON)</AddOn.Name>
<AddOn.Description>Tongass Fjords X Scenery Package (FSADDON).</AddOn.Description>
<AddOn.Component>
<Category>Scenery</Category>
<Path>Scenery\world\scenery</Path>
<Name>Tongass Fjords World Elevation</Name>
<Layer>6</Layer>
</AddOn.Component>
<AddOn.Component>
<Category>Texture</Category>
<Path>Scenery\world\texture</Path>
<Type>WORLD</Type>
</AddOn.Component>
<AddOn.Component>
<Category>Scenery</Category>
<Path>FSAddon\Tongass_Fjords\Tongass_Fjords_Lower_Priority</Path>
<Name>Tongass_Fjords_Lower_Priority</Name>
<Layer>152</Layer>
</AddOn.Component>
<AddOn.Component>
<Category>Scenery</Category>
<Path>FSAddon\Tongass_Fjords\Tongass_Fjords_Higher_Priority</Path>
<Name>Tongass_Fjords_Higher_Priority</Name>
<Layer>153</Layer>
</AddOn.Component>
<AddOn.Component>
<Category>Effects</Category>
<Path>Effects</Path>
</AddOn.Component>
<AddOn.Component>
<Category>Sound</Category>
<Path>Sound</Path>
</AddOn.Component>
<AddOn.Component>
<Category>SimObjects</Category>
<Path>SimObjects\Airplanes</Path>
</AddOn.Component>
<AddOn.Component>
<Category>SimObjects</Category>
<Path>SimObjects\Boats</Path>
</AddOn.Component>
<AddOn.Component>
<Category>SimObjects</Category>
<Path>SimObjects\Rotorcraft</Path>
</AddOn.Component>
</SimBase.Document>
---------------------------------------------------------------------------------------------------
So if you didn't have the <Layer>152</Layer> line in then the sim adds the add-on to the top. But for Tongass this is incorrect as it has to be positioned above the Orbx LC entries and below all of the ORBX Regions and Airports. Then the RTMM stuff sits on the extreme top of everything. That is the correct order for the correct layering.
All of this is a bit confusing but once you get all the pieces it can be figured out.
----------------------------------------------------------------------------------------
So add the layer lines in Tongass to determine the position where they will appear in the order. Create and Add a bottom Insertion " OpenLC add-ons bottom\scenery” folder and manually position it's entry in the scenery lib to be just above the Orbx LC. >> In Orbx Central, set the bottom Orbx insertion point. Orbx land class entries positioned below that OpenLC add-ons bottom\scenery” folder.
That OpenLC add-ons bottom\ entry helps you determine the exact layer for where Tongass should be defined to be placed. (Right above the OpenLC add-ons bottom\scenery folder).
When done the Tongass Layer lines and insertion points.. again, (and the 40 Tongass entries), that should fix up your order and layering problem.
(It takes a bit to figure out or diagnose what is happening without seeing it but hope now we have of the pieces exposed).
Keep posted on progress Peter.
---------------------------------------------------------------------------------------------
Anyways try it and if a no go or you get stuck - we can try to get together. We are not exactly just around the corner to be able for us to visit you being 11, 270 or so miles away and 13 hours difference, (You are GMT+8, I am GMT-5) but still I'm sure we can work it out using teamviewer remote (free)
https://www.teamviewer.com/en-us/ and I have voice comms that we can use at Discord. Link:
https://discord.gg/GD58ZdD also comms at Teamspeak. (But Discord is handier to send direct files if need be).
Norm