Hi All, After having discussed this issue with Martin privately, we have come to the conclusion that it is in the best interest of FlightGear to back out parts of this commit, and wait for an improved version. I had accepted the merge request, after I had concluded that Martin's original objections had been resolved, but that appears not to be the case.
I want to stress that we do see merit to the current patch, but note that there currently are still technical issues that need to be addressed before it is ready. To be more specific, the parts that I will remove are the Models/Jetways directory as well as the nasal files related to this system. I'm happy to accept a merge request where the issues addressed by Martin have been addressed. Cheers, Durk On 05 Jun 2011, at 08:04, Ryan M wrote: > On Fri, 2011-06-03 at 12:38 +0000, Martin Spott wrote: >> I'm feeling slightly uneasy with the current state because people don't >> get any jetways at all if they disable the flag in order to preserve >> performance. Personally I'd prefer a solution which keeps static >> jetways and just disables the animation if people feel like the need >> to. > > That sounds like a good idea. But it _might_ still cause FPS impacts. > Will have to run some tests later. > > On Fri, 2011-06-03 at 12:38 +0000, Martin Spott wrote: >> While I'm at it, I'd like to point to another, presumably more severe >> issue: The elevation of every of the animated jetways is hardcoded into >> the respective 'ICAO.jetway.xml' files. Now take into account that >> ground elevation is subject to change with almost _every_ rebuild of >> the corresponding region and airfield surface .... >>> From my perspective this calls for a more considerate solution. > > The only solution I can think of is to remove the elevation setting and > use Nasal to calculate the elevation for each jetway's > longitude/latitude. The only problem with that is that the calculations > would take into account the terminal buildings, which would cause > jetways appearing on top of the terminal roofs. > > ...however, I just had another idea. Making the elevations _relative_ to > the terrain instead of absolute. That means the current definition files > will have to be changed, but I can automate that with a script easily > enough. That also means I have to update my FG 2.0.0 version. > > > ------------------------------------------------------------------------------ > Simplify data backup and recovery for your virtual environment with vRanger. > Installation's a snap, and flexible recovery options mean your data is safe, > secure and there when you need it. Discover what all the cheering's about. > Get your free trial download today. > http://p.sf.net/sfu/quest-dev2dev2 > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
