In IF version 20.2 changes were made to the API (the application programming interface, which defines how third-party apps can interact with IF).
This was done to add 6DoF (6-gedrees-of-freedom) to several views so that SmoothTrack could be used for head tracking.
Because of these changes Shaky Cam has become more intense.
To correct this, some changes will have to be made to Shaky Cam’s sensitivity settings, which Epaga is planning on doing as soon as he gets the chance.
In the meantime, just turn Shaky Cam off.
Since the API changes were made, certain camera views have been moving slightly while banking the aircraft. This also is a known issue which has been reported in beta.
So sorry for the delay in responding, I’ve been very preoccupied with my other app SmoothTrack.
The repeating sound thing is of course an issue I’d like to fix (though it seems hard to reproduce).
IMPORTANT: If anyone gets the repeating sound issue, could you please send in the IF Log (in Settings)? Laura wants to look into whether the issue is on IF’s side or on IF-A’s side. Thanks!
Also VNAV has stopped working (again). IF’s API on this has changed in 20.2 and the old one doesn’t work any more, so I’m going to need to swap over to the new one to get IF-A’s VNAV working again. Planning on doing that soon(ish).
For anyone with the repeating sound issue (@JerseyAnt and others), thanks to the TIRELESS and AMAZING beta testers @Jan and @Jeno_Farkas, I was able to pinpoint what the issue was, it was a tricky little (dumb) bug having to do with reading in longer data from the IF API. I’m pretty sure I have it fixed and will hopefully be releasing an update soon that will fix it.
Note that this issue only happens on Android and in some areas while flying (probably where there are lots of airports nearby), so flying in more remote places should help until the fix is out :)
Given that VNAV for cruise is not coming in 20.2 would it be possible to integrate it into the android operating system?
Possible perhaps, but IF themselves will be adding to their VNAV function. VNAV is a TON of work so I’d hate to add it to Android only for it to soon after be available anyways in IF. Not planning on that at this point.
Thank you @epaga for the update. I did have to issue again on my last flight but I just kept turning the API connect on and off and finally it sorted itself out.
Thank you again for all your hard work I really love your apps. 🙂
Yes it does. There are two known issues that popped up right before release (everything was working up till then) - one is the shaky cam feature is too sensitive (just turn it off for now) and the second is the repeating “Captain, ready when you are” in some areas of the world (more serious, but only on Android and will have a fix soon)