On 09/09/2009 01:37 AM, John Denker wrote:
> 4) Back in January I wrote the code to implement correct
> ICAO localizer behavior. This includes the important
> service volume issues that Atadjanov Daniyar reminded us
> about recently, i.e. 09/08/09 09:30. This also includes
> false localize
James Turner wrote:
> - fourthly, and most importantly, I'm not doing a blanket edit - I
> wish I could! I'm going to have to go through each aircraft, make the
> changes, and then test that aircraft. I'm sure I'l miss some things,
> but I still believe it's worth it to kill off the dreaded 5
I'm a new kid on the block but I want to raise and issue.
*The Property Tree Documentation*
Its taken a while to kinda figure out and research/mind shift as to
where its all as there in conflicting information from /src mini-docs
with regard to purpose and my intermittent time of research. Wher
http://en.wikipedia.org/wiki/Distance_measuring_equipment
I know , it's wikipedia , but it gives a short explanation of the VOR -DME
pairing ...
On Tue, Sep 8, 2009 at 1:01 PM, James Turner wrote:
>
> On 8 Sep 2009, at 20:01, Torsten Dreyer wrote:
>
> >> There ara a lot NDB-DME in /data/Nava
On 09/08/09 15:18, dave perry wrote:
> [The] note below caused me to ask if the LOC needle deflection is scaled
> differently than the VOR needle deflection in navradio.cxx. It is and
> the comment that it is 4x more sensitive is correct according to notes
> from Instrument Ground School.
1
I have encountered the same problem. I am using CVS that is a couple weeks
old (I need to update soon.)
The plane starts on the ground, and slowly climbs up. I believe the aircraft
is actually supposed to be static ground scenery, as my AI is turned off.
Additionally, with an older CVS, it remains
On 8 Sep 2009, at 23:18, dave perry wrote:
> I don't think it is a good idea to go to a normalized value in a
> blanket
> edit of other's instruments as the needle deflection in the animation
> SHOULD be scaled to achieve the 2 deg per dot for VOR and the 1/2
> degree
> per dot for the LOC.
Hi James,
Your note below caused me to ask if the LOC needle deflection is scaled
differently than the VOR needle deflection in navradio.cxx. It is and
the comment that it is 4x more sensitive is correct according to notes
from Instrument Ground School. From a pilot point of view, what we nee
i was just flying around kpdx when i ran into one of the ai aircraft.
what made it strange is that instead of being just one plane there were
about five or so aircrfat stacked on top of each other. you can see a
picture at:
http://caliban.lbl.gov/fgfs-weird.jpg
not really sure where this is com
Do I have to do so with NAV1/2? I don't seem to find any way to tune
the KI226 DME without using the radio dialog/using the NAV radios.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial.
On 8 Sep 2009, at 20:01, Torsten Dreyer wrote:
>> There ara a lot NDB-DME in /data/Navaids/nav.dat
>> ...
>> 2 -42.72933900 170.95621900146 310 1000.0 HK HOKITIKA
>> NDB-DME
>> ...
>>
>> http://wikimapia.org/9701833/Hokitika-NDB-DME
> No doubt about this. But I don't know of any
On Tue, 8 Sep 2009, James Turner wrote:
> This:
>
>> Just want to ask developers: is it possible to make ILS/LOC
>> establishing radius more realistic?
>>
>> What we have now in FG? You can establish ILS/LOC anywere you are if
>> you are in n-kilometers over airport. In real life ATC asks pilots:
> 2009/9/8 Torsten Dreyer :
> > NDB-DME
>
> There ara a lot NDB-DME in /data/Navaids/nav.dat
> ...
> 2 -42.72933900 170.95621900146 310 1000.0 HK HOKITIKA NDB-DME
> ...
>
> http://wikimapia.org/9701833/Hokitika-NDB-DME
No doubt about this. But I don't know of any NDB receiver (which
2009/9/8 Torsten Dreyer :
> NDB-DME
There ara a lot NDB-DME in /data/Navaids/nav.dat
...
2 -42.72933900 170.95621900146 310 1000.0 HK HOKITIKA NDB-DME
...
http://wikimapia.org/9701833/Hokitika-NDB-DME
--
---
WBR, Vadym.
---
Then it's my fault :D I don't know how to get DME frequencies, Atlas
doesn't tell me that...
Thanks for the information!
>> One thing I would like, if it's not already avaliable: Being able to
>> tune a DME to a NDB-DME. I can't do that in FG, although Atlas
>> reports
>> some NDBs as having D
> One thing I would like, if it's not already avaliable: Being able to
> tune a DME to a NDB-DME. I can't do that in FG, although Atlas reports
> some NDBs as having DME capability.
Huh? As far as I know there are only DME paired to VOR but not NDB. There are
places where DME and NDB might be at t
> Hi there,
>
> On Mac OS X, FG doesn't handle number keys on Keypad properly.
> Attached is a patch for solving this problem (on
> src/Main/FGEventHandler.cxx), so please commit it.
>
> Here is the brief problem statement.
> FGEventHandler::handleKey converts KEY_KP_Insert ... KEY_KP_PageUp keys t
This:
> Just want to ask developers: is it possible to make ILS/LOC
> establishing radius more realistic?
>
> What we have now in FG? You can establish ILS/LOC anywere you are if
> you are in n-kilometers over airport. In real life ATC asks pilots:
> "Report localizer established" because in
One thing I would like, if it's not already avaliable: Being able to
tune a DME to a NDB-DME. I can't do that in FG, although Atlas reports
some NDBs as having DME capability.
--
Let Crystal Reports handle the reportin
Hi!
Is it possible to fix another bug in navradio (?) system? If runway or the
region has two (or more) NDBs with same frequency, then FG shows only one of
them _everytime_. In real life (as far as i know) NDBs of working runway are
turned on and other NDBs with same freqs are turned off. In MS
Hi!
Just want to ask developers: is it possible to make ILS/LOC establishing radius
more realistic?
What we have now in FG? You can establish ILS/LOC anywere you are if you are in
n-kilometers over airport. In real life ATC asks pilots: "Report localizer
established" because in real life you c
Hi there,
On Mac OS X, FG doesn't handle number keys on Keypad properly.
Attached is a patch for solving this problem (on src/Main/FGEventHandler.cxx),
so please commit it.
Here is the brief problem statement.
FGEventHandler::handleKey converts KEY_KP_Insert ... KEY_KP_PageUp keys to '0'
... '9
As part of cleaning-up the nav-radio code, I need to make a painful
change: fixing the confusion over GS maximum needle deflection.
I'm aware that there's problems with the radio reception model, but
I'm not going to attempt to address that at all - what I need to fix
in the short term is a
James Turner wrote:
>- runways (and taxiways) are initialised with the airport elevation
> instead of a zero elevation in the apt_loader. This is still a poor
> substitute for correct values, but in the absence of source for the
> actual runway elevation profile, it's much better tha
On 7 Sep 2009, at 14:36, dave perry wrote:
> I was wrong about the height being correct. Thought it might be a
> scope
> problem for nav_elev so I tried moving the declaration back to
> navradio.hxx and moving the assignment of a value back into the
> search.
> The search is never called???
Count me in!
Jorg
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. D
On 8 Sep 2009, at 03:59, Tatsuhiro Nishioka wrote:
> I've tried, on my Mac OS 10.5/Xcode 3.1.1, FG/SG as of both Sep-06
> and Sep-07 (without -DNO_OPENSCENEGRAPH_INTERFACE option) and all
> have worked fine so far.
The issue went away following further CVS updates - I guess it was the
upda
27 matches
Mail list logo
