Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ground speed incorrect with sim update 6. #53

Open
brucehumblehand opened this issue Oct 19, 2021 · 5 comments
Open

Ground speed incorrect with sim update 6. #53

brucehumblehand opened this issue Oct 19, 2021 · 5 comments

Comments

@brucehumblehand
Copy link

Hello.

Many thanks for FS2FF. I use it every day! With the latest update for MFS, I am seeing an incorrect ground speed in ForeFlight. The pop-up instrument bar at the bottom is showing roughly double what the sim is reporting. I’m using the Working Title G1000 NXi if that helps. The picture below is from a flight in the default Caravan doing a ground speed of approximately 180 knots. Hope this helps.
Screenshot 2021-10-19 at 17 52 19

@sh4d0wl3ss
Copy link

Seeing the same thing. GS of 179 in the C208B is shown as 347 on Foreflight.

@jeffdamp-wave
Copy link

jeffdamp-wave commented Nov 20, 2021

I thought is was in KPH but it is now in Knots and Garmin and FF take Meter/s so updated the code block again i.e. DetaSender.cs var data = string.Format(CultureInfo.InvariantCulture, "XGPS{0},{1:0.#####},{2:0.#####},{3:0.##},{4:0.###},{5:0.##}", SimId, p.Longitude, p.Latitude, p.Altitude, p.GroundTrack, (p.GroundSpeed * 0.514445)); // SimConnect is now reporting in Knots and not meters/s

@jeffdamp-wave
Copy link

Turns out this is Plane dependent. Some planes are reporting GS in meter/s and others are reporting in Knots. I updated my local version to have a checkbox in the settings that does this:

private async Task SimConnectPositionReceived(Position pos)
 {
     if (DataPositionEnabled && (pos.Latitude != 0d || pos.Longitude != 0d))
     {
         if(this.DataAdjustSpeed)
         {
             pos.GroundSpeed *= 0.5144447;
         }

         await _dataSender.Send(pos).ConfigureAwait(false);
     }
 }

@sh4d0wl3ss
Copy link

Hi Jeff,

This in a version that you'll post soon?

Thanks.

Turns out this is Plane dependent. Some planes are reporting GS in meter/s and others are reporting in Knots. I updated my local version to have a checkbox in the settings that does this:

private async Task SimConnectPositionReceived(Position pos)
 {
     if (DataPositionEnabled && (pos.Latitude != 0d || pos.Longitude != 0d))
     {
         if(this.DataAdjustSpeed)
         {
             pos.GroundSpeed *= 0.5144447;
         }

         await _dataSender.Send(pos).ConfigureAwait(false);
     }
 }

@jeffdamp-wave
Copy link

Hi Jeff,

This in a version that you'll post soon?

Thanks.

I would but I'm not a contributor to this repro so I can't push my branch to create a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants