Not had time for much simming over Christmas but flew over NY earlier with Samscene NY City Times installed and found I had tow Brooklyn Bridges.  I've been using Samscene for ages and never had this before.  Has something changed in MSFS?

Could someone try flyig over NY let me know if they have the same issue or whether it's just me?

If it's just me, I'm not sure what to do.  I've not added any recent scenery and changed nothing other that adding a new controller over the holiday period.  The version of Samscene I have is v1.5.1

I stopped using RK Bridgers scenery a long time ago.

I think I just answered my own question.  It looks like I had the msfs2020 verson of new york city times installed rather than the msfs2024 version.  Not sure how that happened.

Replaced the 2020 version with the 2024 version and still seeing 2 Brooklyn Bridges.  I thought that was going to fix the issue.  Anyone else seeing 2 bridges?

Do you have rkbridger NY bridges installed? 

Edit: forget about it. Saw you answered that already.

 

Edited January 3Jan 3 by Nemo

Ran MSFS2024 earlier with no addons other than the samscene new york (both 2020 and 2024 versions) and with each of them, I'm still seeing 2 Brooklyn bridges, so it's not another conflicting addon.  Can't figure out why this has only happened since Christmas unless ASOBO have updated anything for New York, but if nobody else is seeing it, I'm not quite sure what I can do, other than live with it.

 

What I'm seeing is clearly the ASOBO bridge and the Samscene bridge (The Samscene version is much more realistic btw).

It was fine before the holidays.

Edited January 3Jan 3 by cianpars

You're not alone. But now, since I know I also have two of them, it bugs me too ... 😉

8 minutes ago, Nemo said:

You're not alone. But now, since I know I also have two of them, it bugs me too ... 😉

Glad it's not just me then - I guess Asobo did something because it was fine before Christmas

I went now the other way. I disabled SamScene NYC and installed freshly purchased NYC bridges (rkbridger v 5.0). No double bridges. And honestly, I don't see much difference (if any) between Asobo NYC (PG) and SamScene NYC

Edited January 3Jan 3 by Nemo

Surprised that only 2 of us seem to have this issue.  Anyone else?  2 of us could suggest we have something wrong with our setups, but a few more might suggest that Asobo or Samscene need to provide a fix.

Yes, i have the same issue. Issue is caused by Samscene New York City Times. Not RK Bridges. Samscene messes up the brooklyn bridge. I am searching if they have a discord server, if so i will leave a message to them.

Update:

The issue with the Brooklyn Bridge in MSFS2024 caused by the New York City Times 2.2.0 scenery can be resolved by adjusting the scenery layer to the most bottom using the scenery layer tool. This should solve the problem of overlapping and duplicating bridges. Thank you for bringing this to our attention.

I have to check this out. I will report back asap.

Well, no luck. I moved the scenery all the way down. See picture

20 hours ago, bbking said:

Update:

The issue with the Brooklyn Bridge in MSFS2024 caused by the New York City Times 2.2.0 scenery can be resolved by adjusting the scenery layer to the most bottom using the scenery layer tool. This should solve the problem of overlapping and duplicating bridges. Thank you for bringing this to our attention.

I have to check this out. I will report back asap.

Didn't work for me either. 

Just another point on this - v1 is about 1.75 gb on disk and runs just fine.  v2 is about 16 gb on disk and uses up all of my 16 gb or vram, which is why I think I reverted from v2 to v1 in the first place.

It seems to me that Samscene need to fix the Brooklyn Bridge issue and also need to look at the size and vram usage of v2 from what I can see as there are still a lot of users who don't even have 16 gb or vram.

Good news folks - I have just completed a flight over NY this morning and we are back to one Brooklyn Bridge again.  As the Samscene scenery has not been updated, I assume that Asobo made an error around Xmas time and have now corrected it.  Hope it is OK for everyone else now.