Both flights were done in conditions where ATIS broadcasted "visibility 10 kilometres" (that is 9999 on a european METAR...). 

It's hard to see how Asobo can win this one. Weather is a complex beast to simulate. I'm just happy if we have accurate cloud bases for starters.

On 11/22/2021 at 11:09 AM, sightseer said:

This video from Premier 1 Driver shows a range of weather including what a region of low visibility looks like when you fly above it.

The flight starts in great weather at KEGE Eagle CO and ends in rainy-ish weather at Dallas Love.  Its only a half hour and has a pretty little tune in the middle.  Grab some coffee and enjoy.

 

I do enjoy all of the Premier 1 Driver videos.  But if this same flight was performed in the same conditions in MSFS right now (using live weather), you wouldn't be able to see the end of the runway (let alone the mountains) shown in the title shot, as it would be a obscured by fog/haze.  I just did a flight in MSFS into and out of KBKL and could not see the Cleveland skyline, which is maybe a mile away.  While landing, the runway only became visible when I was less than 300 feet AGL.  This low level haze/fog seems to be present in certain areas regardless of the real-life weather and is present 100% of the time (at least during daylight hours). 

It's weird how regional this is.  I've done several flights practicing approaches recently in the Puget Sound area using live weather, where our weather has been a typical November mix of rain, low clouds, patchy fog and sun breaks, and I've been pretty impressed - except for some violent wx transitions which definitely need smoothing out.  But using real-time wx updates on Foreflight to plan approaches, I've found the sim to do a good job of fogging in the airports reporting low wx, and having clear areas where a report supports them.  Examples: 

It's notable that all this flying has been to sea level airports.  Given the bug of METAR cloud bases being interpreted as MSL instead of AGL, it makes sense that erroneous fog would be experienced at high elevation airports and hopefully that's an easy fix - they already have elevation data for every airport, so just a simple conversion to be done.  But if it's also happening incorrectly at low elevation airports (which to clarify, my pictures are not an example of; they're an example of correct conditions) then there's more going on.