Is it looking okay for you?

[Phil0671]

Just to make sure i´ve understood how the "customscenery" folder should be ordered .

 

Thanks.

 

scenery_packs.ini

[wolfko]

I currently only have the TE sceneries of WA, OR, FL and NoCal installed and below you see how my scnery_packs.ini looks like. The only idfference to yours is that I have the the single folders of each area put together in blocks (ABC, ABC, ABC,...) rather than have all the orhtos, all the overlays etc. put together (AAA...,BBB..., CCC,...). My order was automatically done by Orbx Central upon installing and it works perfectly. I have no idea though if your order will also work or not.

 

SCENERY_PACK Custom Scenery/Global Airports/
SCENERY_PACK Custom Scenery/Orbx_A_US_Oregon_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Oregon_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Oregon_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_A_US_NoCal_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_NoCal_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_NoCal_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_A_US_Washington_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Washington_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Washington_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_A_US_Florida_Airports/
SCENERY_PACK Custom Scenery/Orbx_A_US_Florida_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Florida_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Florida_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_OrbxlibsXP/

[Francisco Blas]

PHIL0671,

 

SCENERY_PACK Custom Scenery/03 Orbx_C_GB_Central_TrueEarth_Orthos/
SCENERY_PACK Custom Scenery/03 Orbx_C_GB_North_TrueEarth_Overlay/ <----- this is wrong? should be _Orthos/
SCENERY_PACK Custom Scenery/03 Orbx_C_GB_South_TrueEarth_Orthos/
SCENERY_PACK Custom Scenery/03 Orbx_C_US_Florida_TE_Orthos/
SCENERY_PACK Custom Scenery/03 Orbx_C_US_NoCal_TE_Orthos/
SCENERY_PACK Custom Scenery/03 Orbx_C_US_Oregon_TE_Orthos/
SCENERY_PACK Custom Scenery/03 Orbx_C_US_SoCal_TE_Orthos/
SCENERY_PACK Custom Scenery/03 Orbx_C_US_Washington_TE_Orthos/

 

Anyway, I would not manually change the Orbx names (for Orbx TE sceneries) and have them automatically named as wolfko has shown, most important as when you get updates to the scenery you won't have issues because of the renaming you did.

 

I use xorganizer to manage my sceneries. Orbx scenery is the only issue xorganizer has problems with but it can be easily fixed by manually ordering the Orbx scenery in the ABC convention.

 

fly safe
 

[Jon Clarke]

On 5/20/2020 at 2:09 PM, Phil0671 said:

Just to make sure i´ve understood how the "customscenery" folder should be ordered .

 

Thanks.

 

scenery_packs.ini 3.89 kB · 6 downloads

I have made a few adjustments to your scenery_packs.ini. I personally would not be making any name adjustments to the Orbx file folders, but I understand the logic shown in the prefix numbering you have adopted.

 I am a stickler for the correct layering sequence of the scenery_pack because so many anomalies reported by users are based on incorrect layering causing masking, image anomalies and even CTDs. The rules of the layering sequence are very simple and in general the Orbx Central installer does a good job. There are a couple of issues I have regarding where Orbx Central places a couple of  addons, but I keep that to myself

Using your scenery_pack as a guide here is the simple layering sequence in the .ini that will ensure you have an optimised setup with hopefully minimal errors pertaining to Orbx addons.

From top down:

1.ALL 3rd party payware and freeware airports 

2.Global Airports

3. London landmarks if you have TEGB South

4.ALL Orbx True Earth addons, preferably in the A/B/C/ sequence for each region but OK if you have grouped A's, B's & C's together as you have done.

5. Scenery enhancements like Simheaven VFR, X-Europe, SFD Global, CityScapes etc

6. Here is where I put all Libraries needed for non Orbx freeware airports mainly from x-plane.org website

7. Any Ortho4xp overlay files

8. Ortho4xp scenery image files

3rd party world wide mesh like HD Mesh UHD Mesh by airpilot and any Orbx mesh that comes with an airport and is prefixed with a ZZZ like:

ZZZ-Orbx_KBHB_Bar_Harbor

 

Hope the above clarifies for you.

scenery_packs.ini

[Phil0671]

Thanks @Jon Clarke for those clarifications.

 

So i have one more question. If i read your modifications i can see, for KEYW airport (2 folders : 01 Orbx_A_KEYW_KeyWestIntl/ & 01 Orbx_B_KEYW_KeyWestIntl_Overlay/).

 

You "keep them together" on top, above GLOBAL AIRPORTS, perfect

 

SCENERY_PACK Custom Scenery/01 Orbx_A_KEYW_KeyWestIntl/
SCENERY_PACK Custom Scenery/01 Orbx_B_KEYW_KeyWestIntl_Overlay/

 

But if we look at LOWI airport  that contains 5 folders ( 01 Orbx_A_LOWI_Innsbruck/, 01 Orbx_A_LOWI_LOJT/, 01 Orbx_B_LOWI_Overlay/, 01 Orbx_C_LOWI_DrapedOrthos/, 01 Orbx_D_LOWI_Orthos/)

 

You split it in 2, but for this one you put the folder "overlays" below TE folders. You don´t keep it on top like you´ve done for KEYW?

 

SCENERY_PACK Custom Scenery/00 LFRS Nantes/

 

SCENERY_PACK Custom Scenery/01 Orbx_A_EGFF_Cardiff/
SCENERY_PACK Custom Scenery/01 Orbx_A_EGHI_Southampton/
SCENERY_PACK Custom Scenery/01 Orbx_A_EGLC_LondonCity/
SCENERY_PACK Custom Scenery/01 Orbx_A_GB_South_TrueEarth_Airports/

 

SCENERY_PACK Custom Scenery/01 Orbx_A_KEYW_KeyWestIntl/
SCENERY_PACK Custom Scenery/01 Orbx_B_KEYW_KeyWestIntl_Overlay/

 

SCENERY_PACK Custom Scenery/01 Orbx_A_LFKX_Meribel_Airport/
SCENERY_PACK Custom Scenery/01 Orbx_A_LFLJ_Courchevel_Airport/
SCENERY_PACK Custom Scenery/01 Orbx_B_LFLJ_Courchevel_Mesh/

 

SCENERY_PACK Custom Scenery/01 Orbx_A_LOWI_Innsbruck/
SCENERY_PACK Custom Scenery/01 Orbx_A_LOWI_LOJT/

 

SCENERY_PACK Custom Scenery/01 Orbx_A_US_Florida_Airports/

 

SCENERY_PACK Custom Scenery/01 Orbx_A_US_SoCal_Airports/
SCENERY_PACK Custom Scenery/01 Orbx_EG20_Clench_Common_Field/
SCENERY_PACK Custom Scenery/01 Orbx_ENHA_A_Hamar_Flyplass/
SCENERY_PACK Custom Scenery/01 Orbx_ENOV_A_Orsta_Volda/
SCENERY_PACK Custom Scenery/01 Orbx_L52_A_Oceano_County/

 

SCENERY_PACK Custom Scenery/02 Global Airports/

 

SCENERY_PACK Custom Scenery/03 Orbx_A_GB_Central_TrueEarth_Custom/
SCENERY_PACK Custom Scenery/03 Orbx_A_GB_North_TrueEarth_Custom/
SCENERY_PACK Custom Scenery/03 Orbx_A_GB_South_TrueEarth_Custom/

SCENERY_PACK Custom Scenery/03 Orbx_A_US_Florida_TE_Custom/
SCENERY_PACK Custom Scenery/03 Orbx_A_US_NoCal_TE_Custom/
SCENERY_PACK Custom Scenery/03 Orbx_A_US_Oregon_TE_Custom/
SCENERY_PACK Custom Scenery/03 Orbx_A_US_SoCal_TE_Custom/
SCENERY_PACK Custom Scenery/03 Orbx_A_US_Washington_TE_Custom/

 

SCENERY_PACK Custom Scenery/03 Orbx_B_GB_Central_TrueEarth_Overlay/
SCENERY_PACK Custom Scenery/03 Orbx_B_GB_North_TrueEarth_Overlay/

SCENERY_PACK Custom Scenery/03 Orbx_C_GB_North_TrueEarth_Overlay/

SCENERY_PACK Custom Scenery/03 Orbx_B_GB_South_TrueEarth_Overlay/

SCENERY_PACK Custom Scenery/03 Orbx_B_US_Florida_TE_Overlay/
SCENERY_PACK Custom Scenery/03 Orbx_B_US_NoCal_TE_Overlay/
SCENERY_PACK Custom Scenery/03 Orbx_B_US_Oregon_TE_Overlay/
SCENERY_PACK Custom Scenery/03 Orbx_B_US_SoCal_TE_Overlay/
SCENERY_PACK Custom Scenery/03 Orbx_B_US_Washington_TE_Overlay/

 

SCENERY_PACK Custom Scenery/03 Orbx_C_GB_Central_TrueEarth_Orthos/
SCENERY_PACK Custom Scenery/03 Orbx_C_GB_South_TrueEarth_Orthos/
SCENERY_PACK Custom Scenery/03 Orbx_C_US_Florida_TE_Orthos/
SCENERY_PACK Custom Scenery/03 Orbx_C_US_NoCal_TE_Orthos/
SCENERY_PACK Custom Scenery/03 Orbx_C_US_Oregon_TE_Orthos/
SCENERY_PACK Custom Scenery/03 Orbx_C_US_SoCal_TE_Orthos/
SCENERY_PACK Custom Scenery/03 Orbx_C_US_Washington_TE_Orthos/

SCENERY_PACK Custom Scenery/03 Orbx_D_GB_North_TrueEarth_Orthos/

 

SCENERY_PACK Custom Scenery/01 Orbx_B_LOWI_Overlay/
SCENERY_PACK Custom Scenery/01 Orbx_C_LOWI_DrapedOrthos/
SCENERY_PACK Custom Scenery/01 Orbx_D_LOWI_Orthos/

 

Thanks

 

 

[Jon Clarke]

Yes.  Regarding LOWI that is what I do but it is not really necessary. LOWI is a unique addon in that it is an isolated scenery that doesn't fit into any TE addon.....yet. It is designed for sitting on top of default scenery and is enhanced with its own ortho for a limited surrounding area. It can be layered as a complete autonomous package i.e. grouped together above Global Airports but in my example I just followed the rule of only having the 2 airports above Global Airports. I don't believe that in this unique instance there is any adverse effect either way.

SCENERY_PACK Custom Scenery/01 Orbx_A_LOWI_Innsbruck/
SCENERY_PACK Custom Scenery/01 Orbx_A_LOWI_LOJT/

 

 

[Phil0671]

Thank you Sear