However, these values are interpolated (and thus overwritten) constantly. I think these need to be written to the /environment/config/... tree for all the boundary and aloft layers. Then when the environment manager reinit() is called these values will be loaded into the internal structures which are used for interpolation.
Yes, it needs to be cleaned up and properly documented. The idea is that you can have an environment manager that sets the values under /environment as you fly. The hard-coded manager right now uses the /environment/config values; I assume (though I haven't checked) that the METAR support uses its own environment manager and disables the current one -- in that case, the values under /environment/config would be ignored.
If, on the other hand, the METAR support is not a manager itself but simply a way of initializing the current manager, then disregard what I just wrote; in that case, the values under /environment/config are significant.
Also, the code will *need* to take into account the weather station elevation when it sets the temp and pressure.
In a METAR, the altimeter setting is adjusted to sea level, while the temperature is the actual temperature at station elevation. Use the properties temperature-degC and pressure-sea-level-degC (wherever appropriate in the tree under /environment) and things should take care of themselves.
All the best,
David
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
