On Fri, 2009-05-22 at 19:25 +0100, Dave wrote: > Torsten Dreyer wrote: > > Add --prop:/environment/weather-scenario=none to your command line and it > > works again. > > > > Background: the default weather-scenario is METAR and > > if --disable-real-weather-fetch, a fake, hard-coded METAR is interpreted > > which overrides the given options for visibility and ceiling. > > > > > > > > Hi Torsten, > > Thanks for the quick reply, that works and I can fly IFR now :-) > > However, when real weather is disabled and the user specifies weather > conditions on the command line, would it not make sense to incorporate > those into the fake METAR at startup? Since you say that this is a > fake, hard-coded METAR, I can't see what else this could break? > > Cheers - Dave
My first thought was specifying initial conditions in any of --disable-real-weather-fetch --visibility= --ceiling= should imply environment/weather-scenario=none However perhaps Dave's idea of generating a metar to match the specifications is better. Ron ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
