On 20 Jan 2011, at 23:02, Jacob Burbach wrote: > Originally I had --fg-aircraft pointed to the top level aircraft > directory $HOME/FlightGear/Aircraft. However, though it found the > aircraft this way, I was getting permissions errors from aircraft that > made use of any IO methods such as loadxml. That was when I brought it > up on the list back in December and took away from that that I should > not specify $HOME/FlightGear/Aircraft, but $HOME/FlightGear. Perhaps > that was a miscommunication....but it did indeed work fine that way, > aircraft were loaded, no permissions errors...all good.
Okay, there was miscommunication here, apologies. > It was only recently I noticed that those aircraft are not found by > the MP code though, for whatever reason. Now from this discussion I'm > getting that I 'should' be passing my $HOME/FlightGear/Aircraft as I > had originally. And now that does work, mp finds them, and no > permissions errors. So if nothing has changed, I am really baffled > about that one. :) This the correct way, and it's good (and a big relief!) to hear that it does work with Nasal scripts and MP. Unfortunately, you shall indeed be baffled, because to my knowledge nothing has changed in terms of the committed code and data. I'm not 100% sure about this, but certainly 95% sure - I haven't changed the behaviour myself, and I haven't observed any commits that would obviously affect this - but I might have missed a Nasal change. James ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
