Re: [Flightgear-devel] startup.nas
> > 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-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup.nas
> 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 of removing startup.nas and implenting the > > automatic runway selection depending on METAR wind directly in the > > METAR-subsystem, probably enabled by a property. > > > > I didn't mark the hack as "temporary" because temporary solutions usually > > last longest ;-) > > > > For now, the message from startup.nas should have disappeared and > > automatic runway selection based on METAR wind should work again. > > > > Torsten > > Hi Torsten, > > I still get the message from startup.nas at some airports. Here is an > example at KLMO, home base for the real N7764P. Yep - me, too for KLMO. I'll look into soon. Torsten -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup.nas
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 of removing startup.nas and implenting the > automatic runway selection depending on METAR wind directly in the > METAR-subsystem, probably enabled by a property. > > I didn't mark the hack as "temporary" because temporary solutions usually > last > longest ;-) > > For now, the message from startup.nas should have disappeared and automatic > runway selection based on METAR wind should work again. > > Torsten > > Hi Torsten, I still get the message from startup.nas at some airports. Here is an example at KLMO, home base for the real N7764P. [...@dadsoffice data]$ ./bin/fgfs --airport=KLMO --aircraft=pa24-250 --fg-scenery=/home/dad/scenery --enable-real-weather-fetch FGMultiplayMgr - No receiver port, Multiplayermode disabled Nasal runtime error: nil used in numeric context at /usr/local/games/FlightGear/data/Nasal/startup.nas, line 12 called from: /usr/local/games/FlightGear/data/Nasal/startup.nas, line 29 KI266 dme indicator #0 initialized Nasal Electrical System Initialized fgfs and SimGear updated from cvs yesterday. Regards, Dave P. -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup.nas
* 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 first names which aren't used in Austria. :-) m. -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup.nas
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 implenting the automatic runway selection depending on METAR wind directly in the METAR-subsystem, probably enabled by a property. I didn't mark the hack as "temporary" because temporary solutions usually last longest ;-) For now, the message from startup.nas should have disappeared and automatic runway selection based on METAR wind should work again. Torsten -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup.nas
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 code is now broken since Detlefs recent > changes. I'm innocent on this. You sure meant someone else ;-) > The METAR wind direction/strength is now published too > late for startup.nas, so an aircraft isn't positionend on a > proper runway if METAR is used. *This* is the problem that needs > to be fixed, not the Nasal error message. > > startup.nas is/was a bit hackish, anyway. A proper solution > would be to wait for the METAR wind and only then to set the > runway and FDM. This would require to initialize the environment > subsystem earlier. Then we could also drop the additional > "presets-commit" and save some startup time. startup.nas could > be dropped altogether. > > m. > > -- > Are you an open source citizen? Join us for the Open Source Bridge conference! > Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. > Need another reason to go? 24-hour hacker lounge. Register today! > http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup.nas
* 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/strength is now published too late for startup.nas, so an aircraft isn't positionend on a proper runway if METAR is used. *This* is the problem that needs to be fixed, not the Nasal error message. startup.nas is/was a bit hackish, anyway. A proper solution would be to wait for the METAR wind and only then to set the runway and FDM. This would require to initialize the environment subsystem earlier. Then we could also drop the additional "presets-commit" and save some startup time. startup.nas could be dropped altogether. m. -- Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup.nas
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 us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup.nas
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 what it should look like, but at least it needs nil check for
the property.
Another solution can be setting 0 to the property at the beginning.
setprop("/environment/metar/base-wind-speed-kt", 0.0);
before set_runway_from_metar_wind() is called.
Melchior, what do you think is the better solution for this?
Tat
>>
>> 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 added it , so I'll leave it alone
>
> That's my fault for sure. This node is not initialized before a valid metar
> has been decoded. The boolean property /environment/metar/valid is true if
> the properties under /environment/metar are filled from a valid metar.
> So - if a valid metar has not (yet) been received from noaa, there is no
> wind-speed and no wind-range.
>
> Probably startup.nas should wait for /environment/metar/valid to become true
> before using the wind-speed and wind-range nodes.
>
> Maybe Melchior has a good idea how to do this?
>
> Torsten
>
>
>
>
>
>
>
> --
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup.nas
> 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 added it , so I'll leave it alone That's my fault for sure. This node is not initialized before a valid metar has been decoded. The boolean property /environment/metar/valid is true if the properties under /environment/metar are filled from a valid metar. So - if a valid metar has not (yet) been received from noaa, there is no wind-speed and no wind-range. Probably startup.nas should wait for /environment/metar/valid to become true before using the wind-speed and wind-range nodes. Maybe Melchior has a good idea how to do this? Torsten -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] startup.nas
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 added it , so I'll leave it alone -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
