I just updated the files on our download server. There have been minor changes:

- The METAR download URLs have been changed to the working servers as described in this forum.- The FGCOM binaries has been updated to the latest version.- A small detail in multiplayer communication protocol has been changed as work around for a bug in FGFS. The FGFS bug has been fixed in the source code. So it might be not that problematic anymore. This issue caused, that latest FGFS instances crashed as soon as they came into MP range of a OpenRadar or ATCPie instance.

The Airport Download Server (Error 500) is still down, but I contacted the admin and he will fix it soon.

So if you have updated the METAR URLs yourself, I see no reason to update...

wagnerw wrote in Sat Jan 21, 2017 8:44 am:- A small detail in multiplayer communication protocol has been changed as work around for a bug in FGFS. The FGFS bug has been fixed in the source code. So it might be not that problematic anymore. This issue caused, that latest FGFS instances crashed as soon as they came into MP range of a OpenRadar or ATCPie instance.

This issue was discovered by Guy, and finally he also confirmed that my theory about is was true. Thanks Guy!!!

My workaround was to fill a value in the multiplayer protocol that I did not know with something different from zero. This value tells other FGFS instances how often you send updates about your position. So they can interpolate your position and orientation in space a lot better.I did not know what it was for and as OpenRadar does not change its position / orientation I sent out a zero... for years without problems...

Here is the explanation by the FGFS developer who fixed it on their side. It seems as my workaround did not help in all cases, but anyway, this was seemingly a new bug on the other side.

I think I finally figured this one out. The problem wass initializing anSGVec[234] class with a vlaue of 0. So changing dt fixed this for thisparticular case but not for all. The fix is in git now (and did notaffect previous stable versions of FlightGear).

<https://sourceforge.net/p/flightgear/codetickets/1927/>

As long as we are able to find and fix issues that fast, I am happy. Thanks to everybody involved!