You guys may want to take a look here. This fine gent found the actual cause of the issue causing the spikes, and it’s bad terrain elevation files.
He used original files from an older, non-updated version of MSFS to create a mod that will revert the broken terrain back to pre-patch state with Asobo’s own files. And it should fix ALL the spike issues around the world, not just select areas that were manually patched up in these fixes posted above.
As I said before, Why should someone else in the flight sim community fix Asobo and Microsoft’s cockups. mappamundi who created this file and fix, did it for free and is not paid anything by Microsoft and Asobo. Maybe Microsoft should pay up.
Oh yes I agree totally with the community having an input, but not to fix major cockups after a 13.67Gb update. There are some seriously skilled folk which are creating jaw dropping FREEWARE addons for FS2020, and in some instances way better quality and detail than some payware addons which are out there on the market. I’d like to know what excuse Microsoft and Asobo have got for this major cockup.
It was happening a little before the last patch and now it is happening a lot more. I wonder if it is a Bing to Sim processing error that is happening either when they update the maps to the Scenery servers, or from the servers to us. Anyway, one of the biggest, and new bugs now… Back to FSX type issues.