Recent content by Cobra

Good idea--done!

Just start an email in whatever client you want, use the email address from a past bug report, write up your new bug report, and attach the relevant log from the C:\_iFlyGPS_Data\User\#Logs folder. It won't have all the auto-populated data in the message body, but I think a lot of that is...

That's really a Windows thing, not an iFly thing. I've never bothered trying to set it up so that GMail is the default mail app, but there are various instructions on the web that supposedly work. If iFly is auto-generating an Outlook message, then it should be short work to just copy/paste...

https://adventurepilot.community.forum/threads/sticky-how-to-submit-a-bug-report-from-within-the-ifly-efb-app.26/

Menu > Setup > Alerts and Warnings > Traffic Alerts > Show Relative Altitudes

No, that's not an IFR thing. If you land (either VFR or IFR) at a big airport with a lot of runways and taxiways, the taxi instructions might be somewhat involved. MDreger's just trying to suggest a way that iFly could help with that.

I think the problem with that idea is that there is no data source iFly could consume that has the taxiways defined in such a way that iFly could know what taxiways exist and where they are physically located. There are airport diagrams in the Chart Supplement (A/FD), but they're just images...

There is no iFly setting for turning wi-fi on or off.

Adventure Pilot doesn't usually post publicly about which features they're working on or when they'll become available in iFly, for the same reasons Garmin and FF don't: Trade secret / competitive advantage, the risk of userbase disappointment if priorities change and features are...

Maybe a bug report, and include that screenshot?

Tap the airport on the map to bring up the QuickView popup: Make sure the "APT" tab is selected (top-right corner of the QV popup). Tap "Airport Info" (lower left). You'll get a page that looks like this (note NOTAMs in the middle): Tap the [MORE] button (if present) to get a scrollable...

The engineer in me recoils at the idea of "exact" readouts, because it implies a level of precision that simply does not exist. Many ADSB-out devices are only outputting altitude to the nearest 100'. Even for those that are outputting to the nearest foot, by the time that data gets to you it...

https://adventurepilot.community.forum/threads/sticky-how-to-submit-a-bug-report-from-within-the-ifly-efb-app.26/

Yes, this is a known problem. You can read all about it here (or just go to the last post in the thread to see that it's already been reported for the version you're using): https://adventurepilot.community.forum/threads/version-13-for-windows.624/ It never hurts to submit a bug report even...

If you want a definitive answer, I'd suggest calling Adventure Pilot's Support line during normal business hours. From: https://adventurepilot.community.forum/threads/sticky-welcome-when-asking-questions-please-help-us-help-you.27/