If its any help , the error message pops up the instant the gps dialog is
opened.The dialog seems to work regardless , so Im not sure what the
problem is.
Syd
On Wed, Oct 9, 2013 at 1:20 PM, syd adams wrote:
> No , Im not sure what caused the segfault... but the error message appears
> every ti
No , Im not sure what caused the segfault... but the error message appears
every time i try to use gps navigation ( with the b1900d).Another change in
behavior is the heading needle deflection is extremely sensitive now when
using nav1 slaved to gps. I could be wrong , i dont have the docs in front
Am Mittwoch, 9. Oktober 2013, 01:37:27 schrieb syd adams:
> Not sure what went wrong but i get this error consistently now:
>
> Nasal runtime error: props.setValue() with non-number
> at /media/FG/fgdata/Nasal/props.nas, line 29
> called from: __dlg:gps, line 20
> called from: __dlg:gps, lin
I will search for that. allways a segfault ? fg crash ?
2013/10/9 syd adams
> Not sure what went wrong but i get this error consistently now:
>
> Nasal runtime error: props.setValue() with non-number
> at /media/FG/fgdata/Nasal/props.nas, line 29
> called from: __dlg:gps, line 20
> calle
Not sure what went wrong but i get this error consistently now:
Nasal runtime error: props.setValue() with non-number
at /media/FG/fgdata/Nasal/props.nas, line 29
called from: __dlg:gps, line 20
called from: __dlg:gps, line 134
Segmentation fault (core dumped)
On Fri, Oct 4, 2013 at 1:48
Am Donnerstag, 3. Oktober 2013, 21:38:52 schrieb James Turner:
> On 3 Oct 2013, at 17:35, Dirk Dittmann wrote:
> > The improved-issue1164 is ready.
>
> > https://gitorious.org/fg/dirks-flightgear/source/778cc8c6a0abb88a1238850376ea2374358fd887:
> Thanks, looks good and pushed.
thx
>
> Unfortunat
http://wiki.flightgear.org/Talk:Nasal_Style_Guide
On Thu, Oct 3, 2013 at 9:38 PM, James Turner wrote:
>
> On 3 Oct 2013, at 17:35, Dirk Dittmann
> wrote:
>
> The improved-issue1164 is ready.
>
> https://gitorious.org/fg/dirks-flightgear/source/778cc8c6a0abb88a1238850376ea2374358fd887:
>
>
> Th
On 3 Oct 2013, at 17:35, Dirk Dittmann wrote:
> The improved-issue1164 is ready.
> https://gitorious.org/fg/dirks-flightgear/source/778cc8c6a0abb88a1238850376ea2374358fd887:
Thanks, looks good and pushed.
Unfortunately I now need to fix the route-path code to subdivide long legs
along the gre
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 na
On 1 Oct 2013, at 23:07, James Turner wrote:
> No, there's rules, since the codebase contains quite a mixture.
Whoops, typo. Meant to say,
'No, there's NO rules, since...'
James ;)--
October Webinars: Code for Perfo
On 1 Oct 2013, at 22:34, Dirk Dittmann wrote:
> I understand and will make the improvements. Thx for the hind ! I squash the
> commit and improve readability. Is there any code convention documentation ?
> Which I could read?
No, there's rules, since the codebase contains quite a mixture. We
Am Dienstag, 1. Oktober 2013, 21:37:58 schrieb James Turner:
> On 30 Sep 2013, at 08:47, Dirk Dittmann wrote:
> > branche fix-issue1164 @ my clone
>
> > https://gitorious.org/fg/dirks-flightgear/source/85592ec45db2866a15197c051d97cb4014537b4b:
> Hi Dirk, this is looking pretty good, just some sma
On 30 Sep 2013, at 08:47, Dirk Dittmann wrote:
> branche fix-issue1164 @ my clone
> https://gitorious.org/fg/dirks-flightgear/source/85592ec45db2866a15197c051d97cb4014537b4b:
Hi Dirk, this is looking pretty good, just some small nitpicks:
- please make a helper function for the great-circle XT
Am Montag, 30. September 2013, 12:52:08 schrieb James Turner:
> On 30 Sep 2013, at 12:29, Eric van den Berg
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 really great thing
> wo
on, 30 Sep 2013 12:52:08 +0100
To: flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] GPS - merge request
On 30 Sep 2013, at 12:29, Eric van den Berg
wrote:The other stuff I asked Dirk to add as it makes our extra500 (GPSS) AP
design a lot easier.
Incidentally if you
On 30 Sep 2013, at 12:29, Eric van den Berg 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 really great thing
would be to get the turn-anticipation code enabled. All the pieces are
On 30 Sep 2013, at 12:29, Eric van den Berg wrote:
> It actually does solve issue 1164 (which I started).
> When one switches to the next waypoint, the active leg course and
> x-track-error relate to the leg between the previous and active waypoint of
> the flightplan (as it should in LEG mode
@lists.sourceforge.net
Subject: Re: [Flightgear-devel] GPS - merge request
On 30 Sep 2013, at 08:47, Dirk Dittmann
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 configurable for the aircraft. The
Am Montag, 30. September 2013, 09:00:19 schrieb James Turner:
> On 30 Sep 2013, at 08:47, Dirk Dittmann 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 configurable for th
On 30 Sep 2013, at 08:47, Dirk Dittmann 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 configurable for the aircraft. The default
> is
> the same.
>
> /instrumentation/gps/c
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
/instrumentation/gps/con
21 matches
Mail list logo
