James Turner <ja...@bugless.co.uk> writes: >> 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?
i noticed something even stranger. for me, if the aircraft file matches the directory name then i can load it using --aircraft=<aircraft> syntax (tried it with f16, f-14b, b1900d and some others). if it doesn't (p61 and x35) then i get: Cannot find specified aircraft: p61 Config option parsing failed ... i tried it with and without a .fgfsrc file with the same results. this is with the latest from git. --alex-- -- | I believe the moment is at hand when, by a paranoiac and active | | advance of the mind, it will be possible (simultaneously with | | automatism and other passive states) to systematize confusion | | and thus to help to discredit completely the world of reality. | ------------------------------------------------------------------------------ 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
