Hi:

I'm trying to understand how the scenery order in MSFS works.  Using the "Package Reorder Tool" in the sim, I see all my add-on scenery (located in the Community folder) is #0 followed by two navigraph entries (numbered #1 & #2).

As I'm understanding it, my add-ons should have a number higher then the navigraph entries.  OK, perfect.  BUT, I'm not having any issues/duplicate scenery.  So, do I still need to change the add-ons priority #, or just leave it as is?  If it ain't broke, don't fix it?

Thanks!

I'm more confused as ever about this, as I thought this was no longer an issue and was only pertinent to FSX and P3d addons.

14 hours ago, Dreamflight767 said:

As I'm understanding it, my add-ons should have a number higher then the navigraph entries.  OK, perfect.

No, you got that wrong. Your sceneries should have a lower priority number than the Navigraph entries. That's why they have priority 0 and Navigraph has 1 and 2. Unless you see a scenery with duplicate runways you don't have to mess with that. And in case you see one you should report it on the Navigraph forum and they fix it with an AIRAC revision as they have done for a couple of sceneries already. Navigraph HUB always correctly sets the priorities for Navigraph and you shouldn't change them. 

58 minutes ago, Rockliffe said:

I'm more confused as ever about this, as I thought this was no longer an issue and was only pertinent to FSX and P3d addons.

If you have a scenery folder that you want to take priority over an other... just add a Z or ZZ to the front of the name.  That way it gets read last and takes precedence.   Only do this if you have a conflict.

A real world scenario... I would like my LVFR KMIA payware scenery to take priority over my Samscene payware scenery.  So, I add a Z in front of the LVFR scenery folder name.  🙂

54 minutes ago, Bert Pieke said:

A real world scenario... I would like my LVFR KMIA payware scenery to take priority over my Samscene payware scenery.  So, I add a Z in front of the LVFR scenery folder name.

Ah, so that’s how that works…

1 hour ago, Bert Pieke said:

So, I add a Z in front of the LVFR scenery folder name.

Just tried this but the scenery didn’t show at all (in my addon community folder). Is there a step I’m missing?

15 minutes ago, scotchegg said:

Just tried this but the scenery didn’t show at all (in my addon community folder). Is there a step I’m missing?

What are you looking for, and where are you looking?

Do you own the item you are looking for... 😉

Edited December 10, 20232 yr by Bert Pieke

4 minutes ago, Bert Pieke said:

What are you looking for, and where are you looking?

Do you own the item you are looking for... 😉

Ha ha, yes I do. Not to worry, managed it using the scenery order tool in the experimental page. Didn’t work before but now, finally, I only have one Bank of America in Miami!

3 hours ago, Rockliffe said:

I'm more confused as ever about this, as I thought this was no longer an issue and was only pertinent to FSX and P3d addons.

Aye...if only. 

One niggling scenery order problem in MSFS is that the navigraph navdata gets arbitrarily and automatically put at the top of the priority order (highest scenery order number) any time you make a change to the scenery config, and there are a few sceneries that need to be above the navigraph data in order to get some add-on navaids to work (a prime example being FlyTampa's Las Vegas scenery, which requires it to be above the navigraph data to make their ILS glideslopes to rwys 26L/R to work properly).  So if you add or remove any scenery, including managing what's active with the add-on linker, or if you update the navigraph data, the scenery order gets rewritten with navigraph on top again.  Aggggggggravating.

1 hour ago, Bob Scott said:

Aye...if only. 

One niggling scenery order problem in MSFS is that the navigraph navdata gets arbitrarily and automatically put at the top of the priority order (highest scenery order number) any time you make a change to the scenery config, and there are a few sceneries that need to be above the navigraph data in order to get some add-on navaids to work (a prime example being FlyTampa's Las Vegas scenery, which requires it to be above the navigraph data to make their ILS glideslopes to rwys 26L/R to work properly).  So if you add or remove any scenery, including managing what's active with the add-on linker, or if you update the navigraph data, the scenery order gets rewritten with navigraph on top again.  Aggggggggravating.

You mean with Navigraph above the scenery the glideslopes to runways 26L/R don't work? 

Edit: Just found this posted today on the Navigraph forum, I think it's the same issue: https://forum.navigraph.com/t/klas-again-g-s-issue/14154

Edited December 11, 20232 yr by Alvega

7 hours ago, Alvega said:

No, you got that wrong. Your sceneries should have a lower priority number than the Navigraph entries. That's why they have priority 0 and Navigraph has 1 and 2. Unless you see a scenery with duplicate runways you don't have to mess with that. And in case you see one you should report it on the Navigraph forum and they fix it with an AIRAC revision as they have done for a couple of sceneries already. Navigraph HUB always correctly sets the priorities for Navigraph and you shouldn't change them. 

Oh.  Great.  Thanks!  I really appreciate that clear answer!

I'm still not 100% clear about how you do all this. Where is the library? I hear talk about 1 and 0 then I read earlier about using letters such as Z  Sorry if I sound dim. Is there a link to a visual tutorial about this somewhere?

46 minutes ago, Rockliffe said:

I'm still not 100% clear about how you do all this. Where is the library? I hear talk about 1 and 0 then I read earlier about using letters such as Z  Sorry if I sound dim. Is there a link to a visual tutorial about this somewhere?

There are two ways of doing it.  One is by manually re-naming / ordering the folders in the community folder.  The folders are loaded into MSFS from the community folder in alphabetical order, and with folders loaded last taking precedence (thus the Z- in front of folder names to give them a higher priority),  Basically, if they load last, they over-write any other conflicting data loaded earlier, so they take precedence.  It is possible to use X-, Y-, Z-, ZZ-, etc. to set your order, but normally a simple Z- in front of the folder name will set it to load last and take precedence.  I have never seen more than one clash. 

An example might be loading an improvement mod for an aircraft, and then loading a 'better cameras' file. The better cameras may need a Z- in front to load last, otherwise the standard cameras from the improvement mod would take precedence.
So load order would be the standard aircraft, then the improvement mod, then the cameras over the top of that. 

If the basic aircraft folder loaded last (say an aircraft from flightsim.to in the community folder), you would see its files would immediately over-write the improvement mod and camera files you dropped in there as well. 
The Official folder also loads before the community folder by the way (say for the default C-172), that is how the mod files work, by loading any mods over the top from the Community folder afterwards.

I use this method as it is easy to see your load order using Windows Explorer, and you can change things before going into MSFS.

The other way is to use the package reorder tool within MSFS.  I have never used this method.  This is where they use 0, 1, 2 etc.

Edited December 11, 20232 yr by bobcat999

26 minutes ago, bobcat999 said:

There are two ways of doing it.  ...

 

Thanks for the explanation, Rob. Like Howard, I had no idea about this.

1 hour ago, bobcat999 said:

There are two ways of doing it.  One is by manually re-naming / ordering the folders in the community folder.  The folders are loaded into MSFS from the community folder in alphabetical order, and with folders loaded last taking precedence (thus the Z- in front of folder names to give them a higher priority),  Basically, if they load last, they over-write any other conflicting data loaded earlier, so they take precedence.  It is possible to use X-, Y-, Z-, ZZ-, etc. to set your order, but normally a simple Z- in front of the folder name will set it to load last and take precedence.  I have never seen more than one clash. 

An example might be loading an improvement mod for an aircraft, and then loading a 'better cameras' file. The better cameras may need a Z- in front to load last, otherwise the standard cameras from the improvement mod would take precedence.
So load order would be the standard aircraft, then the improvement mod, then the cameras over the top of that. 

If the basic aircraft folder loaded last (say an aircraft from flightsim.to in the community folder), you would see its files would immediately over-write the improvement mod and camera files you dropped in there as well. 
The Official folder also loads before the community folder by the way (say for the default C-172), that is how the mod files work, by loading any mods over the top from the Community folder afterwards.

I use this method as it is easy to see your load order using Windows Explorer, and you can change things before going into MSFS.

The other way is to use the package reorder tool within MSFS.  I have never used this method.  This is where they use 0, 1, 2 etc.

HIGHLY APPRECIATED !!!! Thank's a lot for your valuable explanation; I'm relatively new to MSFS and this is very useful indeed 😉 .