I think what kind of through me off was that the aircraft loads either
way you give it the path. Except in the case of giving it an Aircraft
directory directly as I was doing, and for aircraft that make use of
IO functions in nasal, I would get lots of permissions errors and
aircraft would be missi
On 1 Dec 2010, at 16:44, Jacob Burbach wrote:
> Apologies, looks to be a misunderstanding on my part. I was putting
> `--fg-aircraft=/some/path/Aircraft', when it seems I should have just
> been putting `--fg-aircraft=/some/path'. Using the latter and
> permissions work properly, the former needs
Apologies, looks to be a misunderstanding on my part. I was putting
`--fg-aircraft=/some/path/Aircraft', when it seems I should have just
been putting `--fg-aircraft=/some/path'. Using the latter and
permissions work properly, the former needs the path in IOrules and
then it will also work apparent
It seems to work fine here without any additional changes , but I only
have one aircraft in that folder at the moment
On Wed, Dec 1, 2010 at 2:36 AM, James Turner wrote:
>
> On 1 Dec 2010, at 08:45, James Turner wrote:
>
>> This is supposed to be automatic - I updated the code in Nasal that sets
On 1 Dec 2010, at 08:45, James Turner wrote:
> This is supposed to be automatic - I updated the code in Nasal that sets up
> the IORules, so each additional aircraft directions should be on the
> read-allowed list. Of course, it's entirely possible I didn't get this 100%
> correct - it's awkwa
On 1 Dec 2010, at 03:54, Jacob Burbach wrote:
> I also needed to add an entry in Nasal/IOrules to allow reading in my
> custom aircraft directories when using this in order for most aircraft
> to load properly. This should be changed imho as IOrules has a READ
> entry for $FG_AIRCRAFT/* already,
I also needed to add an entry in Nasal/IOrules to allow reading in my
custom aircraft directories when using this in order for most aircraft
to load properly. This should be changed imho as IOrules has a READ
entry for $FG_AIRCRAFT/* already, and I would think explicitly added
aircraft directories
found it :
--fg-aircraft=/my/addons;
On Tue, Nov 30, 2010 at 6:04 PM, syd adams wrote:
> Hi guys, how do I set the path for the development aircraft ...
> outside the FG-ROOT/Aircraft. I did some searching but couldn't find
> the email that announced this recent change.
> Thanks
>
---
Hi guys, how do I set the path for the development aircraft ...
outside the FG-ROOT/Aircraft. I did some searching but couldn't find
the email that announced this recent change.
Thanks
--
Increase Visibility of Your 3D Ga
9 matches
Mail list logo
