On Wed, 2011-09-28 at 09:09 +0100, James Turner wrote:
On 25 Sep 2011, at 09:10, James Turner wrote:

>> 2. After about 1hour of flying, FG seems to go into a endless loop; the sound continues to play, however the screen is frozen (goes to black if you minimise then re-maximise it), and all network activity drops off (ie: you disappear from multi-player)
>>     I ran it with gdb and notice the following stack;
> We've seen issues like that before, when _geo_inverse_wgs_84 is used over large (eg, half the planet) distances. The workaround / fix has been to switch range checks of this nature to convert coordinates to cartesian space (earth centred) and then use cartesian distance - not appropriate for navigation, but fine for a range check (and quicker too).

I just pushed a tweak to make this code work in cartesian space, thanks for the bug report.


Thanks James, that looks like it fixed that up, I re-flew the same route and no problems.


All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
Flightgear-devel mailing list