Curtis L. Olson writes:
I'm looking at doing some fault modeling ... things like failing
various instruments, CDI, GS, to/from flag failing, and quite a few
other things with avionics, electrical, fuel, flaps, engines, etc.
What makes the most sense to me is to create a section for
Jon Berndt [EMAIL PROTECTED] said:
JSBSim reports the lat/lon/alt of the current CG. We know the relative
locations of other points, but do not calculate the lat/lon/alt of those. I
don't know who should calculate those things.
Ah ooo..hmmm...see the cg related message I just sent. This
Here is the last few lines before the segmentation fault.
Panel visible = 0
Playing audio after 0 sec: rumble
Playing audio after 0 sec: squeal
Tile not found (Ok if initializing)
scheduling needed tiles for -122.358 37.6117
load() base = /usr/local/FlightGear/Scenery
Loading tile
Dave Perry wrote:
Here is the last few lines before the segmentation fault.
Panel visible = 0
Playing audio after 0 sec: rumble
Playing audio after 0 sec: squeal
Tile not found (Ok if initializing)
scheduling needed tiles for -122.358 37.6117
load() base = /usr/local/FlightGear/Scenery
Loading
Dave Perry
Here is the last few lines before the segmentation fault.
Panel visible = 0
Playing audio after 0 sec: rumble
Playing audio after 0 sec: squeal
Tile not found (Ok if initializing)
scheduling needed tiles for -122.358 37.6117
load() base = /usr/local/FlightGear/Scenery
Norman Vine wrote:
Dave Perry
Here is the last few lines before the segmentation fault.
Panel visible = 0
Playing audio after 0 sec: rumble
Playing audio after 0 sec: squeal
Tile not found (Ok if initializing)
scheduling needed tiles for -122.358 37.6117
load() base =
I really don't understand the requirement as to having the origin
at the same location for all the FDMs.
That's not necessarily true. The requirement would be that the FDMs use the
coordinate system that they need to use, but publish a known point on the
aircraft in its (the FDMs) frame.
William Earnest writes:
Norman Vine wrote:
Dave Perry
Here is the last few lines before the segmentation fault.
load() base = /usr/local/FlightGear/Scenery
Loading tile /usr/local/FlightGear/Scenery/w010n00/w001n00/2938503
Segmentation fault
FWIW, the directory
Jon Berndt
I really don't understand the requirement as to having the origin
at the same location for all the FDMs.
That's not necessarily true. The requirement would be that the FDMs use the
coordinate system that they need to use, but publish a known point on the
aircraft in its (the
Jon Berndt wrote:
I really don't understand the requirement as to having the origin
at the same location for all the FDMs.
That's not necessarily true. The requirement would be that the FDMs use the
coordinate system that they need to use, but publish a known point on the
aircraft in its (the
On 12/12/02 at 10:01 AM Andy Ross wrote:
Fabien ILLIDE wrote:
David Luff wrote:
FWIW, the grey panel with the Radeon 7500 and the DRI drivers still
persists despite the patch to fix this behaviour with the ATI binary
drivers.
I jump onto this post to say that I've just see that I've got
On Saturday, December 14, 2002, at 08:51 PM,
[EMAIL PROTECTED] wrote:
Message: 11
Date: Sun, 15 Dec 2002 01:50:13 +
Subject: Re: [Flightgear-devel] Mac OS X 0.9.1 build available
From: James Turner [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
On Saturday, December
Jon Berndt [EMAIL PROTECTED] said:
This is exactly what I've been pushing for in that last day or two.
FWIW it makes the most sense to me to have the origin at the center of
the bounding sphere of the model
I'm not arguing that this doesn't make sense, BTW, just that it is ambiguous
13 matches
Mail list logo
