On Monday 12 June 2006 07:15, Mick - wrote:
Through observation, I found that my calculated agl value (as discussed in
my
previous post) was close to that of /position/ground-elev-ft when using
the
current lat/lon values instead of those from
Point3D calc_gc_lon_lat( const Point3D orig,
Hi,
On Sunday 11 June 2006 06:53, Mick - wrote:
I've managed to get Mathias' suggestion of using get_elevation_m but with
strange AGL values.
I used calc_gc_lon_lat from simgear/math/polar3d.hxx for getting the
latitude/longitude from
x-meters away, then feeding the resulting lat/lon values
: Re: [Flightgear-devel] collision avoidance
Date: Sun, 11 Jun 2006 12:21:23 +0200
Hi,
On Sunday 11 June 2006 06:53, Mick - wrote:
I've managed to get Mathias' suggestion of using get_elevation_m but
with
strange AGL values.
I used calc_gc_lon_lat from simgear/math/polar3d.hxx for getting
[EMAIL PROTECTED]
Reply-To: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
To: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] collision avoidance
Date: Fri, 02 Jun 2006 13:58:18 +0200
Hi all!
Best thing to do
Hi all!
Best thing to do would be bounding boxes. It's fast to calculate and
relative accurate.
You can calculate bounding box for each object one time and use every
time!
On Friday 02 June 2006 01:44, Mick - wrote:
I'm trying to create a type of collision avoidance capability, and would
I'm trying to create a type of collision avoidance capability, and would
need AGL data from in front of the aircraft.
Could someone suggest where (in the code) I could get projected elevation
information, for example, AGL data 10 meters in front. My understanding is
that AGL is taken from the
6 matches
Mail list logo
