[Flightgear-devel] Fwd: Generic Autopilot works by location?
Hey all, I am finding the Generic Autopilot either works as expected, or loads with unchangeable data, depending on spawn location. I seem to recall some discussion about a location dependent bug, but I thought it was related to weather. (?) FlightGear v2.0 8/21/2010 snapshot from Tat's site. Any aircraft without a purpose built AP seems to be affected, based on the number I've tested, but for these locations listed I was using the popular MD-81 from Gary Neely's website. Airports to the north and to the south are working, where the middle area is not. Working locations tested: To the south - Kathmandu, Nepal, San Antonio, TX; Orlando, FL, and Key West, FL To the north - Rost, Norway; Montreal, QC Non-working locations seem to be anything across the middle third - Burlington, VT (just across the border from Montreal) Atlanta, GA Charles De Gaulle, Paris, France EHAM KSFO What I don't know yet is if this related to latitude/longitude, the airport itself, or something outside of that. But the data at the moment presents itself as a lat/lon issue. In a non-working location bad data consists of a default speed in the 13,000 range, alt hold in the 33,000 range, and headings from 130 - 550 degrees. These values can not be changed by the user. Often the headings and speed values are constantly climbing. A valid working location typically loads with 0 for heading and speed, and a single digit value for altitude hold. These are then changeable. Can anyone enlighten me on it? Thank you, Peter Brown Does no one have information on the Generic Autopilot only working above or below certain latitudes? -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: Generic Autopilot works by location?
Hi Peter, I can't think of any reason the basic autopilot functionality would be tied to a particular location. Could you provide a specific aircraft and airport (i.e. command line options) that tickle this bug? Perhaps it's something with your local build? Perhaps it's something really obscure that no one else has noticed? Thanks, Curt. On Mon, Jan 3, 2011 at 1:28 PM, Peter Brown wrote: Hey all, I am finding the Generic Autopilot either works as expected, or loads with unchangeable data, depending on spawn location. I seem to recall some discussion about a location dependent bug, but I thought it was related to weather. (?) FlightGear v2.0 8/21/2010 snapshot from Tat's site. Any aircraft without a purpose built AP seems to be affected, based on the number I've tested, but for these locations listed I was using the popular MD-81 from Gary Neely's website. Airports to the north and to the south are working, where the middle area is not. Working locations tested: To the south - Kathmandu, Nepal, San Antonio, TX; Orlando, FL, and Key West, FL To the north - Rost, Norway; Montreal, QC Non-working locations seem to be anything across the middle third - Burlington, VT (just across the border from Montreal) Atlanta, GA Charles De Gaulle, Paris, France EHAM KSFO What I don't know yet is if this related to latitude/longitude, the airport itself, or something outside of that. But the data at the moment presents itself as a lat/lon issue. In a non-working location bad data consists of a default speed in the 13,000 range, alt hold in the 33,000 range, and headings from 130 - 550 degrees. These values can not be changed by the user. Often the headings and speed values are constantly climbing. A valid working location typically loads with 0 for heading and speed, and a single digit value for altitude hold. These are then changeable. Can anyone enlighten me on it? Thank you, Peter Brown Does no one have information on the Generic Autopilot only working above or below certain latitudes? -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/http://www.flightgear.org/blogs/category/personal/curt/ -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: Generic Autopilot works by location?
On Jan 3, 2011, at 2:37 PM, Curtis Olson wrote: Hi Peter, I can't think of any reason the basic autopilot functionality would be tied to a particular location. Could you provide a specific aircraft and airport (i.e. command line options) that tickle this bug? Perhaps it's something with your local build? Perhaps it's something really obscure that no one else has noticed? Thanks, Curt. On Mon, Jan 3, 2011 at 1:28 PM, Peter Brown wrote: Hey all, I am finding the Generic Autopilot either works as expected, or loads with unchangeable data, depending on spawn location. I seem to recall some discussion about a location dependent bug, but I thought it was related to weather. (?) FlightGear v2.0 8/21/2010 snapshot from Tat's site. Any aircraft without a purpose built AP seems to be affected, based on the number I've tested, but for these locations listed I was using the popular MD-81 from Gary Neely's website. Airports to the north and to the south are working, where the middle area is not. Working locations tested: To the south - Kathmandu, Nepal, San Antonio, TX; Orlando, FL, and Key West, FL To the north - Rost, Norway; Montreal, QC Non-working locations seem to be anything across the middle third - Burlington, VT (just across the border from Montreal) Atlanta, GA Charles De Gaulle, Paris, France EHAM KSFO What I don't know yet is if this related to latitude/longitude, the airport itself, or something outside of that. But the data at the moment presents itself as a lat/lon issue. In a non-working location bad data consists of a default speed in the 13,000 range, alt hold in the 33,000 range, and headings from 130 - 550 degrees. These values can not be changed by the user. Often the headings and speed values are constantly climbing. A valid working location typically loads with 0 for heading and speed, and a single digit value for altitude hold. These are then changeable. Can anyone enlighten me on it? Thank you, Peter Brown Does no one have information on the Generic Autopilot only working above or below certain latitudes? -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/ I will put together more information. Thank you, Peter-- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
