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


------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to