Recent content by Brian

Hi, thanks for the report! Can you enumerate clearly what you are seeing. From what you've said, I'm going to translate into what I'm thinking you mean: 1. Instruments Mode - has overlap that isn't being fixed. Try "Map Mode => Customize => Select Layout => Reset Active Layout" (does it...

Still happening for you? If so, please Send Bug Report (Menu => About => Send Bug Report => Default file)

Are you still having all of these issues today? Or did some of them subside. v14.0.x is coming out soon, and I want to make sure it has your fixes in it. Can you "Send Bug Report" to us? (Advance Options => Send Bug Report)

Audio Voice Callouts is a version 14 feature -- soon to be released to production. So when you heard these, I'm guessing you were probably running a 14.0.x Beta version, before switching back to the v13.3.x production.

I'll be reverting this back to how it was -- showing "feet MSL" for the absolute traffic altitude. If someone then gripes, "hey where is my FL??" - then we can consider providing the flexible option of choosing the units. This will be changed back for the next beta, coming probably by end of...

This was my doing. During testing of heavy traffic ADSB replays, noticing the extra text on the screen. And noticed the inconsistency between relative altitude being in terms of "FL", while absolute altitude was raw 'feet'. Since ADSB traffic updating typically has delay, and there is also...

Thanks for the feedback! I've added tickets now for the following Windows-specific issues: 1. Consumes too much CPU when minimized! (currently we do not handle this at all, so run full tilt, targeting 30 FPS!) 2. Stability issues associated with minimizing and re-opening the window. Did I...

I've added this to my list for fixing in 13.3. Your selection should persist, as it used to.

We apologize for this mishap, I should have set the "Min iOS version" for our v13.0.30 release to "iOS 13+", and then those with these older devices simply would NOT have seen the update. The downside would have been, is that if you ever removed the app or had to do "App Restore (e.g. from...

I'm duplicating this symptom now on iFly EFB 12.3.3 -- and should have it fixed tonight for tomorrow's beta release. Looks like we might need to do an emergency patch release for all of our users, on 12.2.x

I also responded in other thread, and have added this thread link into our bug list to be fixed for iFly version 12.3/4.

BOTH ARE NOW FIXED -- for the first Beta release of 12.3 which due for release within a few weeks.

Added this to my short list: 1. 3 chars typed should show "Google" on Androd too. 2. Android "Back" button from search results should be same as "Cancel" not "Done/apply". You can expect these to be fixed for 12.3. Thank you for the detailed bug report!

Dynon Patch has been released here, ready for testing/validation: https://iflygps.com/AndroidAPK Install "DynonPatch-iFlyEFB-12.2.23.Android.apk". The main fix here is Auto-Detect was fixed. Without this fix it was partially working, instead of full-failure, which caused more confusion...

Hi Mike, thanks for the detailed bug report. It's possible (likely?) that when we added Avidyne support that we caused Dynon to break, in which case the fix should be easy. It's been several years since we touched Dynon code. This'll float to the top of my todo list, for the coming week...