On 7 Sep 2010, at 20:34, James Turner wrote:
I've been turning the idea around in my head for most of today, and I can't
really see a problem with it, though I'm still open to persuasion by a really
convincing argument.
I've pushed this change now - so the correct structure is now:
--
From: James Turner zakal...@mac.com
Sent: Wednesday, September 08, 2010 11:05 AM
To: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] Aircraft dirs (and noisy output
atlog-level=info
--
From: James Turner zakal...@mac.com
Sent: Monday, September 06, 2010 11:06 PM
To: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] Aircraft dirs (and noisy output
atlog-level=info)
On 6
On 7 Sep 2010, at 08:25, Alan Teeder wrote:
I could add code to ensure the directory passed to --fg-aircraft has an
'Aircraft' subdir, or I could do the hacking such that an intermediate dir
named Aircraft is unnecessary - it means slightly more messing with the
file paths, but I can't
Just thinking out loud , but wont all the paths in the aircraft's xml files
need to change ?
I'm thinking of the ones that require the full /Aircraft/myplane/Sound ,,,
etc .
Having a separate Aircraft folder seems like it would make dropping the
finished work into fgdata/Aircraft fairly painless.
On 7 Sep 2010, at 20:14, syd adams wrote:
Just thinking out loud , but wont all the paths in the aircraft's xml files
need to change ?
I'm thinking of the ones that require the full /Aircraft/myplane/Sound ,,,
etc .
Having a separate Aircraft folder seems like it would make dropping the
On 5 Sep 2010, at 20:46, Ron Jensen wrote:
OK, I tried
$fgfs --help --verbose
That came up with --aircraft-dir but not --fg-aircraft.
I discussed this with Ron on IRC, and seperately with Durk a few days ago -
--aircraft-dir is a very old option, which I will remove (or maybe just hide),
On 5 Sep 2010, at 12:26, James Turner wrote:
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,
--
From: James Turner zakal...@mac.com
Sent: Monday, September 06, 2010 9:59 AM
To: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] Aircraft dirs (and noisy output
atlog-level=info)
On 5
On 6 Sep 2010, at 18:03, Alan Teeder wrote:
Now with e.g. Lightning outside fgdata I get no part of the aircraft - even
the splash screen is white. There are none of the log messages saying which
aircraft directory is in use. I do see the message Cannot find image file
.
Can you give
--
From: James Turner zakal...@mac.com
Sent: Monday, September 06, 2010 9:46 PM
To: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] Aircraft dirs (and noisy output
atlog-level=info)
On 6
On 6 Sep 2010, at 22:19, Alan Teeder wrote:
No command line. I am executing a shortcut to fgfs.exe.
My structure is (I think) conventional, e.g.
Flightgear
3rd Party
fgdata (git)
flightgear (git)
simgear
--
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
On 5 Sep 2010, at 11:29, Alan Teeder wrote:
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,
On Sunday 05 September 2010 05:26:33 James Turner wrote:
On 5 Sep 2010, at 11:29, Alan Teeder wrote:
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
Hi Ron,
On Sunday, September 05, 2010 09:12:27 pm Ron Jensen wrote:
$fgfs --aircraft-dir=/home/jentron/fg/fgdata/Aircraft/fokker100
--aircraft=fokker100 Cannot find specified aircraft: fokker100
Config option parsing failed ...
The correct option is --fg-aircraft. --aircraft-dir is
On Sunday 05 September 2010 13:26:45 Durk Talsma wrote:
Hi Ron,
The correct option is --fg-aircraft. --aircraft-dir is (presumably) an
older option that is unrelated to the new aircraft infrastructure recently
developed by James.
I actually ran into the same issue earlier on. I can't recall
17 matches
Mail list logo
