On 19 Jul 2010, at 21:04, Lance Levsen wrote:

> Same, same. Sorry. :) I have a .fgfsrc which sets the b1900d as
> default. However, I also specified it on the cmdline.
> 
> dante:~$ fgfs --show-aircraft
> Cannot find specified aircraft: b1900d
> Config option parsing failed ...
> 
> dante:~$ fgfs --aircraft=b1900d
> Cannot find specified aircraft: b1900d
> Config option parsing failed ...
> 
> dante:~$ fgfs --aircraft=777-200ER
> Cannot find specified aircraft: 777-200ER
> Config option parsing failed ...
> 
> dante:~$ fgfs --help
> Cannot find specified aircraft: b1900d
> Config option parsing failed ...
> 
> All options command line options fail in the same way. (That's a
> little worrying actually.)

Unfortunately that's due to how the --aircraft option is parsed - *before* most 
of the config files are loaded.

You're on Unix, I infer from the paths you posted earlier ... hmm. Can you 
email me your .fgfsrc?

James


------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to