What you might be seeing is tester’s bias where yes, the first time the plane approaches the object you see the lack of detail but once it’s loaded it gets cached and stays in the scenery. The next times you do a test it appears to work fine. The tester is looking at the big picture instead of the details or they weren’t paying attention to the object the first time they approached it or, even worse they merely began their test right next to it. Major POI’s need to be created with different LOD levels. We as users though need to understand that the more information a scene we’re flying into contains, the longer the load times are going to be for that scene. Seeing Devil’s Tower as a nice little bump from 10 miles away also means that the scenery directly around us at that 10 mile point needs to also contain some detail of a far away object. Hopefully Asobo will continue to add detail and stay honest with us about all of this.

1 Like

My guess is the promotional videos were made with multiple flights over the same POI to get it right. Once an object is loaded, I believe it stays loaded or at least resides in cache regardless of LOD factor.


I’ve tried different Cache Options and it’s always the same with these POI, they do not Render in until you’re on top of them. So no it’s not Tester Bias.


In my tests over London I noticed that crappy looking buildings got better after multiple flights over the same place even after I flew away from them and back. Objects that are loaded late do seem to remain so I assumed that was a cache thing. I’m just guessing here. Ultimately we need multiple LOD objects for major POI’s. All I’m talking about is how this may have got past the QA stage. Let’s say as a tester you have 30 objects to check off and some very short time frame to get done because your company has bragged about the release. The tester’s bias would be slewing very close to your object to begin your test instead of flying to it from 10 miles off which doing so over 30 objects would take up a huge amount of your time. If it remains in memory or cache it would cloud the results even if you flew away and back. I’m not excusing it. You should see how detailed the QA department of our software company gets. It almost seems ridiculous at times. Our product is extremely high quality but then again we aren’t selling to an audience of impatient gamers either. lol

Any tip on how to do this ourselves? Great work!

I have this issue on only one of my own imported objects. All other imported objects show up just fine, but one only pops in when I’m practically divebombing the building.

My xml only shows this:

?xml version=“1.0” ?
ModelInfo guid="{df4edded-554a-4880-4805-15f27a714f00}" version=“1.1”/>

It’s the big round building in the middle that draws only when close

I’ve reported this bug month ago both on forums and to zendesk and nothing was done about it. Not just that, but some POI’s have issue with shifting up and down depending on LOD.

Finally more people notice this issue, but Asobo doesn’t care to revisit all the landmarks to actaully fix them.

I’ve lost all hope that this will ever get addressed. It’s the main reason why I didn’t buy any in game addons and haven’t played MSFS in weeks.

It just takes away all the fun from exploring when suddenly landmarks (that are used for VFR flying btw), don’t load until you nearly crash into them.

I was gonna buy CRJ too just to have a nice plane to explore the world… now? Not so much. Asobo fixes the issue, I return and buy all the addons I want and they get profit along with third party devs… Asobo ignores this issue and I won’t bother with MSFS anymore. Simple.

@Jummivana Please do something. This bug has been plaguing the game since USA world update, and the more world updates they push, the more POI’s will release as broken, and the more they will have to revisit each World Update. They are going to stack each and every World Update with this bug until there’s thousands POI’s that are BROKEN. The more POI’s there are to fix, the more time they have to spend fixing them. It’s best to fix this bug now instead of letting it fester.

This is bad to ignore now because it will get WORSE.


@Jokabaku El Capitan only has 1 LOD level, but I see the scaling is 100.

Still happens.

Of course it will.

Anything with scaling with have this issue. But a scaling of 2 will hardly be noticed, while a scaling of 100, you will need to be 100 times closer for it to initially load.

Bump for visibility

In conclusion, which settings we have to chose for not having problems with the terrain charge?

This thread is about POI not Terrain Lods, there’s other threads for that.


I really think someone of the team should acknowledge this



However given my findings and the ones in this discussion, as well as my exchange with a dev, I’d suspect there is something indirectly related between the two issues but not for the same reasons.


CtpLucky8, I want to commend you for your posts. You don’t just whine about things. You deeply research the problems and offer solutions, try to educate folks. Asobo should hire you.


Today I suffered this again, this time at the Cliffs of Dover POI. I know I will suffer from this until those locations are fixed, but worth to gain some visibility.

So this wasn’t fixed in SU3, come on Asobo please fix these blatantly obvious errors, we’ve even given you the Solutions as to how to fix them.


Yeah, coming up quickly on almost 4 months since I reported the issue about the Devil’s Tower.

Please upvote the topic for visibility!