On Fri, Jan 21, 2011 at 3:56 AM, James Turner wrote:
> Actually the search has *always* been recursive - for years, by the look of
> it. I use the same (refactored) code to support all aircraft dirs, both the
> default one in fg-data, and the additional ones. Obviously I didn't want to
> break
On 20 Jan 2011, at 23:47, Jacob Burbach wrote:
> Ok, that does raise another question then. In order for the 'wrong'
> method to work in any fashion, means you have to be recursively
> searching the path given by --fg-aircraft...right? Seems odd, and
> certainly serves to create ambiguity and con
Ok, that does raise another question then. In order for the 'wrong'
method to work in any fashion, means you have to be recursively
searching the path given by --fg-aircraft...right? Seems odd, and
certainly serves to create ambiguity and confusionso why are we
doing that? Would it not be much
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 loadx
On Thu, Jan 20, 2011 at 4:59 PM, James Turner wrote:
> Nothing has changed in this area for several months, so I'm confused what
> state your setup was/is in, that half works, but not completely.
Interesting. :)
Ok, so may layout is like so:
Top level aircraft directory, which contains individ
On 20 Jan 2011, at 17:22, Jacob Burbach wrote:
> Oh...but previously we had discussion (December?) in regards to IO
> permissions 'not' working if you used an Aircraft directory directly
> and had to use only a directory 'containing' an Aircraft directory.
> This must be a fairly recent change th
On Thu, Jan 20, 2011 at 6:22 PM, Jacob Burbach wrote:
> Oh...but previously we had discussion (December?) in regards to IO
> permissions 'not' working if you used an Aircraft directory directly
> and had to use only a directory 'containing' an Aircraft directory.
> This must be a fairly recent cha
On Thu, Jan 20, 2011 at 12:06 PM, James Turner wrote:
> That won't work, you need:
>
> --fg-aircraft set to $HOME/FlightGear/Aircraft
>
> (This changed half-way through the development of the --fg-aircraft feature,
> and I should add code to detect it and warn/fix this case, since it has
On 20 Jan 2011, at 16:58, Jacob Burbach wrote:
> Hmm, does not work here for me. Aircraft from outside FG_ROOT are not
> getting picked up with MP. I am using Ubuntu Linux, recent git build,
> and have --fg-aircraft set to $HOME/FlightGear which contains an
> Aircraft directory where the aircraft
On Thu, Jan 20, 2011 at 3:01 AM, ThorstenB wrote:
> It didn't work with MP initially - but that was fixed months ago. I'd been
> using this with MP a quite a lot afterwards. And I guess you're using a
> recent build, so it should work, though I haven't tested it in recent weeks.
> There is a missi
On Thu, Jan 20, 2011 at 4:56 AM, Jacob Burbach wrote:
> Was just playing around a bit on MP and noticed that aircraft located
> in directories specified with --fg-aircraft do not seem to get picked
> up by multiplayer. The pilot list shows them as aircraft not installed
> in the pilots list, and y
Was just playing around a bit on MP and noticed that aircraft located
in directories specified with --fg-aircraft do not seem to get picked
up by multiplayer. The pilot list shows them as aircraft not installed
in the pilots list, and you just get the good old yellow glider. Once
I copied or linked
12 matches
Mail list logo
