Unfortunately DEM data is *way* too noisy and has too much potential for
odd artifacts to use directly. What I have done is to take a coarse
Hmm... About what resolution are we talking here?
What additional data do you have available for the runways? I guess you
have it's position (two
Oliver C. wrote:
This file has been committed.
Thank you, but i think (after looking into cvs today) that you checked in
another file, it is different to my one and doesn't have the fixes.
I committed the one you sent to the list, except that I added the nasal
bindings for flaps already.
Erik
Windows doesn't care whether the files name is upper case, lower case or some
funky mixed case, they all refer to the same file.
I presume that on a case sensitive file system the case of the filename and the
case of the reference to the filename must match, but on Windows this is not
the
* Richard Bytheway -- Monday 08 November 2004 10:13:
I have noticed that there are files in the MD11 model which have the
same name on a system with a case insensitive filesystem:
While we are at it: even though filenames containing spaces are understood
by most file systems, they are still
Melchior wrote:
While we are at it: even though filenames containing spaces are understood
by most file systems, they are still ugly and can cause problems
(especially
when given as an argument to badly written scripts or command lines ;-).
Could these, too, be changed please?
$
Gerhard Wesp wrote:
What additional data do you have available for the runways? I guess you
have it's position (two endpoints? center point, direction, length?)
Runway center point, orientation, length, width and in rare cases an
exact elevation - not to think about that the whole stuff has
Innis,
We brought the mdl T6 model into 3DS max and we're in the process of
cleaning up the geometry and skin (many of the small geometry issues are
likely due to errors during the import). As far as I know, the T6 in
Flightgear never had any animations associated with it. The reworked T6
On Monday 08 November 2004 16:31, Arthur Wiebe wrote:
I will. (Not that I've been trying that hard lately)
The biggest problem is getting plib to compile and install. But then
again my problem was with simgear. I have some new ideas now and will
try them out. If ever I break through the ice
Gerhard Wesp wrote:
Hmm... About what resolution are we talking here?
Generally, 90m SRTM.
What additional data do you have available for the runways? I guess you
have it's position (two endpoints? center point, direction, length?)
and ``elevation''? Commonly, the runway elevation at both
On Tuesday 09 November 2004 09:58, Erik Hofman wrote:
Oliver C. wrote:
This file has been committed.
Thank you, but i think (after looking into cvs today) that you checked in
another file, it is different to my one and doesn't have the fixes.
I committed the one you sent to the list,
Is there an aircraft currently in flightgear that is a good
example of proper 3D cockpit construction? I looked over the p51's files
and it seemed fairly straightforward so following the p51's example I
added these lines to my cong file. With this simple config, the compass only
shows up
On Tue, 9 Nov 2004 12:57:43 -0500, Vance Souders
[EMAIL PROTECTED] wrote:
Is there an aircraft currently in flightgear that is a good example of
proper 3D cockpit construction?
I don't know about 'good', but the J3 Cub and the PA-28-161 both have
pure 3D cockpits (no 2D panel code).
All the
This [wc]ould cause problems in places where runways intersect and
doesn't account for the surface of all the taxiways and the rest of the
Ack. I missed that point.
For what it's worth, I believe I have beaten the nurbs approach into
submission (mostly) and I hope that the next scenery
David wrote:
Is there an aircraft currently in flightgear that is a good example of
proper 3D cockpit construction?
I don't know about 'good', but the J3 Cub and the PA-28-161 both have
pure 3D cockpits (no 2D panel code).
You can add the Spitfire to that list. It might not be good,
I have been trying to build FlightGear 0.96 (CVS) on a Mac, and have been
using fgdev, and have followed the instructions in the FG users guide, as
well as the instructions included in fgdev, but I have run into a bunch of
problems.
Any help that anyone can offer would be greatly appreciated.
I
On Monday, 8 November 2004 11:13, Vivian Meazza wrote:
Could you use the properties browser to make sure
all switches/fuel cocks
are in the right position, and confirm that the
Coffman starter is indexing
correctly? You are using the starter button and not
the adjacent fuel gauge
button (I'm
16 matches
Mail list logo
