> Quoting Martin Spott :
> > Frederic Bouvier wrote:
> > > Martin Spott wrote :
> > >>This is what I meant: I run FlightGear and it actually reads most of
> > >>the values in my manually written 'system.fgfsrc', except a single one
> > >>(as far as I can tell), which is the aircraft to use. I've already
> > >>moved the "--aircraft="-clause to different positions but this didn't
> > >>make any difference.
> > > From the beginning, fgrun was starting fgfs with 2 command line
> > > : --fg-root and --aircraft because you need the first to find
> > > system.fgfsrc and the second because it was not used in this file.
> > I never talked about 'fgrun', I am talking about FlightGear itself,
> > alias 'fgfs.exe'. How do I manage to let FlightGear on Windows read the
> > aircraft name from the 'system.fgfsrc' ? Is the use of 'system.fgfsrc'
> > still a 'supported' option with FlightGear on Windows ? If yes, then I
> > think FlightGear on Windows simply has a bug because it ignores the
> > aircraft name. If not, is there an official replacement for this
> > configuration file ?
> I was just writting about my experience on the problem, and this is not a
> issue, although I silently worked around. But are you sure it is specific
> windows ?
Same under Cygwin - it's been like it for as long as I can remember - I
thought it was a feature not a bug, and have lived with it.
Flightgear-devel mailing list