Hi,
On Wednesday, July 21, 2010 09:12:43 pm Dave wrote:
Yikes - is that ancient code still used? I thought it had been ripped
out long ago - I would certainly agree with disabling it by default. I
developed that code on Linux (gcc 3.x I think) and I've since discovered
with the kln89 code
On 28 Jul 2010, at 07:36, Durk Talsma wrote:
As a general plan of approach, I'll try to link the AI traffic gui settings
to
the AIModels system, and then bring back the ATIS and Frequency look up (if
still desired).
Frequency lookup and comm station handling should be doable using a new
Hi James,
On Wednesday, July 21, 2010 05:39:08 pm James Turner wrote:
My hypothesis is that something in the AI-Traffic code doesn't like being
re-positioned; if I reset/re-position very rapidly, I don't usually crash,
whereas if I wait 20-30 seconds at a location, before re-positioning, the
On 21 Jul 2010, at 18:47, Thorsten wrote:
My hypothesis is that something in the AI-Traffic code doesn't like being
re-positioned;
Maybe related to issue #133 in bug tracker:
http://code.google.com/p/flightgear-bugs/issues/detail?id=133
The AI code corrupts memory when the plane leaves
On 21 Jul 2010, at 19:37, Durk Talsma wrote:
My hypothesis is that something in the AI-Traffic code doesn't like being
re-positioned; if I reset/re-position very rapidly, I don't usually crash,
whereas if I wait 20-30 seconds at a location, before re-positioning, the
crash is much more
On Wednesday, July 21, 2010 08:42:49 pm James Turner wrote:
The old code. I'm going to try Thorsten's patches in #133, but a related
question - could we not make --disable-atcdcl the default? (I.e,
--enable-atcdcl instead)
I'm actually strongly considering this; however, the current
James Turner wrote:
On 21 Jul 2010, at 19:37, Durk Talsma wrote:
My hypothesis is that something in the AI-Traffic code doesn't like being
re-positioned; if I reset/re-position very rapidly, I don't usually crash,
whereas if I wait 20-30 seconds at a location, before re-positioning, the
7 matches
Mail list logo
