Speed carret
-
Issue is still not resolved
-
And maybe will not anytime soon as it is a minor issue (especially compared to some other things).
As long as you follow the carret you will be on TOS anyway. -
And maybe will not anytime soon as it is a minor issue (especially compared to some other things).
As long as you follow the carret you will be on TOS anyway.No, you often won’t depending on crosswind. I missed your earlier question (Are you able to respect the planned TOS (+/-10s) by following the caret until about 3Nm remaing distance to waypoint?)
Answer is no when using realistic weather maps with 70 - 100 knots of crosswind at altitude. The CAS carret goes up to non-achievable values 10’s of nm’s from the selected waypoint (on 100 - 200 nm legs).I suspect this is also the reason why AI flights often skip half of their waypoints when crosswind is present.
-
Please provide a video.
Even with a 80kts xwind I had no issue on my side . -
If you follow caret you’ll have caret slowly creep up over time. It’s asymptomatic passing the point. The math is a little complex but at some point it’ll run away to unachievable. When you notice it (say +5 knots) you’d have to exceed caret by a bit to maintain constant schedule or push it back down.
-
Please provide a video.
Even with a 80kts xwind I had no issue on my side .Don’t have video. It’s actually with head/tail wind, not so much with cross wind. Try with 85 kts head wind on a 100 nm leg with 410 kts planned ground speed and follow the CAS carret precisely. The CAS carret starts around 300 kts initially and keeps increasing until it becomes too high to follow around 20 nm from the next waypoint. Doesn’t make a very economical flight.
With tailwind the CAS carret behaviour is the other way around, it starts way too high and decreases throughout the leg.
Current workaround is to switch to GS and follow that carret but this isn’t practical.
Anyway, hope it will be solved sometime.
-
Grammar / spelling **** alert: I think the word you’re looking for is spelled “caret”. We now return to our regularly scheduled programme
All the best,
Uwe
EDIT: On 2nd thought maybe it should be renamed to “carrot” as it’s much like a carrot dangling from a stick in front of your nose when you try to follow it
-
Don’t have video. It’s actually with head/tail wind, not so much with cross wind. Try with 85 kts head wind on a 100 nm leg with 410 kts planned ground speed and follow the CAS carret precisely. The CAS carret starts around 300 kts initially and keeps increasing until it becomes too high to follow around 20 nm from the next waypoint. Doesn’t make a very economical flight.
With tailwind the CAS carret behaviour is the other way around, it starts way too high and decreases throughout the leg.
Current workaround is to switch to GS and follow that carret but this isn’t practical.
Anyway, hope it will be solved sometime.
In other words: The Speed Caret which is the symbol indicating the DED TOS Req Speed on the HUS’s speed scale is dependent to the HUD speed selector switch and should ALWAYS be calculated using the current total headwind component (which would make sense).
Please check if it is only the “Speed Caret” on HUD, or if the “Req Speed” in DED TOS page is also wrong/changing depending on HUD speed selector (?)
-
In other words: The Speed Caret which is the symbol indicating the DED TOS Req Speed on the HUS’s speed scale is dependent to the HUD speed selector switch and should ALWAYS be calculated using the current total headwind component (which would make sense).
Please check if it is only the “Speed Caret” on HUD, or if the “Req Speed” in DED TOS page is also wrong/changing depending on HUD speed selector (?)
The RQD GS indication on the DED is always correct. It’s only the carrets for the CAS and TAS that are wrong.
-
Already since 4.34 and the introduction of strong winds I’ve suspected that the behaviour of the speed carret is peculiar. When flying faster than the carret indicates, with constant altitude, velocity and (head)wind you should arrive earlier at the steerpoint than the pre-planned time. But somehow the carret manages to overtake the constantly maintained (faster than required) speed. How is this possible? If at one point you’re faster than the carret and nothing changes in earlier mentioned parameters you should always end up earlier at the steerpoint, right? I understand that the closer you get to a steerpoint, the larger the deviations, but the deviation should always remain on the same side of the carret when everything else remains constant.
Now I’ve found something even more interesting, when changing between CAS and GS the carret is below my current speed with CAS selected and above my current speed when GS is selected! How is this possible?
Related to this, since 4.34 the AI very often takes shortcuts from their original flight plan to arrive in time over the target.
thank you,
the bug has been identified and will be fix in 3 to 4 weeks
-
The RQD GS indication on the DED is always correct. It’s only the carrets for the CAS and TAS that are wrong.
actually it was also wrong by a little
-
-