I think this is a easy thing to change. Why are here so less votes. Please Asobo read this thread and revise this
Please Asobo Microsoft log this as bug!
With the perhaps surprisingly small number of votes, maybe weâll just need to hope that the âdigital twinâ work, for FS2024, will result in a better treatment of waterways, even if that might be more by luck than by design??
Some sleuthing on this has revealed that this is related to the Open Street Map data that was used to create the water masks. Where there are odd water features in sim correspond to the OSM data. Most water features have no width data, so I think a default width is applied. Often these water features in OSM are also miscoded as âstreamâ or âcanalâ instead of âintermittent streamâ which does not appear to get a water mask. Edits to OSM data do not, however, show up in sim. It looks like the data was pulled once, but never revisited. Hopefully a fresh pull gets done for FS2024 and the updates get applied.
If that is the case, then a relatively easy fix would be to default unknown widths to a far narrower value. Especially as you might expect that itâd probably be the smaller water courses that are less likely to have width data.
Swings and roundabouts i guess.
1 Like
The thread has got a feedback logged. Whatever this means? For me it is a bug what can be easily correct. Please log as bug!
1 Like
OP here, I learned the SDK and have worked tirelessly to exclude these streams but there are just too many. Unless Asobo changes the data or the way the sim interprets river vector data this is going to be a constant problem. I was at least able to fix most of Arizona. Donât even get me started on water covering photogrammetry bridges, marinas, docks and other random stuff.
1 Like