Yes, one would asume that, but it does not. You can get as close as you want, it stays blurry.
Its like its unloading the good scenery as soon as you get close. It even loads it in again once you’re far enough away. Quite the reverse what it should do.
Try emptying your rolling cache.
The old cached files may not be playing nice with the update.
Emptying or disabling your rolling cache might help. Maybe Bing update a patch there, the source data is pretty bad regardless.
Bing high detail
Zoomed out a detail level
This is what I get on those coordinates without rolling cache
I tried emptying cache and it had not effect. The sad thing is the graphics were excellent for the first month or two without a hit to performance on my high end system. But now the graphics are terrible.
I tried disabled rolling cache (deleted it and turned it off), BING and photogrammetry, all to no effect.
Its like MSFS has forgotten it had scenery there. Instead it loads this blob. It is for sure a Terrain LOD thing, as you can increase/decrease the circle of the blob by setting small LODs. I have set it to the minimum (10) so I can see where I am flying to.
After discussion I come to the conclusion the changed the slider on the terrain scenery to as what is allowed to be shown and when it is too low of a resolution you have this effect. I hope they change it back.
I just flew over Newcastle Australia, some photogrammetry issues there as well
The real mystery, why Newcastle and not Sydney?
My sim looks like this all the time with photography on, bing data on, sliders max and rolling cleared wired connection with 100mb down,
Also I fly in areas I know should have good ground textures. I know because my sim before the first sim update ever looked great in this exact location near Ireland west knock.
When gets the LOD fixed? The problem is here since day 1 and nothing has changed for me. 
I don’t know if it’s because it’s Sunday, but Azure seems to be throttling downloads to the point Asobo should add row boats to enjoy London instead of trying to fly over it…
My experience today touring the Thames, have to pause the game all the time waiting for the data to download. To start this is my internet (measured today, while testing)
Test one, pausing the game, waiting for the detail to show up
Even when fully resolved you still frequently get stuff like this
Test 2
More holes in the Thames, fully resolved scene (no more network activity)
Two more tests, sometimes it has a speed burst
Most of the time it just sits on its ■■■■ waiting for… ?
I tried creating a manual cache around the Thames but that just CTDs everytime I try to download. (CTDs on esitimating time to download, never downloads a thing. Tried a small area around Empire State to see if it was size or area releated, CTDs the same)
So pls, add rowboats, to enjoy London…
That test flight from london city to Heathrow downloaded 4.3 GiB of data btw. (In comparison LaGuardia to JFK straight past the Empire state building, no pausing, sucks in 6.7 GiB)
Edit: Small error in my comparison to NY. Checking my notes LaGuardia to JFK is ‘only’ 1.63 GiB of data. London is the new Benchmark king by far. My test flight today (with lots of pausing) following the Thames from London City to Heathrow, consumed 6.12 Gib! Manhattan is an island after all, London is much denser scenery. (It’s also a longer distance flight yet the last part to Heathrow has no PG data)
I don’t know if you’ve seen this, but it might offer some insight.
No, this isn’t an instructional on how to operate a rowboat, it does explain the CTD with the manual cache.
This thread deals with the performance issue.
Ah, strongly discouraged to use manual cache haha.
So the only option is to slowly move over the area with rolling cache enabled to cache the area, so you can then have a regular flight later without data throttling turning London into a nuclear wasteland 
So how do you move very slowly ? Do i use Active pause or “esc” ?
I think for the “tile healing” you will need the “active pause” feature.
But maybe regular “Pause” (ESC) might work also. Recently I have seen an (live traffic) aircraft fly behind the three main “ESC Pause” menu images. So it seems like even in Pause the game engine continues running.
But in “Active Pause” it is easier to watch the tiles heal.
Personally I did not test both procedures yet.
You can use any pause, the game keeps going regardless.
Active pause messes with your plane, least desirable but useful if you’re too fast on approach. Active pause, plane stays in place, wait for the speed to drop, unpause and land. It’s basically a cheat… Works for take off as well if you run out of room.
You can bind real pause in the options (Set Pause On, Set Pause Off), this will stop animating your plane but the world moves on including updating the scenery. That’s what I use to wait for the scenery to come in and take pictures with the drone. In this mode you can still make inputs to the plane (set flaps for example) which will be executed once you resume. The drone works in this pause mode, boats, traffic, weather, windmills all keep going.
Or you can press Y, slew mode. The game also keeps going in slew mode, but it’s rather disruptive to the plane. It’s a toggle and continues when you press it again but you can’t operate the drone, the view is locked in place and the plane systems get a jolt on resume.
I don’t think there is a real pause (freeze everything in place)
Yes, hit “esc”. Then again to return to the sim.
Btw you can also move slowly by halving or quartering the sim rate. (Bind Increase Sim Rate / Decrease Sim Rate in options). Each decrease halves the sim rate, each increase doubles it. 1/4th is the minimum, so basically you can fly at 20 knots over London in slow motion.
(Traffic and water/other animations still move at regular speed)
It works very well, London is looking glorious today
The amount of detail is amazing, it just needs time to get it all in
Are you sure there is photogrammetry in Newcastle? Not all cities even have it.
Newcastle, Australia, yep
Back for the daily checkup to see if this is fixed
I can assure you it won’t be fixed any time soon. They won’t even acknowledge the issue in last couple of Twitch streams. 
