David Megginson wrote:
> 
> I've committed the start of a new environment subsystem to the CVS.

Hi,

sorry, but I can't understand that. I don't know why you try to do
multiple work instead of working together and increasing the output.

Apart from the FDMs using the weather stuff (all the necessary
properties are already exported so that should be a no brainer) and a
cryptic "set-up" system everything's there.

- layerd winds
- world wide coverage
- layered temperature
- realistical air pressure (not that of the tables that can't take
tamperature into consideration)
- gusts (ok, there's some code missing here, but it should be easy to
add)
- "realtime" worldwide weather

So what's missing?
- METAR
- an easy menu that allows you to set the weather manually 

but if you write that anyway, why aren't you writing it for the existing
code?

> Otherwise, FlightGear still defaults to Christian's weather subsystem.
> I am designing the new subsystem to be simpler than Christian's but
> well integrated into the rest of the program.

The only integration that's missing are the FDMs. And those can use the
current exported properties easily.

>  Right now, it simply
> tracks winds and visibility for a single point, but soon I'll be
> adding temperature, variability (i.e. gusts and changing wind
> direction), air pressure, magnetic variation, cloud information, and
> possibly even humidity and precipitation.  

Have you thought about world wide coverage? Or at least as few stations?

Adding that and you are as complex as the WeatherDB.


CU,
Christian

--
The idea is to die young as late as possible.        -- Ashley Montague

Whoever that is/was; (c) by Douglas Adams would have been better...

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to