Course is modulo 360. The bug was that the modulo operation worked on double precision, while the GPS wanted a single precision input. So it was possible to get a number close to 360 that was not being touched by the modulo, since it squeezed below 360 as a double, but with less precision it looked like 360.

It’s a master of disguise. 🙂

Oh crikey, I’ve never noticed that button! Sorry!

But it would make support a bit more difficult: Is the problem in the distributed version of X-Plane, or is it in the airport fetched from the gateway? Personaly I’d prefer a solution where “some” (could be a few thousands) airports are distributed with X-Plane, while the user has the option to add more airports from the gateway, or “overlay” the distributed airports with more recent ones (meaning both versions would be in different files with the option to revert to the distributed version).

I don’t think “rc” vs. “beta” is very useful. I don’t know if it’s possible, but “revert to last version installed” seems more useful to me.
As an alternative “early beta” vs. “beta” could make sense. In the former case you would be offered to update to the beta as soon as it’s available, while in the latter case the offer would be presented if the same beta is available for (let’s say) at least 48 hours.

In Windows it’s also available when hovering over the exe file in Explorer, or if you view details after pressing the right mouse button over the executable.

We like this idea a lot – it’s on the roadmap. We just haven’t had time to code it yet. This would allow the community to update airports more frequently.

It’s already in the about box – click “about x-plane” from the general settings menu.

You could have an “RC” option available in steam as well as “beta”, which might help this.

Also, could I request that the current version is visible in the sim under a menu or window somewhere? If you happen to miss the version number shown on the loading splash screen then I think the only other way currently is to open the log file…