> Not quite sure about the sim itself, but I believe the sim isn't waiting > for valid METAR before selecting the start-up runway (or it has a timeout > and doesn't always wait long enough). This should work. I moved the logic from startup.nas into the initialization sequence to use the same code as the AI system and to avoid opposite runway assignment for AI-traffic and the aircraft. The logic behind is, that if the FDM has been initialized, METAR requests are handled by a worker thread. During initialization (and reset), as long as the FDM is uninitialized, the weather controller waits for a METAR response before it continues.
Setting log-level to info should spit out something like NoaaMetarRealWxController::update(): spawning load request for station-id EHAM followed immediately by NoaaMetarRwalWxController::update() received METAR for EHAM: (metar text here) Do you remember the METAR you received, your runway and the active AI runway? Torsten ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
