On Dienstag 15 März 2005 22:10, Andy Ross wrote:
> Curtis L. Olson wrote:
> > The conversion between VCAS and VIAS is aircraft specific and is often
> > shown in a table in the POH (and depends on things like flap position.)
> > So FG can't come up with a nice tidy formula to convert between the t
> From: "Curtis L. Olson"
>
>
> 6. If we split out /velocites/airspeed-kt into
> /velocities/airspeed-vcas-kt and /velocities/airspeed-vias-kt are we
> going to break a lot of stuff?
>
This has been there so long I'd almost suggest depricating it and removing
airspeed-kt sometime in the dis
Curtis L. Olson wrote:
> The conversion between VCAS and VIAS is aircraft specific and is often
> shown in a table in the POH (and depends on things like flap position.)
> So FG can't come up with a nice tidy formula to convert between the two
> values. Thus FlightGear leaves everything as VCAS in
Would this be a valid way to explain away the problem:
The conversion between VCAS and VIAS is aircraft specific and is often
shown in a table in the POH (and depends on things like flap position.)
So FG can't come up with a nice tidy formula to convert between the two
values. Thus FlightGear
Curtis L. Olson wrote:
> 1. FlightGear has a property called /velocities/airspeed-kt; does anyone
> know if this was originally intended to be VCAS, VIAS, VTAS, or what?
>
> 2. The pitot system uses /velocities/airspeed-kt as it's input (and
> seems to assume this value is VIAS.)
This value looks
