On Tuesday, November 27, 2012 14:53:07 James Turner wrote:
>
> Gitorious was down this morning, or I would have already given some review
> comments. However I see quite a few new versions of the patch, it would be
> good to know it's 'ready' from your perspective, before reviewing. I too
> would
On 27 Nov 2012, at 12:44, Adrian Musceac wrote:
> I have not updated the merge request with these features yet, waiting for the
> new radio to make it into 'next' since it's enough code there already.
> I have also added a "Request for info" chapter in the wiki page, asking
> anybody with deep
Update: I've added new signal calculation for DME stations too. As explained
detailed in the wiki, DME uses a very high frequency range, thus it is
possible sometimes in reality to receive the VOR signal but not the DME
signal. Screenshots provided in the wiki article.
Also, TACAN reception is
On Monday, November 26, 2012 19:18:26 James Turner wrote:
> I'll do a review if no-one beats me to it, but this definitely needs to be
> 'off-by-default' for the next release. We can add a checkbox to the
> realism dialog to enable it from the GUI, and give aircraft authors a
> chance to adapt.
>
On Monday, November 26, 2012 19:18:26 James Turner wrote:
>
> I'll do a review if no-one beats me to it, but this definitely needs to be
> 'off-by-default' for the next release. We can add a checkbox to the
> realism dialog to enable it from the GUI, and give aircraft authors a
> chance to adapt.
On 26 Nov 2012, at 17:11, Adrian Musceac wrote:
> I have added VOR, localizer and glideslope signal calculations for the old
> (classic) navradios (navradio.cxx)
> Now an ILS navaid is basically considered as two separate stations: Localizer
> and glideslope, as in reality. Both these stations
Hi,
I have added VOR, localizer and glideslope signal calculations for the old
(classic) navradios (navradio.cxx)
Now an ILS navaid is basically considered as two separate stations: Localizer
and glideslope, as in reality. Both these stations can have separate
parameters like transmitter power,
> "Jean" == jean pellotier writes:
Jean> I see the update is done, thanks, (and sorry for windows users
Jean> waiting for a compatible binary build :) ). It appears that
Jean> Atlas don't like the new nav.dat.gz, and crash on start up,
Jean> because some navaids contains empt
Martin Spott a écrit :
Salut Jean,
jean pellotier wrote:
Is nav.dat supposed to be updated from robin X-plane database?
If nobody else is going to do that, I'll be updating the file from
Robin's most current package during our pre-release phase (however this
is going to be defined ..
John Denker wrote:
> On the opposite side of the same coin, the last time
> I looked, the scenery database listed huge numbers of
> airports that were unknown to Robin's database.
I don't know which "scenery database" you've been looking at, but it's
certainly not been the one which we're using
On 19 Dec 2009, at 16:19, John Denker wrote:
> Maybe the code should be made more robust so that this
> is not a fault condition.
>
> This is not the first time in history that code has
> needed to perform a join on two databases that are
> not in one-to-one correspondence.
Well I wrote the co
On 12/19/2009 07:40 AM, Martin Spott wrote:
> ... Robin's current set of navaids ...
> contains navaids for airfields which are otherwise unknown to
> FlightGear,
On the opposite side of the same coin, the last time
I looked, the scenery database listed huge numbers of
airports that were unknow
Pete Morgan wrote:
> Is nav.dat supposed to be updated from robin X-plane database?
Yes.
>> If nobody else is going to do that, I'll be updating the file from
>> Robin's most current package during our pre-release phase (however this
>> is going to be defined ).
>>
>>
> Can't the data be
Is nav.dat supposed to be updated from robin X-plane database?
>
> If nobody else is going to do that, I'll be updating the file from
> Robin's most current package during our pre-release phase (however this
> is going to be defined ).
>
>
Can't the data be commited to CVS now ?
pete
---
Salut Jean,
jean pellotier wrote:
> Is nav.dat supposed to be updated from robin X-plane database?
If nobody else is going to do that, I'll be updating the file from
Robin's most current package during our pre-release phase (however this
is going to be defined ).
> here's a diff toward our
Hi,
I've got a question about the navaids, particularly nav.dat.
Is nav.dat supposed to be updated from robin X-plane database?
The french missing navaids I submited to robin ( approach locators ) are
included in recent nav.dat from X-plane, and I was waiting them to come
in Flightgear, but a
On 02/07/2008 07:28 AM, Cleber Santz wrote:
> I have trace same routes using waypoints and find many duplicates
> entries in FIX Data ( like LEPAS, HARDY ) with different coordinates,
> thats is correct ?
1) That is a correct observation, there are duplicate fixes. That
includes named waypoints
Yes, SBGL is in APT.DAT but the FIX around is not in FIX.DAT ( Like FICO,
PERES )
And there duplicates entries in X-Plane data too, i have send mail for Robin
check it, but FIX of around SBGL airport is in X-Plane but not in Flightgear.
Tks,
Cleber
"K. Hoercher" <[EMAIL PROTECTED]> escre
On Thu, Feb 07, 2008 at 03:42:05PM +0100, Pietro wrote:
> At Thursday 07 February 2008 15:28:55 Cleber Santz wrote:
> >One more thing, some FIX that find in X-Plane navaid data not appers in
> > FlightGear ( FIX for SBGL airport for example ), is not the same database ?
Well I checked LEPAS an
At Thursday 07 February 2008 15:28:55 Cleber Santz wrote:
>One more thing, some FIX that find in X-Plane navaid data not appers in
> FlightGear ( FIX for SBGL airport for example ), is not the same database ?
Hi,
AFAIK the fgfs navaids files have been converted from X-plane data files,
but al
Hi,
I have trace same routes using waypoints and find many duplicates entries in
FIX Data ( like LEPAS, HARDY ) with different coordinates, thats is correct ?
One more thing, some FIX that find in X-Plane navaid data not appers in
FlightGear ( FIX for SBGL airport for example ), is not t
Mathias Fröhlich wrote:
Jon,
On Tuesday 24 January 2006 22:45, Jon Stockill wrote:
I've just discovered that when using the null fdm I'm not getting
updates to /position/ground-elev-m any more. So I can't actually
retrieve the terrain elevation. Is there somewhere else in the property
tree I c
Jon,
On Tuesday 24 January 2006 22:45, Jon Stockill wrote:
> I've just discovered that when using the null fdm I'm not getting
> updates to /position/ground-elev-m any more. So I can't actually
> retrieve the terrain elevation. Is there somewhere else in the property
> tree I could read this from
Curtis L. Olson wrote:
Hmmm, ouch, ground_cache issues? This was added by others so I don't
understand it enough to know if this could be the issue or not. Might
be something to look at though ...
Well using the UFO, without specifying fdm=null seems to work. Just got
to hope the UFO doesn
Thanks guys did an update and ILS works again ! Now I just
have to figure out why I break my Nav needle animations when using
several different conditions on the same object . :)
Cheers ,
Syd
---
This SF.net email is sponsored by: Spl
On Tuesday 24 January 2006 22:45, Jon Stockill wrote:
> Jon Stockill wrote:
> > So with any luck I should have a full update of all the navaids in the
> > database with correct elevations by this weekend.
>
> It seems I don't have any luck at the moment.
>
> I've just discovered that when using the
Jon Stockill wrote:
Jon Stockill wrote:
So with any luck I should have a full update of all the navaids in
the database with correct elevations by this weekend.
It seems I don't have any luck at the moment.
I've just discovered that when using the null fdm I'm not getting
updates to /posi
Jon Stockill wrote:
So with any luck I should have a full update of all the navaids in the
database with correct elevations by this weekend.
It seems I don't have any luck at the moment.
I've just discovered that when using the null fdm I'm not getting
updates to /position/ground-elev-m any
Curtis L. Olson wrote:
Hmmm, it appears that Robin added a range field to the data file, and
embarasingly, I didn't not notice before updating the data file. I see
if I can get that straightened out here.
That caught me out too, however I now have a script to import the
current format into t
Curtis L. Olson wrote:
Hmmm, it appears that Robin added a range field to the data file, and
embarasingly, I didn't not notice before updating the data file. I
see if I can get that straightened out here.
Hi Syd, give the latest cvs (code) a try ...
Curt.
--
Curtis Olsonhttp://www
syd & sandy wrote:
After a very recent CVS update I noticed some strange behavior while
working on my Citation-Bravo ... heading needle deviation seems to be
inaccurate. I fired up Atlas and the first thing I noticed was ALL ILS
navaids were pointing roughly south .Has anyone else noticed this .
After a very recent CVS update I noticed some strange behavior while
working on my Citation-Bravo ... heading needle deviation seems to be
inaccurate. I fired up Atlas and the first thing I noticed was ALL ILS
navaids were pointing roughly south .Has anyone else noticed this ...
or have I messed up
32 matches
Mail list logo
