|
An explanation of what happened: FG changed version number; specifically, we went from 3.7 to 2016.1.0. The version number is hardcoded in FlightGear as well as in FGData. Whenever the simulator is run, it checks whether those numbers match, so that you won't experience problems caused by incompatibilities between old FG versions/new FGData or vice versa.
In your case, you probably had an older nightly build installed/built (which had version 3.7 hardcoded in). By pulling yesterday's FGData, you pulled in the change in version number as well, so that FG will now - legitimately - refuse to start due to the mismatch. The latest nightly FG build on the build server should fix the problem.
|
|