Posted this on discord but got no attention there so just wanted to highlight it here.
In addition to the poor LOC tracking that you are attending to in the incoming update (thank you), the same happens when navigating with the GPS, where the aircraft can't remain on the proper course and drifts either left or right of the course and then flies offset. It never does regain the correct course.
Have not tried tracking a VOR radial but would suspect it happens there too.

INS navigation tracks perfectly from what I have seen.

Not sure if it's going to be fixed when the ILS tracking is fixed so posting just in case.

Edited April 4Apr 4 by atcogl

Bump

Hi, sorry the discord can get very crowded quickly so I appreciate you making a follow-up post here. The GPS is entirely WT Code, we just provide the physical system electrical power in the sim to the GNS unit itself. I'll ask the team about it in case there is something else I might be missing. Thank you

In addition to other AP Guidance changes, we are reviewing the AP Mode again just to make sure. Thank you

15 hours ago, IniJamir said:

Hi, sorry the discord can get very crowded quickly so I appreciate you making a follow-up post here. The GPS is entirely WT Code, we just provide the physical system electrical power in the sim to the GNS unit itself. I'll ask the team about it in case there is something else I might be missing. Thank you

Hey Jamir, no problem I know you guys have a lot going on after a new release.
I don't believe its related to the GNS as such, the aircraft navigates along the route, the waypoints sequence properly, it all works fine, except the track is always just a little offset, a half dot or so and it will wander both left and right of course. It's exactly like the localiser tracking issue where the aircraft sort of tracks the localiser but never fully captures and flies parallel to it. This is exactly what it does in GPS mode as well. It flies along the track, just not right on it.

@IniJamir Hi Jamir, just wanted to follow up that after a few flights in 1.0.1 this issue appears to be fixed, so you can close this one up now.
Thanks

Glad to hear it, thank you 🙂