August 24, 20205 yr 1) There being no coherent transition between model data ( suposedly feed from Meteoblue ) and observation data ( METAR ) whose source we don't know for sure but could also be Meteoblue. In it's present state MFS is not providing overall acceptable accuracy / matching between METAR data for a given airfield and what the simulator "puts" there as real world weather... There can sometimes be acceptable matches at certain times and places, but most of the time there's mismatch between METAR and Temp, Wind, Visibility, Cloud cover, etc... as reflected in the sim; 2) There is no way to set prevailing visibility when manually setting weather, and there's no document that can at least give some clues on how that new "variable" called "aerosol density" can be used to set exact visibility values; 3) Apparently density altitude is not being modeled when for the same place and QNH, temperature is made to vary - I should say I didn't have the chance to test this! Of course it would be great to test with varying T / Td proportions, but I couldn't find a way to set Td either; 4) The new "local" turbulence / wind variability menu looks interesting in that it provides some way to set gust direction variation as well as speed, but there is no information on how to properly use that new menu. Edited August 24, 20205 yr by jcomm Flying gliders since 1980 Flightsimming since 1992 AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)
Archived
This topic is now archived and is closed to further replies.