Hi James , I have one request (since you have write access) , could you
change that <has-barber-pole> option to <has-overspeed-indicator> ?
Dont know if that slang would be clear to everyone , but Im sure everyone
understands "overspeed".
If your planning on further changes , two facts seem to pop up consistently
while researching this :
1: overspeed needle always points to Mmo ... mach limit .
2: when the aircraft reaches that limit .. the overspeed and indicated
airspeed needles should be aligned .
Personally I think K. Hoercher's code worked well, without over-complicating
things , and the default
figures were there in case someone only enabled the <barberpole> without
options ....
260 ias seems to be a pretty common airspeed limit.
Thanks
On Tue, Mar 9, 2010 at 3:19 AM, James Turner <zakal...@mac.com> wrote:
>
> On 9 Mar 2010, at 09:18, James Turner wrote:
>
> >> Could someone take a look and commit please ?
> >
> > I'm testing these now, and will commit in a couple of moments.
>
> Committed now, with some changes:
>
> - I've switched the pressure-alt source to be configurable, instead of
> hard-coded; it defaults to /instruments/altimeter/pressure-alt-ft
> - the ias and mach limits are read each frame, so they could (potentially)
> be updated from Nasal
> - I've removed the default values for alt-threshold / ias-limit /
> mach-limit, on the assumption that anyone enabling the barber-pole will
> supply appropriate values. If people disagree with that, adding back the
> B1900 values (or similar) as default is easy.
>
> My biggest concern is that the code references /velocities/mach to compute
> the mach-limit, which seems undesirable - instruments should read/compute
> values based on physical properties if possible - that's certainly the
> philosophy of the basic instruments.
>
> Ideally, we would extend the airspeed indicator to compute Mach as
> described here:
>
> http://williams.best.vwh.net/avform.htm#Mach
>
> I know OAT is available trivially, which lets us compute CS (speed of
> sound) easily, but computing TAS from IAS is more complex, as the formulae
> show. If someone can explain the formuale in detail to me, I'd be happy to
> add a 'indicated-mach' property to the airspeed indicator code (effectively
> allowing it to be used as a mach-meter too), and then use that mach value
> for the mach-limit computation.
>
> Comments? I guess all the formulae required already exist elsewhere in the
> code.
>
> Regards,
> James
>
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
