>
> I still get the message from startup.nas at some airports. Here is an
> example at KLMO, home base for the real N7764P.
This should be fixed now.
Torsten
--
___
Flightgear
> Torsten Dreyer wrote:
> > Just commited a hack for envrionment_ctrl.cxx.
> >
> > It now waits for the first METAR to arrive before proceeding with the
> > initialization sequence. This prevents the nasal-dir-initialized signal
> > being fired before a METAR has arrived.
> >
> > I more and more li
Torsten Dreyer wrote:
> Just commited a hack for envrionment_ctrl.cxx.
>
> It now waits for the first METAR to arrive before proceeding with the
> initialization sequence. This prevents the nasal-dir-initialized signal being
> fired before a METAR has arrived.
>
> I more and more like the idea o
* Detlef Faber -- 6/23/2009 9:17 PM:
> Am Dienstag, den 23.06.2009, 14:25 +0200 schrieb Melchior FRANZ:
> > is now broken since Detlefs recent changes.
>
> I'm innocent on this. You sure meant someone else ;-)
Whoops, indeed, sorry. (That was probably because Torsten and
Detlef are both German f
Just commited a hack for envrionment_ctrl.cxx.
It now waits for the first METAR to arrive before proceeding with the
initialization sequence. This prevents the nasal-dir-initialized signal being
fired before a METAR has arrived.
I more and more like the idea of removing startup.nas and implent
Am Dienstag, den 23.06.2009, 14:25 +0200 schrieb Melchior FRANZ:
> * Tatsuhiro Nishioka -- 6/23/2009 5:01 AM:
> > I'm not so sure what it should look like, but at least it needs
> > nil check for the property.
>
> That would only be cosmetics and just hide the fact that the
> METAR runway choosing
* Tatsuhiro Nishioka -- 6/23/2009 5:01 AM:
> I'm not so sure what it should look like, but at least it needs
> nil check for the property.
That would only be cosmetics and just hide the fact that the
METAR runway choosing code is now broken since Detlefs recent
changes. The METAR wind direction/st
I've just changed line 12 to :
if (getprop("/environment/metar/base-wind-speed-kt") or 0 < 1)
return;
Dont know if that's a real fix , but it prevents an error message.
Syd
--
Are you an open source citizen? Join
Hi there,
On Jun 15, 2009, at 4:12 AM, Torsten Dreyer wrote:
>> I've had another error message for the last few weeks while starting FG ,
>>
>>
>> Nasal runtime error: nil used in numeric context
>> at data/Nasal/startup.nas , line 12
I've encountered exactly the same problem.
I'm not so sure wh
> I've had another error message for the last few weeks while starting FG ,
>
>
> Nasal runtime error: nil used in numeric context
> at data/Nasal/startup.nas , line 12
>
> so it looks like "environment/metar/base-wind-speed-kt" is still nil when
> read the first time ...
> I fixed it locally , bu
I've had another error message for the last few weeks while starting FG ,
Nasal runtime error: nil used in numeric context
at data/Nasal/startup.nas , line 12
so it looks like "environment/metar/base-wind-speed-kt" is still nil when
read the first time ...
I fixed it locally , but not sure who
11 matches
Mail list logo
