-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello to all,
I've downloaded/installed/compiled the latest bleeding edge CVS tarballs of
SimGear/FlightGear (as described in the getting started guide).
I haven't had a problem doing all the necessary steps (well, only one: the
link of the SimGear
Tommygio writes:
-BEGIN PGP SIGNED MESSAGE-
Hello to all,
I've downloaded/installed/compiled the latest bleeding edge CVS tarballs of
SimGear/FlightGear (as described in the getting started guide).
I haven't had a problem doing all the necessary steps (well, only one: the
link of the
Danie Heath writes:
I take it you guys are running some sort of binary space partitioning,
what is the type you use ?
Can you be more specific? Partitioning which space, for what purpose?
Thanks,
Curt.
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Cities
Title: Message
Hi again ...The Binary Space Partitioning I mean is
:What is the method you guys follow to subdivide the scenery, objects,
aircraft so that you only render what you see ... Wouldn't the rendering be more
efficient with a system like this ...Danie HeathRisC Com cc+27
12 654
Danie Heath writes:
What is the method you guys follow to subdivide the scenery, objects,
aircraft so that you only render what you see ... Wouldn't the rendering
be more efficient with a system like this ...
Plib defines a bounding sphere for each leaf or branch node in a scene
graph,
Once upon a time, you were sitting and writing:
What is the method you guys follow to subdivide the scenery, objects,
aircraft so that you only render what you see ... Wouldn't the rendering
be more efficient with a system like this ...
Hm binary trees ?
I always thought the main
Danie Heath writes:
Hi again ...
The Binary Space Partitioning I mean is :
What is the method you guys follow to subdivide the scenery, objects,
aircraft so that you only render what you see ... Wouldn't the rendering
be more efficient with a system like this ...
We use a scheme where we
Hello,
With an older cvs of plib, the current FlightGear cvs builds and runs
fine. With the plib cvs update within the past 2 days, (and the
Makefile edits to include -lplibjs), fgfs segfaults consistently for
me, both on RH 7.1 and RH 7.3. A faster machine than my usual one,
with 7.3, gets
Hello again,
Backing out the plib cvs changes to 6 days ago eliminated the
segfault I see in fgfs. The additions of -lplibjs to the Makefile
files is still in place, but causes no problem. Hope someone with more
experience can resolve what else changed in an incompatible way.
--
Bill
Hi,
this is my latest in the neverending series of dumb questions. I have
a Radeon 8500 that does a great job for most of my work. I currently
use the ATI binary driver (since XFree86 hasn't quite got good 3D
support, but it's getting there).
I updated the driver from the fglr200-1.4.3 to the
Major A [EMAIL PROTECTED] said:
- the 747-yasim panel is not drawn at all -- all I get is the beige
background, no instruments. Running the same CVS build without DRI,
I get all instruments (at 0.3fps though). All worked fine with the
older driver.
There is no 747 panel...yet. :-)
- the 747-yasim panel is not drawn at all -- all I get is the beige
background, no instruments. Running the same CVS build without DRI,
I get all instruments (at 0.3fps though). All worked fine with the
older driver.
There is no 747 panel...yet. :-)
Sorry, I only said 747
Just another question: I noticed that the different places in which
heading plays a role (the different indicators as well as the
autopilot) use magnetic and geographic heading at will. Are there any
plans to unify them and/or come up with a convention of what heading
is magnetic and what isn't?
I've noticed that there is an abundance of FDMs in FlightGear. It also
seems that yasim and jsbsim are developed in parallel -- is there one
which is considered most universal or simply best?
Two different approaches are used in modeling aircraft aerodynamics. You
can learn more about JSBSim
Major A writes:
I've noticed that there is an abundance of FDMs in FlightGear. It also
seems that yasim and jsbsim are developed in parallel -- is there one
which is considered most universal or simply best?
No.
All the best,
David
--
David Megginson, [EMAIL PROTECTED],
Major A wrote:
Sorry, I only said 747 because that was the only one I could run in
the broken build I used. I now fixed that one, it happens with all
2D panels, 172, 182, 747 (press P), etc.
I can confirm this. Layers on the 2D panels (but oddly, only the 2D
panels) aren't drawing over the
Major A writes:
Just another question: I noticed that the different places in which
heading plays a role (the different indicators as well as the
autopilot) use magnetic and geographic heading at will. Are there any
plans to unify them and/or come up with a convention of what heading
is
I wrote:
I can confirm this. Layers on the 2D panels (but oddly, only the 2D
panels) aren't drawing over the background with the current ATI
drivers.
OK, this turns out to be a trivial fix, although I still think it's a
driver bug. There are two calls to glPolygonOffset in the panel
Another ATI bug I've noticed is that they seem to have trouble with
texture border. It's sampling the border color even when there is no
border width defined, with the result that the runway tiles have dark
shadows between them. Screenshot at:
OK, this turns out to be a trivial fix, although I still think it's a
driver bug. There are two calls to glPolygonOffset in the panel
rendering code (shared by both 2D and 3D panels). One is called
per-layer, and sets up a layer-specific offset. The other is called
for drawing the
Andy,
I could easily be wrong since I've never messed with glPolygonOffset
myself, but it's my understanding that one of the problems with this
function is that the values you need to assign to the parameters can be
different across platforms to accomplish the same thing.
Curt.
Andy Ross
- The autopilot in the 172 tries to keep the orange heading bug at the
top of the directional gyro, period. If you set the DG to the true
heading (as you would in the Arctic), then the autopilot uses true
Ever flown a (real) 172 across the North Pole? :-)
The only place you can get the
Curtis L. Olson wrote:
I could easily be wrong since I've never messed with glPolygonOffset
myself, but it's my understanding that one of the problems with this
function is that the values you need to assign to the parameters can
be different across platforms to accomplish the same thing.
David Megginson writes:
The only place you can get the true heading directly is the HUD, which
isn't really meant to simulate anything you'll find in a small plane
-- it's just a (useful) developer's tool or a user's toy.
Note David is talking from a 'small plane' C172 perspective.
There
Major A writes:
- The autopilot in the 172 tries to keep the orange heading bug at the
top of the directional gyro, period. If you set the DG to the true
heading (as you would in the Arctic), then the autopilot uses true
Ever flown a (real) 172 across the North Pole? :-)
No,
Norman Vine writes:
The only place you can get the true heading directly is the HUD, which
isn't really meant to simulate anything you'll find in a small plane
-- it's just a (useful) developer's tool or a user's toy.
Note David is talking from a 'small plane' C172 perspective.
David Megginson wrote:
Major A writes:
- The autopilot in the 172 tries to keep the orange heading bug at the
top of the directional gyro, period. If you set the DG to the true
heading (as you would in the Arctic), then the autopilot uses true
Ever flown a (real) 172 across the
David Megginson writes:
Major A writes:
- The autopilot in the 172 tries to keep the orange heading bug at the
top of the directional gyro, period. If you set the DG to the true
heading (as you would in the Arctic), then the autopilot uses true
Ever flown a (real) 172
Andy Ross writes:
It's worth pointing out that a DG will work fine in the polar regions.
Other than precession (which has a 24 hour period -- hardly a huge
source of error), there's no way for it to know that it's over the
pole. It will even work fine on the pole itself, in the sense that
29 matches
Mail list logo
