Honestly I am very disappointed with this update. You still stick to the OSM junk that causes such an error:
Already at that time MFSX tried to implement this OSM junk in and that failed because this junk is immature.
No idea what are you referring to. That we haven't yet fully implemented support for bridges, overpasses, or that there are occasional errors in road connections or that the lanes do not match? Some are errors in OSM but the larger part is our missing support for many features.
Anyway, you can turn off the roads in settings, world -> datasets if they bother you so much.
JSBSim and user friendly FM programming interface
Well, that's not going to happen. Why would we lose time on that if there already exists a tool that allows you to configure FDMs for JSBSim? We are making a world renderer/simulator and not a JSBSim flight sim, and JSBSim is just one simulation core used there as an
example. Even aircraft developers we talked to often want to use their own simulation engine with their models ...
If someone wants to develop an in-game UI for a FDM configurator - no problem, but I'm 99% certain it won't be us doing it, that would really be wasting our resources on something we don't have much experience with anyway.
Besides, it would be for all users have been much more useful than seeing these fully broken roads from OSM Scrap. Even hand-made roads look and feel much better still passable. It would also be more useful if you can save the made map parts to exchange it with the other users. This Personally, I find it much more useful than fumbling around with the OSM junk and hoping it will work out somehow. It works out not because the OSM data is scrap!
As for the rivers (especially Rhine, since I live there) I was positively surprised. Have the short piece (v. Mannheim to Koblenz) looked up and found it better than it was in the previous patch. Therefore, thank you very much!
Beware, you might be thanking OSM here!
Even if OSM data is often problematic, I don't see many usable options. Commercial navigation data costs are too high, manual coverage is insufficient. What MFSX tried and failed is fairly irrelevant.