leee wrote: > On Thursday 15 Oct 2009, Martin Spott wrote: > >> Pete Morgan wrote: >> >>> Glad you picked the 787, this is broken in CVS with all sorts >>> of errors.. thats why We need an aircraft fault list... >>> >> I would not call it "broken", instead, call it "incomplete". To >> my opinion we're never going to have any aircraft in FlightGear >> complying with the term "finished", there will always be features >> missing, simply because it's just a simulation. >> Maybe we need a certification, so all featured are checked, then rechecked. (this could be automated) Ie a list that goes down and what is complete and not complete atmo. simply because of change in "base code", whatever that is..
>> Having different levels of "completeness" is the nature of Open >> development and I'm pretty much convinced that the respective >> authors are well aware of the deficiencies, as they already did a >> lot of research on the respective type of aircraft. >> If you think that a "fault list" is going to motivate more >> developers to jump into improving the fleet, then please go ahead >> and start compiling such list, including detailed or at least >> reasonable reports about what's missing - "all sorts of errors" >> is insufficient - and, at best, how it should be improved. >> >> Cheers, >> Martin. >> Cool, Martin, and kinda agree. Indeed I am checking that process. At least a Brute force "attack the problem", might mean actually "freezing" the whole fleet in autopilot, then fixing them all easily, eg from prop/tree > > > I think you need to accept that many aircraft are indeed broken, and > most have been broken by software changes made since the aircraft > was released. It is not just a case of aircraft being incomplete > or incorrectly configured in the first place. > Indeed having an "unmainted list", and a "needs help" list might be useful. (that ia another issues, however I might be an autopilot expert soon, maybe) If thats a problem, then that is a challenge I'm prepared to address and identify. So at least I can replicate some simple AP functions on my virtual "generic" flight deck. Ie in my instance I need to select some aicraft, mainly modern and glassish, where autoilot and nav (another issue) works.. So what I'd like to do analyse and identify the problems, then fix them. If this means writing a wriggling python script and checking values by snaking each aircraft automatically somehow. eg Some aircraft cant have autopilot, or limited X capabilites.. Can I suggest a wiki page or indeed could be a fg-autopilot.google-code just for its issues list for now so me can solve le problema..? Indeed I'm trying to create a document which is a "synopsis" of it all. At its various levels from code, to comments on the mailing list, and a muppet like me as a junior pilot. I'm up for it, because I need it :-)) ie identify the autopilot problems. Pete > Sadly, while no consideration is given to backwards compatibility > i.e. by allowing different versions of sub-systems to be used by > specifying a version in the appropriate config file, broken > aircraft will remain a feature of FG. > > LeeE > We can only go forward.. > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > Does Flightgear work on a blackberry, and is it plane I can fly at a conference from a blackberry ? (ATC) ;-) > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
