Content in MSFS 2024

[Spook]

I purchased Las Vegas for MSFS 2020 some time ago and have now transferred over to MSFS 2024. However, when I look in my library in 2024 I can see my “purchased” items, some say something like “transferred” and others say something like “not available” but the Vegas scenery does not appear to be listed at all.

Is this a problem with MSFS 2024 and it should be listed, even if “not available” or is this something else?

Many Thanks

[Brain]

Same issue here, only flytampa las Vegas city pack not showing in 2024 library list

[seeingeyegod]

Same problem. It's pretty frustrating since the stock 2024 Vegas is a big downgrade from 2020 with the addon.

[Ced24]

Hi!
I purchased KLAS through MSFS2020 Store. Any chance to see it in my MSFS2024 community soon?

[alclawson]

Same issue here. Purchased KLAS for 2020 through the Marketplace. I see all my other aircraft and scenery purchases listed and can "enable/disable" them, but Las Vegas is missing. Any recommendations?

[BurnedFireman]

Also have the same issue. There is suppose to be a work around to copy from MSFS2020 and paste into the MSFS2024 community folder.
I did this and MSFS2020 LAS Vegas from Fly Tampa now shows up, but is listed as unavailable and cannot be streamed or activated.

I reached out to MSFS2024 tech support and got a generic response that doesn't help at all. Also reached out to Fly Tampa and got no reply.
I paid $200+ for the full FS2024 version and I'm very unhappy with not having the custom KLAS.

[alclawson]

I can’t find the folder in 2020 to even try to copy over to 2024. Was it in your 2020 Community folder?

[BurnedFireman]

If you purchased and installed from the Microsoft Store:

locate MSFS2020 Folder:
C\Users\”USERNAME”\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore

Copy and paste into the MSFS2024 folder:
C:\Users\"USERNAME"\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community

I attempted the above and FlyTampa Las Vegas addon shows up as disabled.

[FlyingRagilein]

For me, the scenery now works fine in 2024. But I bought it from FlyTampa directly and simply copied it from the
2020 "Community" folder to the 2024 "Communitiy" folder. I also applied two additional fixes that are available
in my package "General Aviation Enhancement and MSFS 2024 Fix for FlyTampa Las Vegas" at flightsim.to

If there are activation problems, although you copied the scenery fom the OneStore folder to the Community folder, I suspect that
the Content Manager applies some knowledge about compatibility to the scenery.

So, I would try to break the link between this knowledge and the scenery.

Notice: All I write here is just my guess and it goes without saying, that you try everything on your own risk!

The first candidates for breaking the link would be to rename the scenery folder in the 2024 "Community" folder
from "flytampa-lasvegas-airport" to something like "flylasvegas-lasvegas-airport" and
to edit the file "manifest.json" within this folder by changing the two occurances of
"FlyTampa" to "FlyLasVegas"

Hope, this helps.

[Mets747]

For me, the scenery now works fine in 2024. But I bought it from FlyTampa directly and simply copied it from the
2020 "Community" folder to the 2024 "Communitiy" folder. I also applied two additional fixes that are available
in my package "General Aviation Enhancement and MSFS 2024 Fix for FlyTampa Las Vegas" at flightsim.to

If there are activation problems, although you copied the scenery fom the OneStore folder to the Community folder, I suspect that
the Content Manager applies some knowledge about compatibility to the scenery.

So, I would try to break the link between this knowledge and the scenery.

Notice: All I write here is just my guess and it goes without saying, that you try everything on your own risk!

The first candidates for breaking the link would be to rename the scenery folder in the 2024 "Community" folder
from "flytampa-lasvegas-airport" to something like "flylasvegas-lasvegas-airport" and
to edit the file "manifest.json" within this folder by changing the two occurances of
"FlyTampa" to "FlyLasVegas"

Hope, this helps.

Thank you so much for your mod to fix something that FlyTampa should have fixed ages ago. The scenery lights are still not perfect but at least I dont have massive triangles everywhere and I can use a good Vegas in 2024. I'm also really enjoying the other little enhancements you did in that package. Thanks and lets hope FT has an update coming. They literally do not respond on the forums here.

[FlyingRagilein]

Thanks for the feedback! They probably moved on and are doing something else now. Their Vegas scenery is still very, very good. So, we can try to make the best out of what we got. What further changes regarding the lighting would you like? Maybe I can improve something in a future update.

[Mets747]

Thanks for the feedback! They probably moved on and are doing something else now. Their Vegas scenery is still very, very good. So, we can try to make the best out of what we got. What further changes regarding the lighting would you like? Maybe I can improve something in a future update.

Not quite sure it is something you can do but the airport lights are like non existent. All you can see is the yellow caution lights near the runways. No Blue edge or green center line lights. I think that is a FT issue and compatibility issue thought. You can see what im talking about in this screenshot I took. Other than that it is the best we will get at the moment! Thanks!

[FlyingRagilein]

The lights are there. You should see them once you are on a taxiway. Those are weak lights. You won`t see them from a large distance. Maybe I`ll increase the visibility a bit in the next update.
I just got an idea how to do this realistically. But you still will not see them from across the field ;)

[FlyingRagilein]

BTW: Did you apply the City-Lights fix too? The casinos are still way too bright.