Version: 1.0.72.0
Frequency: Consistently
Severity: Low
Context: EDDB, VNLK, Everest Basecamp
Bug description:
New rivers with the “buffer” areas around them stand out like a sore thumb in the landscape and in other areas they cut through airports where there shouldn’t be any rivers of that size.
Attachments:
EDDB:
VNLK:
Everest Basecamp:
We have observed the same issue at our KLIA WMKK airport. There is excessive water in the base FS2024 scenery, in areas where there shouldn’t be water, and isn’t present in FS2020.
A workaround just tested, with adding a water exclusion poly to the affected areas (using FS2020), then testing in FS2024 community seems to solve the issue.
Not sure if the excessive water is ‘visual glitch’ that will be corrected later, but the water exclusion does produce the same results in 2020 and 2024, albeit a rather tedious exercise that may or may not be needed.
Looks like whoever was in charge of vector GIS data accidentally included all rivers/streams tagged as TUNNEL=YES in OSM.
EDDB as an example:
KLIA also had lots of streams that are partially tunnels. Those shouldn’t be visible and cutting through airports.
Upon further investigation in 1.0.88.0 it seems to be impossible to exclude those rivers. This is before the exclude:
And here is the result after drawing two exclude polygons around the airport. One for type=river, one for type=water.
Streams need lots of work before going into a simulator.
Those little rivers are simply awful, especially when they flow down from snowy mountains
Guess is both a limitation of the water shader and/or a wrong design choice: if you have no data about stream width, please… don’t render it!
Because otherwise it will look just fake
Or render it max 1meter wide (if the shader is capable), and without that large falloff that removes grass and snow
Hello everyone,
There has been a fix for this, server side, so it should no longer occur on the live build.
Regards,
Sylvain
Seems to have been fixed now indeed, thank you!
Hello, just a small update on this: it’s now fixed for me too. I did a small mistake with the exclude, I did exclude the “water”, but forgot to exclude the “rivers”. My apologies.
All good now ! 
All possible fixes have been pushed server side.
The remaining cases are to be considered “by design” and the result of the environment rendering changes on MSFS 2024.
Regards,
Sylvain
