On Fri, Feb 26, 2010 at 10:21 PM, Ron Jensen w...@jentronics.com 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,
Yippee! After the recent A380 update, there are
presently NO 'case' only duplicates in any single
folder, causing a Windows cvs update to hiccup...
Thank you all... Case closed ;=))
Geoff.
PS: This is nothing to do with a
parallel, seemingly similar thread -
RE: Duplicate files in base
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-Tek
On Fri, 2010-02-26 at 16:39 -0600, stan.mar...@l-3com.com wrote:
Update on my own post, regarding the missing files...
Hi Stan, et al,
includes a number of files which appear to have moved ...
In addition to the dependencies problems, mentioned by
Reagan, this missing or moved files also adds
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
I just updated data to try the A380, and I'm not seeing any model (interior or
exterior) - the FDM and other pieces seem to be loading fine. My tree contains
assorted minor changes, but nothing that should affect this.
Relevant errors, I suspect:
Failed to load submodel: Failed to load 3D
On Sat, 2010-02-27 at 07:56 -0500, David Megginson wrote:
On Fri, Feb 26, 2010 at 10:21 PM, Ron Jensen w...@jentronics.com 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
Ewww , a GUI to do this ?
Its already pretty easy to point the model 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
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 david.meggin...@gmail.com
wrote:
On
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:
Yeah this was discussed earlier because that list rapidly filled up with old
bugs .
I agree , missing features , or incomplete feature , or not knowing how an
instrument works shouldn't be filed as a bug :)
On Sat, Feb 27, 2010 at 12:54 PM, Heiko Schulz aeitsch...@yahoo.de wrote:
Hi,
The
Heiko Schulz wrote:
I wonder if a bug-tracker makes really sense here- we have more than 130 (?)
aircrafts
130?! There's 300 of them in CVS, so about 350 with the additional hangars! :)
Agree with you on all points btw. It might be nice to have an additional bug
tracker for
aircraft
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
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,
I don't want to see any feature requests for the code either :)
Tim
On Sat, Feb 27, 2010 at 9:54 PM, Heiko Schulz aeitsch...@yahoo.de wrote:
Hi,
The Google Bug tracker is a nice instrument for the harcore developers
here.
But I have some problems with bug tracking there on aircrafts.
All
Index: terrasync.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/utils/TerraSync/terrasync.cxx,v
retrieving revision 1.28
diff -u -r1.28 terrasync.cxx
--- terrasync.cxx 23 Jan 2010 22:27:38 - 1.28
+++ terrasync.cxx
16 matches
Mail list logo
