Be Aware... POI status in My Library may effect underlying 3rd-party scenery

User Support Hub Scenery & Airports
, , , ,
1

Just a quick heads up to everybody, as I found this out the hard way through lots of troubleshooting, and perhaps it could help someone struggling with a scenery rendering issue of their own.

I recently installed Cli4D’s excellent Bora Bora Enhancement Mod for FS2024 (in SU5) and immediately noticed that most of the major hotels and their extensive overwater bungalows were not rendering. Many other assets of the mod were rendering perfectly well though, so it was really puzzling. Another user on the developers Discord channel confirmed he had the problem too.

After days of troubleshooting I finally discovered that that the “Oceania - Points of Interest” in the My Library tab in my MSFS2024 settings were disabled. After enabling them, all the Bora Bora hotels and their respective overwater bungalows popped in and rendered perfectly fine. I noted afterward that all of the missing hotels were under established POI’s, so that was clearly the issue. (Note: The Oceania POI in My Library said “MSFS2020” but it apparently ports over to the MSFS2024 POI’s.)

Oceania-POI's-Enable
Oceania-POI's-Enable1456×784 81.8 KB

Therefore, everyone who notices missing or corrupted parts of certain 3rd-party sceneries would be advised to check if it’s happening under or near an established POI, and then check that regions POI status in the My Library tab. Why the sim is coded to physically affect the underlying objects rather than just remove the pins, or whether this is the case with all regional POI’S or not I haven’t a clue, but it fixed my Bora Bora problem in Oceania for sure.

I happened upon the clue to check the regional POI status from a post about El Capitan in Cli4D’s Yosemite scenery having rendering issues: https://forums.flightsimulator.com/t/new-photogrammetry-el-capitan-being-overridden-by-handcrafted-poi-from-world-update-ii-usa/696136 ~ Curiously, in that case the user said he disabled - rather than enabled - the USA POI’s to remediate the problem.

Either way, if it helps anyone save the hours of troubleshooting I just went through - give it a shot - and see if it solves your particular scenery corruption issue.

2

Quick addendum to my post above:

Unfortunately, there’s another pesky issue when enabling or disabling miscellaneous FS2020 World Update POI’s. Depending on your situation it may be a lose-lose Catch 22 situation:

The issue is that FS2024 sometimes handles rendering POI “Objects” vs. POI “Geologic Assets” differently, depending on the situation. Case in point, with my issue with Cli4D’s Bora Bora mod, I can get the major hotels and overwater huts to render fine by enabling the Oceania POI’s, but then it corrupts his excellent work on Mount Otemanu, Bora Bora’s central peak. Disabling the Oceania POI’s puts the peak back to normal but the hotels and huts disappear again. The graphic below illustrates the issue:

POI-Issue-Graphic
POI-Issue-Graphic2000×1613 383 KB

This perhaps explains why the user at Yosemite (mentioned above) had success by turning the USA WU2 POI’s OFF. And in another forum post from May of 2025 a user pointed out the very same thing with the Navajo Bridge at Marble Canyon (an object) versus The Monument Valley buttes (a geologic feature).

That user’s report to Asobo only garnered 15 votes (mine is one of them), so it’s clear this problem only arises in a few places here and there. To be sure, all the other examples cited here involve either objects or geologic features that are officially flagged as “Points of Interest”. But if it’s a place you love to fly that has been carefully rendered by a 3rd party that has both objects and geologic enhancements that are also POI’s then obviously it’s a bummer to have to choose between one or the other if they’re exhibiting this kind of “Catch 22” conundrum for you. Luckily, the POI’s can be turned off or on without rebooting the sim but it’s still a PIA to have to choose between “seeing the hotel properly or the mountain”.

I haven’t had experimented with seeing if terrain flattening or TIN exclusions and the like might help circumvent the problem with geologic corruptions but if I find a way to circumvent the issue without disabling all the objects in a POI I’ll post it here.

3

Same thing goes for Moorea from Cli4D water Hunter not there BUT when you had the POI 2020 again they show up , was not able to spot if something else was wrong do

4

Okay, addendum to my addendum!

This may work for other issues with various POI packages, though I haven’t tested others, but for those with Cli4d’s Bora Bora Improvement mod who are experiencing the Catch-22 I outlined above, I found a way to get both the overwater huts and hotels to show as well as properly render Bora Bora’s central peak Mount Otemanu as the developer intended.

In short, downloading the streamed “Oceania POI” package and putting it in the community folder with Cli4D’s Bora Bora mod set to a higher priority seems to take care of the issue. But there are a few things that must be adhered to, so here is a more detailed breakdown of how I set it up…

Don’t be discouraged, it only takes a few minutes:

  1. Boot the sim, go to My Library, make sure “Oceania - Points of Interest” is enabled, and hit the “Download” button. Once downloaded it will prompt you that it’s “Ready to install”. Do so. When finished it will say “Installed” with a 6.32GB size.

  2. Now close the sim. Now you’ll need to COPY (not remove) the downloaded “microsoft-oceania-point-of-interest” folder (should be 6GB+ in size), to a temporary location outside the simulator, such as your desktop…

For my version (MS Store) and personal install of the sim, it was found at this location:

C:\Users(MyName)\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Official2020\OneStore

(Assumably, it downloaded to the “Official2020/OneStore” folder, as technically the Oceania POI package was an FS2020 release.)

  1. Now reboot the sim, go to My Library, and DISABLE the Oceania POI package. Note however, as it is no longer a “Streamed” package, you may have to check the “All” button at upper left to see it show up in the menu! Make sure you do this or what we’re about to do next won’t work.

  2. Close the sim again, and move your downloaded copy of the Oceania POI’s from its temporary location to the FS2024 Community folder.

Note: At this point, so far as the Sim knows, the POI package is disabled. But the downloaded package will now render like any other third-party scenery that’s in the community folder - HOWEVER - it’s important that Cli4D’s Bora Bora scenery has a Higher Scenery Priority! In FS2020 this was simply a matter of naming the package with an earlier alphabetic name. This sometimes works by default with FS2024 but not always…

Therefore:

  1. For good measure rename the “microsoft-oceania-point-of-interest” folder to something like “a-microsoft-oceania-point-of-interest” (assuming you haven’t renamed Cli4D’s Bora Bora package, i.e. “a” comes before “c” alphabetically). Then to be DOUBLY SURE that the Oceania POI’s have a lower priority than the Bora Bora package, reboot the sim, activate Dev Mode, and use the scenery reorder tool (at Tools>Scenery Reorder Tool") to ensure that the Bora Bora package is LOWER DOWN in the list (higher priority packages are at the bottom).

I forget whether I needed to reboot the Sim after changing this priority in Dev Mode or it just worked after the reorder, but if Mount Otemanu is still messed up after doing so just reboot the Sim again and you should be good.

It sounds like a lot of work when spelled out in steps like this, but it really just takes a few quick minutes to do! I can only assume the reason this works is because “streamed” packages may take priority over the Community folder or something. Your guess is as good as mine. In any case the Oceania POI package appears to still fully function in the sim.

Based on how this worked for me, perhaps this technique might also fix other Catch 22 conundrums with POI packages such as those with Navajo Bridge versus Monument Valley and El Capitan in Yosemite vs. Cli4D’s Yosemite package, etc. Basically, any third party that does a custom version of a feature that is already flagged as a custom POI for FS 2024 may exhibit these wonky rendering issues, and perhaps using this technique can overcome that.

I’ll be experimenting with those others and report back here if I have additional success.