Hi James,
On 24 Apr 2012, at 11:13, James Turner wrote:
Well, the main thing needed is to break apart the 'finishInit' into more
steps, to avoid the remaining pause. I think that can be done by traversing
the scheduled aircraft list in batches.
Just as a quick heads up; I didn't have a
On 25 Apr 2012, at 08:15, Durk Talsma wrote:
1). On my machine I'm actually experiencing an extremely startup during the
reading airport/nav data stage (~up to minute or so). This usually only
happens when I try to load flightgear for the first time. Once these files
are buffered
Just so people know, I made a change to how AI traffic is started (so you can
ignore this email if you run with traffic turned off) to avoid the long pause
during 'initialising subsytems' when all the XML schedules are parsed and
loaded.
This has a few effects - the app doesn't go unresponsive
On 24 Apr 2012, at 10:24, James Turner wrote:
This is still at the 'hack' state, it's be trivial to revert to the old
method.
I'll have a look at it later today. I guess this change was slowly but
increasingly becoming necessary. I'll let you know if I see any undesirable
side effects.
On 24 Apr 2012, at 09:45, Durk Talsma wrote:
I'll have a look at it later today. I guess this change was slowly but
increasingly becoming necessary. I'll let you know if I see any undesirable
side effects.
Well, the main thing needed is to break apart the 'finishInit' into more steps,
to
5 matches
Mail list logo
