On 14 Sep 2009, at 00:23, Pete Morgan wrote:
Flying the East to West eg from EGLC London City to EGLL Heathrow
crashes in a similar fashion.
That's weird, I flew from EGLL to EGLC just the other day, and it
worked fine.
I'll try the route, and aircraft you suggested, in the next couple of
Two (unrelated) glideslope things:
1) I tested making the has-gs property be based upon the GS range
check (leaving aside any discussion of how GS reception range should
be calculated). This is good, because existing panels generally use
has-gs as a 'valid GS signal being received', to
Hello,
few days ago I have explore FlightGear and I have install a FGMS on my
server. Now I have seen, that the MPServer network has a very few
selection for servers that are running. So I offer the server for the
MPServer network. If you want one server more in your network that
stands in
On Mon, 2009-09-14 at 10:38 +0100, James Turner wrote:
Two (unrelated) glideslope things:
1) I tested making the has-gs property be based upon the GS range
check (leaving aside any discussion of how GS reception range should
be calculated). This is good, because existing panels generally
On 09/14/09 02:38, James Turner wrote:
Two (unrelated) glideslope things:
1) I tested making the has-gs property be based upon the GS range
check (leaving aside any discussion of how GS reception range should
be calculated). This is good, because existing panels generally use
has-gs
Hi all. I've got a bunch of shapefile data for the island of Newfoundland that
I'm intending to use in Terragear. It's called Canvec data, and I think I'm
going to need to use ogr-decode on it to get it into WGS84 format. Provided I'm
understanding this correctly, that is. Everything in the
Two (unrelated) glideslope things:
1) I tested making the has-gs property be based upon the GS range
check (leaving aside any discussion of how GS reception range should
be calculated). This is good, because existing panels generally use
has-gs as a 'valid GS signal being received', to
On 14 Sep 2009, at 15:44, John Denker wrote:
Specifically, I recommend introducing dme_inrange
and gs_inrange properties. The concept of dme in
range and gs in range are meaningful to real
world pilots.
Yep, seems reasonable to me, I was already looking at the navradio DME
patch.
I'll change all of my AP glideslope behaviors , the hacks are usually
because I haven't
found any documentation , so I go with a rough guess. I have come across
information that states that on some systems , the glideslope will not
capture until the localizer has been.
I also use the has-gs when
Hello,
i try to overlay a HUD over my flightgear application.
The HUD is generated by a other computer and I am grabbing it with a
framegrabber card.
The backgroundcolor of the HUD which I display in a window (windows) I
set transparent so that the background is the output of my flightgear
On 14 Sep 2009, at 18:51, syd adams wrote:
Another thing I've always wanted in the nav system is an RNAV radial
and RNAV distance
property, and the nav calculations done from this phantom station.
Dont know how doable that is since I dont feel qualified enough to
tackle that.
I'm lost
On 14 Sep 2009, at 18:44, James Turner wrote:
Specifically, I recommend introducing dme_inrange
and gs_inrange properties. The concept of dme in
range and gs in range are meaningful to real
world pilots.
The gs-in-range prop is in CVS now. Next up is integrating your
navradio-DME patch.
On 14 Sep 2009, at 16:54, Torsten Dreyer wrote:
But I can provide a fix for a potential division by zero bug: Some
stations
don't have a range configured and bomb here:
double range_exceed_norm = loc_dist/effective_range_m;
Thanks Torsten, I fixed this slightly differently, but a good
Indeed. I have a X52 joystick and it's very confusing to configure in the
joystick .xml file. When I updated to CVS recently, the hats buttons don't
work properly in windows. This should be looked at and fixed.
On Mon, Sep 14, 2009 at 6:45 PM, Tatsuhiro Nishioka
tat.fgmac...@gmail.comwrote:
Hi,
14 matches
Mail list logo
