fixed F16 and F18 in headwind, incorrect CAS value shown in the HUD by A LOT

[JCTherik]

The headwind component of airspeed seems to be calculated incorrectly when near the ground, or on the ground.

Strong wind will show it the best, in all the screenshots, there's ~90kn of headwind pretty much nose on, yet the huds of 16 and 18 show 175kn. That's almost double.

All airplanes are parked on the ground.

The airplane still behaves consistently with 90kn airspeed, ie. cannot rotate, but when forced to rotate by other means, can just barely hold nosewheel off the ground.

After takeoff, few hundred feet above the ground the airspeed seems correct, but the closer to the ground the more off it is.

The wind on the ground seems lower than the wind just barely few hundred feet up, and my guess is the HUD just calculates the airspeed with the wind value that's few hundred feet above, ignoring the fact that next to the ground, the airspeed is lower.

 

 

Having a correct airspeed indicated is absolutely crucial for flying, especially on takeoff and landing in strong winds.

Sure, 90kn wind is not realistic, but it seems to be off even at lower speeds.

 

Following are screenshots of HUDs with screenshots of F2 views, which seems to report correct values. Tomcat shows correct airspeed, included for reference.

 

EDIT, sorry for crap screenshots, i'll remake them

 

wrong-ias.trk

Edited May 1, 2023 by JCTherik
better screenshots

[JCTherik]

Same bug in both airplanes.

[JCTherik]

Any news on this?

[JCTherik]

Eeeh, I don't know what to say, really.

 

I'm talking about the IAS in the HUD being shown incorrectly on takeoff and landing, which is... kinda important...

I made sure to put an effort into this bug report, there is a description, screenshots and track replay, all together with a probable cause, and a description of expected behaviour.

 

It's been a month without any response. Is this being worked on or is it being ignored?

[draconus]

14 hours ago, JCTherik said:

It's been a month without any response. Is this being worked on or is it being ignored?

You did all well, thanks. You just can't demand a response, note, work reports or ETAs on fixes. Just report and move on, they assure us they do read bug reports.

We all have our favourite bugs listed to squash some day.

 

Edited May 31, 2023 by draconus

[JCTherik]

1 hour ago, draconus said:

they assure us they do read bug reports

 

I've read that too, but sometimes there are some bug reports that linger around for years, and are brought up again and again before being acknowledged. And since there's no [REPORTED] or [INVESTIGATING] here, I'm worried that it fell through the cracks.

I'm not asking for ETA, or progress report, just a little "Filed" reply, or [REPORTED] flair.

 

But anyway, if you say it's filed, it's filed, I'll leave it.

[draconus]

1 minute ago, JCTherik said:

if you say it's filed

I don't know that and didn't say it was for sure.

[razo+r]

Just ask @BIGNEWY if it's been reported yet or not...

[BIGNEWY]

investigating now, seems to be Marianas only? 

[BIGNEWY]

Thank you for the report @JCTherik please feel free to tag me or message me in the future if you think a bug has been over looked. 

I have reported to the dev team.

[JCTherik]

3 hours ago, BIGNEWY said:

please feel free to tag me or message

Will do next time,

thanks a lot!