-------------------------------------------------- From: "James Turner" <zakal...@mac.com> Sent: Monday, August 02, 2010 11:46 PM To: "FlightGear developers discussions" <flightgear-devel@lists.sourceforge.net> Subject: [Flightgear-devel] Aircraft dirs (and noisy output atlog-level=info)
> I committed some code a few days ago, to change how aircraft data files > are loaded - if you're running the latest code, you may have noticed the > paths used for each data file are now logged. This is a transitional > feature - it will help if someone reports problems with particular data > files not being loaded; once the code has had sufficient testing, I'll > remove or downgrade the message. > > The good news is, FG now supports --fg-aircraft=some/path/;another/path > syntax for loading aircraft data; you should be able to place development > aircraft or similar outside data/Aircraft and have everything work as > expected (right now you still need to have an 'Aircraft' dir, so I > do: --fg-aircraft=/foo/my-aircraft, and then have > /foo/my-aircraft/Aircraft/MD-81/MD-81-set.xml, and so on). > > data/Aircraft is still checked as a location, too, of course - this keeps > generic Aircraft resources (such as the standard AP) and shared > instruments working, though these could also be located in a separate > dir - the code check the current aircraft's direction, then > the --fg-aircraft paths in order, and finally data/Aircraft. > > This will hopefully simplify life for aircraft developers, packagers and > release maintainers in the near future, but in the short term it would be > great if people could try the feature out, and report any issues or > problems. > > BTW, the more verbose logging of file paths does reveal some latent places > where a file was missing / not-found (including in the C172 effects files, > due to a confused path), but this fact was not previous reported. > > James I am using the new Aircraft dirs for my current development. It certainly is very useful. However now that I have my cockpit layout nearly sorted out I have come across a problem, which can be duplicated using the existing Lightning (I am using the Lighning as a template for my own model) as follows: Copy the Lightning aircraft into the directory defined by --fg-aircaft, and rename or delete the original in FGROOT. Set --aircraft=lightning in system.fgfsrc and run fgfs. All runs until I attempt Auto Engine Start from the Lightning Configuration menu, when fgfs crashes. If I restore the original Lightning aircraft directory in FGROOT, even after starting up fgfs, but before attempting the engine start, everything runs OK. Hope this give you enough to go on. Regards Alan ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
