Foreflight update breaks injection

[Viralwhite]

Reported it already to foreflight, but not sure if there is anything you can recommend in the meantime... after the most recent updates, if you try to turn on VATSIM traffic, it only shows you the live real world traffic. Foreflight acknowledged the problem but there is no ETA for a fix of course.

[jeffdamp-wave]

Did you try the GDL90 version of FS2FF?
https://github.com/jeffdamp-wave/fs2ff

[Viralwhite]

Thanks for that! That seemed to fix it. I was unaware of a GDL90 version since their website directs you to the other one. Thanks for the help with this!

[jeffdamp-wave]

I had done some work on this a while back to get FS2FF to work with more EFBs ended up emulating Stratus and Stratux hardware that use GDL90 over WiFi. Asten stopped having much time to maintain the primary branch. I think at one point we talked about merging my changes in here but never got around to it.

[vbazillio]

Thank you @jeffdamp-wave for all what you do! And thanks to @Viralwhite for raison the question. I was facing the same "issue" and activated GDL - based on this discussion - makes all my Say.intentions AI trafic injection reappearing!

[Dflight94]

Is there a setting I missed in the new update that gets rid of the crabbing effect of the aircraft in FF? I just installed the GDL update and my breadcrumbs are straight but the ship is crabbed.

[jeffdamp-wave]

I currently don't have an FF sub. Can you add a screenshot. How many degrees is it off? It did work way back when I tested it but things change. The app is converting what the simconnect lib is providing and packaging it into the standard GDL90 protocol. I'll fire up the sim to see if anything has changed

[Dflight94]

I currently don't have an FF sub. Can you add a screenshot. How many degrees is it off? It did work way back when I tested it but things change. The app is converting what the simconnect lib is providing and packaging it into the standard GDL90 protocol. I'll fire up the sim to see if anything has changed

Here is what it looks like on the FF side.

[Dflight94]

When I turned North, it got worse. Winds in this picture - xwind of 78kts and a head wind of 84kts.

[jeffdamp-wave]

Hmm ok. Looks like the planes actual heading from the AHARS packets are being used in FF. Im guessing a 0 X-wind means no grab? Ill see if Garmin does the same thing.

[Dflight94]

Hmm ok. Looks like the planes actual heading from the AHARS packets are being used in FF. Im guessing a 0 X-wind means no grab? Ill see if Garmin does the same thing.

Any updates on the issue?

[jeffdamp-wave]

Im leaning towards by design here. My 750 in my actual plane does the same thing. I think you are just used to using the xplane packets that does it wrong