From: Vivian M. <viv...@li...> - 2011-01-11 19:34:00
|
ThorstenB, I don't use EHAM all that often, but the frame rate with your update was a very acceptable 45 fps in general, with 23 looking at the terminal area. Knowing how heavy the ground detection code is, this has to be an improvement. I haven't seen an problems so far, although I'm not sure why my aircraft was instantiated at one end of the runway, while the whole of KLM was taking off from the other. Perhaps we have a mismatch in the runway selection code, but that would have nothing to do with this update. I would call this a good update. Vivian -----Original Message----- From: [mailto:br...@gm...] Sent: 10 January 2011 20:55 To: FlightGear developers discussions Subject: [Flightgear-devel] AI traffic performance update Hi, I've pushed a tiny update for AI traffic to flightgear/next. It improves performance at airports with busy AI traffic by avoiding repeated elevation/scenery checks for stationary aircraft. On my system this means a considerable frame rate improvement at EHAM (many AI aircraft parked at a gate). The improvement takes effect a short while after you started or got close to an airport. Once the parked AI aircraft have positioned and checked the scenery elevation, frame rate should improve. As a side effect, the update also changes (but doesn't fix) the behaviour of a bug (#221) concerning multiple aircraft occupying the same parking position: such models no longer climb upwards to infinity, but just remain idle and stacked on-top of each ( Bremer Town <http://en.wikipedia.org/wiki/Town_Musicians_of_Bremen> Musician's style :) ). A bit better than before. Unfortunately Durk isn't available for review. So let me know if you noticed any new problems related to stationary AI aircraft. Likewise if you see improved performance. If there are no new issues and it turns out to be an improvement for more people, we might add this to the release branch too. Otherwise we'll need to wait for Durk's AI expert advice. cheers, Thorsten |