On 7 May 2012, at 07:56, Renk Thorsten wrote:

> In a fresh pull of everything as of this morning, I lost the ability to 
> re-locate by choosing an airport from the list. Trying to do so results in
> 
> command 'presets-commit' failed with exception
>        message:invalid leg index (from FlightPlan::setCurrentIndex)

My fault, will take a look.

> 
> written to the console and the location stays where it is.
> 
> 
> In addition, my console is still flooded by a torrent of
> 
> Checking arrival time: ete 257573. Time to go : 4001. Track length = 110423
> (...)
> 
> arriving per frame, which makes it *very* hard to catch any meaningful debug 
> information. Could we please identify the subsystem from where the messages 
> originate and eliminate them - I'd really like to use the console for 
> debugging stuff, but this is outright impossible now.

Not seeing that here, strange.

The context is, I'm doing some major overhauling of the route-manager code, to 
expose everything to Nasal, and hence remove the amount we have hard-coded in 
C++. I pushed a large chunk last night, and I expect a bit of instability and 
maybe some odd behaviour while everything settles down again.

James


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to