On Sat, May 23, 2009 at 2:48 PM, Torsten Dreyer wrote:
> How about this?
>
> --metar="27012KT 2SM OVC1000 15/14 Q1001 NOSIG"
>
> It will set weather-scenario to METAR and disable real-weather-fetch.
>
> Needs just a little coding and gives some flexibility. But it probably is
> not
> very intuitiv
> 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 M
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 inte
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
> Trying to set up conditions for an IFR approach with the latest CVS
> code, I find that the following command line which used to do the trick
> a few years ago gives fine VFR weather:
>
> $ ./fgfs --disable-real-weather-fetch --enable-clouds --visibility=3000
> --ceiling=1000
>
> The visibility a
Trying to set up conditions for an IFR approach with the latest CVS
code, I find that the following command line which used to do the trick
a few years ago gives fine VFR weather:
$ ./fgfs --disable-real-weather-fetch --enable-clouds --visibility=3000
--ceiling=1000
The visibility and ceiling
6 matches
Mail list logo
