, 2013 at 1:48 AM, Dirk Dittmann
dirk.dittmann@gmail.comwrote:
Am Donnerstag, 3. Oktober 2013, 21:38:52 schrieb James Turner:
On 3 Oct 2013, at 17:35, Dirk Dittmann dirk.dittmann@gmail.com
wrote:
The improved-issue1164 is ready.
https://gitorious.org/fg/dirks-flightgear
Am Donnerstag, 3. Oktober 2013, 21:38:52 schrieb James Turner:
On 3 Oct 2013, at 17:35, Dirk Dittmann dirk.dittmann@gmail.com wrote:
The improved-issue1164 is ready.
https://gitorious.org/fg/dirks-flightgear/source/778cc8c6a0abb88a1238850376ea2374358fd887:
Thanks, looks good and pushed
Hi James,
The improved-issue1164 is ready.
https://gitorious.org/fg/dirks-flightgear/source/778cc8c6a0abb88a1238850376ea2374358fd887:
Dirk
Am Dienstag, 1. Oktober 2013, 21:37:58 schrieb James Turner:
- please make a helper function for the great-circle XTK error function,
with some sane
Am Dienstag, 1. Oktober 2013, 21:37:58 schrieb James Turner:
On 30 Sep 2013, at 08:47, Dirk Dittmann dirk.dittmann@gmail.com wrote:
branche fix-issue1164 @ my clone
https://gitorious.org/fg/dirks-flightgear/source/85592ec45db2866a15197c051d97cb4014537b4b:
Hi Dirk, this is looking
Hello,
Improved the Cross track error according to the great circle.
http://williams.best.vwh.net/avform.htm#XTE.
And make the overflight sequence configurable for the aircraft. The default is
the same.
/instrumentation/gps/config/over-flight-arm-angle-deg 90
Am Montag, 30. September 2013, 09:00:19 schrieb James Turner:
On 30 Sep 2013, at 08:47, Dirk Dittmann dirk.dittmann@gmail.com wrote:
Improved the Cross track error according to the great circle.
http://williams.best.vwh.net/avform.htm#XTE.
Great,.
And make the overflight sequence
Am Montag, 30. September 2013, 12:52:08 schrieb James Turner:
On 30 Sep 2013, at 12:29, Eric van den Berg evan_den_b...@hotmail.com
wrote:
The other stuff I asked Dirk to add as it makes our extra500 (GPSS) AP
design a lot easier.
Incidentally if you (Dirk) are looking at this code, the
Hi Clément,
I'm not convinced adding a string is relevant, in real life you haven't a
message you tell you if you are correctly connected to X frequency. The
only way to check is to look at your radio, in FG it's the same.
seams we have different experience in fgcom. And there will be no
Clément,
The easier solution is the last one, it can be really easy to implement this
in FGCom standalone/integrated and totally transparent for our users. As
example, we can decide that
fgcom01.flightgear.org handles frequencies 118.0 to 124.9
fgcom02.flightgear.org handles frequencies
Am Donnerstag, 15. August 2013, 21:52:34 schrieb Clement de l'Hamaide:
Hi Clément,
- bandwith:
Indeed IAXClient has a function called void iaxc_set_silence_threshold(float
thr); unfortunately, looking at source code this function does exactly the
same as we are doing in FGCom source code :
- frequencies range:
I understand your problem about multiple identical frequences but it seems
the problem comes from our apt.dat file which is excessively out-dated.
Looking at Jeppensen charts it appears that
- EDBM doesn't transmit on 124.170 in real world :
11 matches
Mail list logo