* 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
