Theres a bug in the GEA 24 software, so they pulled the update off the website. Should be fixed in a few days.

That would explain it.... I updated the day after it came out and now, when I come out of config mode, all my engine and ADHRS data flickers with Red Xs. A full reboot fixes it, but not something you want to see on the screen....

Anyone know how to get the AGL data? It doesn't appear to show up automatically.

Don't know for sure cause I don't have the update, but I expect it is one of the display "Data Bar" fields.

• Menu/Menu/Setup/Data Bar/Change
• Touch one of the data bar fields
• Touch a new data field from the list (in this case look for the AGL data field)

Looks like the current version is now 4.90. The link on the original post works now.

Correct, this is how AGL can be displayed, I just updated. Thank you Garmin.
Don't forget to re-pair your bluetooth devices after you upgrade.

I also updated a couple weeks ago, and was surprised to find my autopilot seemed to lose its gain settings. Either that or the updated servo software requires more gain than previous settings.

In any event I had to increase the AP gain for both roll and pitch after the update.

No big deal as they are easy enough to reset, but I have noted the settings this time and will check whenever another update is applied.

Does anybody know if finally the g3x software allows for vertical navigation (vnav) were the pilot sets the descent angle (e.g. 3 degrees) rather than the target fpm (as is in the g1000 and many other certified and non-certified efis)? This has been requested in other 2 vaf threads and g3xpert wrote he would look into it, but never came back afaik. At the moment, the way vnav in the g3x works is that the system fix the angle based on the speed of the plane around one minute before the top of descent, with no control and no visibility for the pilot of what this angle is (so no idea if the descent profile will clear terrain or obtacles, for example). In particular there is no way that the pilot can reproduce exactly the same descent angle to a waypoint on 2 different flights, despite setting the same fpm target on both flights