: 27 février 2010 12:59
À : FlightGear developers discussions
Objet : Re: [Flightgear-devel] Duplicate files in base package
Hi,
What ever is discussed, decided, as someone else noted,
a full FG 'base' data checkout now takes HOURS, on a
fast machine with good Internet connection,
Interesting idea... Ive got a panel file for each panel layout , but that
changes the entire instrument positions and types , not individual
instruments ...
Might be tricky unless the instrument selection is from the Instruments-3d
folder ...
Just thinking out loud here :)
Syd
On Sat, Feb 27, 201
I don't know about dynamic positioning of instruments, but I would
find it interesting to have an easy method of selecting alternate
instruments for the same position. For example, I have several
attitude indicator variations that could be used based on period or
pilot/owner preference. This would
I can see 3d instruments being easier position them on the panel with a
mouse click then drag them like i did the b1900d manual ... or menu buttons
in a dialog like the ufo does scenery objects for finer adjustments ...
I suppose the 2d instrument placement would be almost the same...
Dont kno
Could certainly be done ... perhaps (although maybe a little awkwardly ...
or not?) using the FlightGear gui and nasal infrastructure.
I'm envisioning the 2d panel structure I guess ... probably would be more
complicated with 3d panels.
Curt.
On Sat, Feb 27, 2010 at 2:26 PM, syd adams wrote:
>
I think I misunderstood you ... a graphical tool to do this would certainly
speed things up ... currently I used a dummy panel in Blender to find
positions.
I though you meant from the runtime menu :).
Syd
On Sat, Feb 27, 2010 at 11:23 AM, David Megginson wrote:
> On Sat, Feb 27, 2010 at 2:10
On Sat, Feb 27, 2010 at 2:10 PM, syd adams wrote:
> Its already pretty easy to point the section to a different
> instrument , and the one Im currently working on , Im creating several panel
> files with different layouts that can be selected in the set file , but I'd
> hate to see instruments b
Ewww , a GUI to do this ?
Its already pretty easy to point the section to a different
instrument , and the one Im currently working on , Im creating several panel
files with different layouts that can be selected in the set file , but I'd
hate to see instruments being changeable while in flight ..
On Sat, 2010-02-27 at 10:18 -0700, Ron Jensen wrote:
> On Sat, 2010-02-27 at 07:56 -0500, David Megginson wrote:
> > On Fri, Feb 26, 2010 at 10:21 PM, Ron Jensen wrote:
> >
> > >> I still support the idea common shared directories idea for such things
> > >> as
> > >> instruments
Hi,
What eve
On Sat, 2010-02-27 at 07:56 -0500, David Megginson wrote:
> On Fri, Feb 26, 2010 at 10:21 PM, Ron Jensen wrote:
>
> >> I still support the idea common shared directories idea for such things as
> >> instruments
>
> > This is a nice, happy thought. But in the real world it hasn't worked
> > out
Something I'd love to see, in the long term, is a GUI that allows
users to customize their panels, just like real aircraft owners do. I
could decide to install a different brand of TC (the default late
1970s Cessna 172P now has a vintage 1950s needle and ball instead of a
TC -- cool, but what's up
> A Sigma-Tek attitude gyro, for example, looks and works pretty-much
> the same as a primary instrument for a Cessna 150 or as a backup
> instrument on a 747 -- the differences (such as different voltage for
> the backlighting) are pretty trivial. I'd hate to see 100 copies of
> the same Sigma-Te
On Fri, Feb 26, 2010 at 10:21 PM, Ron Jensen wrote:
>> I still support the idea common shared directories idea for such things as
>> instruments
> This is a nice, happy thought. But in the real world it hasn't worked
> out so well. Since we model such a huge variety of aircraft, and
> differe
On Fri, 2010-02-26 at 21:13 +, Alan Teeder wrote:
> I still support the idea common shared directories idea for such things as
> instruments
>
> Alan
This is a nice, happy thought. But in the real world it hasn't worked
out so well. Since we model such a huge variety of aircraft, and
di
--
From: "Gene Buckle"
Sent: Friday, February 26, 2010 8:29 PM
To: "FlightGear developers discussions"
Subject: Re: [Flightgear-devel] Duplicate files in base package
> On Fri, 26 Feb 2010, Alan Teeder wrote:
>
>>
On Fri, 26 Feb 2010, Alan Teeder wrote:
>> Maybe it's time to use what's already there?
>>
> One problem which springs to mind is that there must be many same name files
> (e.g. HSI.xml and its related HSI.ac) which are specific to one aircraft and
> are in fact entirely different.
>
> These will
--
From: "Stefan Seifert"
Sent: Friday, February 26, 2010 5:26 PM
To: "FlightGear developers discussions"
Subject: Re: [Flightgear-devel] Duplicate files in base package
> This repeatedly strikes me as problems that Linux
On Friday 26 February 2010 17:16:38 Detlef Faber wrote:
> I guess most duplicate files are instruments which are not in the
> generic folder.
> Of course it would be desireable to have them all in one place and
> reference to there, but that would cause severe problems with the
> aircraft download
Am Donnerstag, den 25.02.2010, 22:23 +0100 schrieb Roy Vegard Ovesen:
> FSlint reports that the base package, or the data directory, contains quite a
> lot of duplicate files. The file that is wasting the most bytes is
> glass_shader.png (some instances named glass.png) with 43 974 656 bytes, or
On Friday February 26 2010 02:18:30 syd adams wrote:
> I agree , there's a lot of duplication ,(in instruments, too) but I think
> the problem is author's tastes ...
> I've duplicated textures because I dont care for the look , or style ,
> etc,of existing ones and Im sure that's the same for other
I agree , there's a lot of duplication ,(in instruments, too) but I think
the problem is author's tastes ...
I've duplicated textures because I dont care for the look , or style ,
etc,of existing ones and Im sure that's the same for other contributors.
So it might be a problem deciding who's get's
21 matches
Mail list logo
