Flying west of Grand Junction, Colorado, going west down the Colorado River looks god-awful. Everywhere else too, rivers running up the sides of mountains. It’s looks terrible.
Wow, wth did they do? It looked great in the first shot.
There’s a screenshot challenge this week for Island Hopping … just saying.
This screenshot challenge sounds like bad joke considering the ugly coastlines.
Just another example where I really do not understand how something that obvious can slip any beta of an update. Are those guys at Asobo simply blind? Add this to the overdone icing visuals and you have no choice but wonder what the heck those guys do when testing their updates… Certainly not checking the visuals once, otherwise this is not explainable.
Seems like Microsoft with the entire team, resources, money is still capable of breaking things, and not so much fixing (not to mention quality checking preventing the breaking in the first place).
So an individual user must step in and fix it for them:
@mappamundi is the same guy who fixed the terrain spikes, for the spikes it was more like 0/1 binary fix for the entire world, for the shorelines in his own words:
“it’s far from perfect even within the limited area I cover and it’s a bit of sledgehammer type fix but IMO it’s better than the sledgehammer the algorithm change took to the coasts”.
It requires individual treatment for every mile of the shoreline, but @mappamundi is working on this.
Kudos to @mappamundi.
Shame to Microsoft (their status is started/backlog). The issue was introduced months ago with World Update 2 (USA).
Skyscrappers everywhere - broken by MS, fixed by user, only later by MS.
Trees distance issue - broken by MS, fixed by user, no fix from MS yet.
Terrain spikes - broken by MS, fixed by user, MS fix expected with World Update 3 (delayed twice already).
VR optimization settings - guide from user for Reverb G2 and Valve Index, no manual from MS (yet?).
Etc.
2 Likes
Thanks for the kudos. I certainly don’t intend to do every mile of shoreline on the planet, especially if an official fix may or not be coming this week. But will see what we get. If it takes as long to get a fix as it has to get the spikes resolved then I will look at making it an ongoing project and perhaps take requests for areas to fix. But anyways it’s been a useful learning process for me.
7 Likes
Big thanks from here too.
@Asobo/microsoft: Imho, you owe this guy (among others) a lot for doing all this work! For free!
I don’t know how difficult is to use your set of tools. Just in case I volunteer to join a project led by you to fix some shores in Scandinavia. I can devote ca. 16 h per month, don’t know how steep the learning curve is…
@mappamundi you Sir, deserve the community highest respect. To be honest i hope you’re some kind of rogue Asobo/Microsoft developer 
Italy Amalfi coastline, since i went there two years ago and know that it doesn’t have that cyan/blue coastline glitching uphill… 
Without and with the mappamundi fix, both with LOD set to 2.5 via config.
1 Like
Great that someone came up with a partial fix, but Asobo and Microsoft must address this issue because it is unaccettable to have this graphic glitches. This is in between Friday Harbour and Seattle…I mean…really?
3 Likes
Really hope this baked right in to the next update…but mappamundi, kudos to you sir!
Thanks for that, and for your work.
Hello,
I am flying over Patagonia and it’s the same problem …
According to the patch notes the frequency of this issue was reduced, probably not completely eliminated. Once it’s done downloading, could anyone check to see the extent of this improvement?
Quick check at TFFJ…
Some fixes, better watermasks… only they forgot to remove the boats… and clouds…
1 Like
Oh dear 