11 minutes ago, SayAgain said:

No reply, but experiment per my video above where I moved SamScene3D to the bottom and it removed some of the issues like duplicate bridges.  Check my video (no monetized and I make zero income from it, any Ads you see have absolutely nothing to do with me, all YouTube) if you want to see where to put it using the MSFS Ordering Tool (hoping MS AddOn Linker gets update by dev to support SU4 new folders).

EDIT: video covers the LA area, but the ordering changes I made also address most of CA including SF/Bay Area.

 

Thanks for the quick reply. I viewed your YouTube video.  I have a few follow-up questions if you don't mind.

1. Do items on top of the Ordering Tool have priority and write over those at the bottom?
2. Any idea why items under the 1st column have an "Invalid" label (see screen cap below)?
3. Under the last column titled "Package name" in the Ordering tool, would you happen to know the "Bucket" name for the California Update?

You mentioned that moving your SamScene3D to the bottom removed some of the issues like duplicate bridges.  However, my SamScene3D-sightseeing-usamoderncity2 item is already towards the bottom of the list (I didn't move it) and I'm still getting the duplicate Bay Bridge in San Francisco. 😞


 

26 minutes ago, Matt Sdeel said:

Do items on top of the Ordering Tool have priority and write over those at the bottom?

No, the other way around, but there are also “exclusions” defined by the scenery designer and other specific settings which can muddy the waters.  I’m not sure why the but the process of scenery/add-on layering has been a mess since the scenery add-ons were a thing a few decades ago.

As far as “Invalid”, my understanding is the developer didn’t include a package_ordering_hint in the manifest.json file.  There are many different values that can be used:

Unfortunately I don’t know the specific package for the CU13 update as I didn’t do a before and after compare.  Possibly the Asobo-TravelBook entries but that’s really just a guess.  I do download and install CU13, I don’t stream it (well, PG is still streamed but the actual CU13 updates I don’t stream).  I am of course assuming you are using PG (photogrammetry)?

5 hours ago, SayAgain said:

No, the other way around, but there are also “exclusions” defined by the scenery designer and other specific settings which can muddy the waters.  I’m not sure why the but the process of scenery/add-on layering has been a mess since the scenery add-ons were a thing a few decades ago.

As far as “Invalid”, my understanding is the developer didn’t include a package_ordering_hint in the manifest.json file.  There are many different values that can be used:

 

Unfortunately I don’t know the specific package for the CU13 update as I didn’t do a before and after compare.  Possibly the Asobo-TravelBook entries but that’s really just a guess.  I do download and install CU13, I don’t stream it (well, PG is still streamed but the actual CU13 updates I don’t stream).  I am of course assuming you are using PG (photogrammetry)?

I did a quick scan of the list (there's probably 100's of items in the list for those not familiar with the tool) and found a line item that might be the item below. I tried moving the "*city3-tin" line item (see below) around a bit but it disappeared after moving it several times and the list does not have search functionality. I gave up.

1 hour ago, Matt Sdeel said:

it disappeared after moving it several times and the list does not have search functionality. I gave up.

Yeah, the tool is horrible, barely functional.  It likely it moved ‘somewhere’ in the list but you’ll have scroll to hunt for it.

See my other thread here:

 

45 minutes ago, SayAgain said:

Yeah, the tool is horrible, barely functional.  It likely it moved ‘somewhere’ in the list but you’ll have scroll to hunt for it.

See my other thread here:

 

Excellent write-up of the tool. 

It took some guessing, but I somehow managed to fix the double bridges by moving the SamScene3D scenery down the list as you suggested. Thank you. 

(But, It'll probably get screwed up if and when SamScene3D issues an official update.) 

The PG around San Fran is AWESOME!  

dd

10 minutes ago, Sky_Pilot071 said:

PG around San Fran

Did you really just call it “San Fran” … ugh, next you’ll be calling it “Frisco”! 😉

 

On 1/29/2026 at 1:11 AM, vbazillio said:

Some PoI's are invisible with MSFS2024 (only): https://forums.flightsimulator.com/t/handcrafted-griffith-observatory-poi-missing/755842 

Can add the Hollywood sign to the list of CU 13 issues...

Edited February 3Feb 3 by udidwht

The giant trees have nothing to fear, they aren't going away...

 

 

1 hour ago, Fielder said:

The giant trees have nothing to fear, they aren't going away...

 

 

Bijan Seasons Enhanced will rid those giant pesky trees.

1 hour ago, udidwht said:

Bijan Seasons Enhanced will rid those giant pesky trees.

Correct me if I'm wrong. Wanted to remove these awfully blocks of trees and been advised to buy the Bijan's addon. "But" when I looked at comparison screen shots, it seems that 3D trees are removed by an exclusion area which most of time covered and replaced photogrammetric buildings by autogen buildings. So, autogen buildings are back. Moreover, it's seems to be a very hand made process and not a automatic algorythm, so many 3D block trees are still there. 

Edited February 4Feb 4 by vbazillio

9 hours ago, udidwht said:

Can add the Hollywood sign to the list of CU 13 issues...

Someone in the linked description (status bug logged) mentionner the sign and other POI's. One replied that the Hollywood wasn't handcrafted in the stocked MSFS. Can't personaly remembered as I certainly have a freeware to do that, picked on flightsim.to

Source: https://forums.flightsimulator.com/t/handcrafted-griffith-observatory-poi-missing-in-fs2024/755842/6

Edited February 4Feb 4 by vbazillio

The sign did get an upgrade but still dismal...(at 3:01)

 

CU 13 installed no SS3D scenery...how on earth they let that slip by QA is mind boggling.

Edited February 4Feb 4 by udidwht

23 hours ago, SayAgain said:

Did you really just call it “San Fran” … ugh, next you’ll be calling it “Frisco”! 😉

 

Yea, I got the same attitude.  lol

dd