Re: [Flightgear-devel] --fog-fastest --fog-disabled - the latter w/o

2004-07-26 Thread Boris Koenig
Hi !
Martin Spott wrote:
Boris Koenig wrote:

--fog-disabled:
http://flitetutor.sourceforge.net/mlist/fgfs-screen-fog-disabled.png

Do you use an ATI Radeon with OpenSource DRI drivers ?
This is an effect I have seen many times during major changes in the
Radeon driver in the XFree86 pre-4.3 phase,
While it is not a Radeon card, it is indeed an ATI (Rage 128) card - the
driver is DRI (from the latest XFree release).
Also, the problem seems indeed to occur only with the ATI card, the same
settings do work on the other machine, otherwise I get less FPS with a
current nvidia card than with the old ATI Rage128 :-/
Erik also mentioned that some of the problems that I previously
described when I was using specific graphic card settings, are
likely to be driver-related, but then: on the other hand I don't
have any of these (or similar) problems on the same machine/config
with other openGL software, regardless if I am running tuxracer, blender
quake or whatever: everything looks normal.
---
Boris
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] --fog-fastest --fog-disabled - the latter w/o update below horizon ?

2004-07-24 Thread Chris Metzler
On Sat, 24 Jul 2004 21:32:25 +0200
Boris Koenig [EMAIL PROTECTED] wrote:

 A couple of other things: I *did* search, but didn't find
 a way to directly set the heading of an aircraft if you
 want to position it in air - if it's there already, please
 tell me where :-)
 
 If it isn't it might be worth to be added ?

What did you search?

Place #1:

} stax:~-534 fgfs --help --verbose
}
} Usage: fgfs [ option ... ]
}
} General Options:
}   --help, -h   Show the most relevant command line options
}   --verbose, -vShow all command line options when
combined
}with --help or -h
}   --fg-root=path   Specify the root data path
}   --fg-scenery=pathSpecify the base scenery path;
}Defaults to $FG_ROOT/Scenery
}   --language=code  Select the language for this session
[ snip ]
}   --lon=degreesStarting longitude (west = -)
}   --lat=degreesStarting latitude (south = -)
}   --altitude=value Starting altitude
}(in feet unless --units-meters specified)
}   --heading=degreesSpecify heading (yaw) angle (Psi)
^^

Place #2:  in Docs/getstart.pdf, Chapter 4 Takeoff:  How to start
the program, Section 4 Command Line Parameters, we come to 4.4.5,
Initial Position and Orientation, which gives the same info as above.
This can also be found in the HTML version of this document, at
Docs/InstallGuide/html/getstart.html (click on 4.4, Command line
parameters).


 Regarding the navaids discussion I'd like to know if airports
 are currently exclusively bound to the scenery, actually I
 was looking for some airports that FlightGear also finds, but
 didn't see any rwys - if airports should really depend on specific
 scenery to be installed, it might be worth to think about
 separating airports from scenery - at least the basics like
 runways etc ...or what else is the reason for not _seeing_
 an airport which FlightGear actually knows of ?

Can you rephrase this?  I can't figure out what it is that you're
saying here.

-c

-- 
Chris Metzler   [EMAIL PROTECTED]
(remove snip-me. to email)

As a child I understood how to give; I have forgotten this grace since I
have become civilized. - Chief Luther Standing Bear


pgpXSqw8xqFYr.pgp
Description: PGP signature
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


Re: [Flightgear-devel] --fog-fastest --fog-disabled - the latter w/o update below horizon ?

2004-07-24 Thread Boris Koenig
Chris Metzler wrote:
On Sat, 24 Jul 2004 21:32:25 +0200
Boris Koenig [EMAIL PROTECTED] wrote:
A couple of other things: I *did* search, but didn't find
a way to directly set the heading of an aircraft if you
want to position it in air - if it's there already, please
tell me where :-)
If it isn't it might be worth to be added ?

What did you search?
sorry, I was reffering to the Set Position dialog within FlightGear,
not any command line options, I do know that you can set these manually
or use directly the property tree, but I thought it might make sense
to directly include that option within the corresponding dialog.
And that's where I was looking for that option, because I thought
it would make sense to be there !?

Can you rephrase this?  I can't figure out what it is that you're
saying here.
lol, simple:
FlightGear knows of various airports that I can pick to start at,
but these airports aren't all *visible* within FlightGear, so -
even if I am sure that I am at the right coordinates I don't see
a specific airport or rather runway layout.
This happens also with standard airports that are selectable
from the corresponding dialog.
My assumption was hence, that the airports are currently bound to
the scenery, as I don't have much additional scenery installed.
That's why I thought that not all airports/runways might already be
available.
So the question is, whether that's true or if there's anything else
wrong with my base package.
I was a bit surprised to learn that, since I thought FlightGear uses 
X-Planes Navaids/Airports info - and X-Plane deals with scenery and
airports separately, so it doesn't matter if I have the necessary
scenery installed or not, because the airports, including the proper
runway aligment will always be available, even if that means that
KLAS 25 R becomes an island within the ocean ;-)

Just tell me if you need even another version of this :-)



Boris
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel