Haven't received a response..... too hard or not interested? Dene
Last month I posted this and got alot of comments back. I've experimented and have some extra information which may shed some light on the problem; I undertook this trip in the 172P Skyhawk (1981 model), 2D panel, a mammoth trip. I encountered the same sort of behaviour at varying intervals (about 2 hours) into the flight but because of either; better recovery charateristics or lower ground speed the autopilot was able to recover and continue. This enabled me to switch windows to the FGFS MSDOS window which I was unable to do once the aircraft had hit the ground with in either of the two previous aircraft tried. The FGFS window had these error messages. These occurred over a period of about 4-5 hours until I quit the flight due to running out of fuel!!!! Failed to untie property propulsion/c-thrust[0] Failed to untie property propulsion/engine[0]/reverser-angle Failed to untie property propulsion/c-thrust[0] Failed to untie property propulsion/engine[0]/reverser-angle Failed to untie property propulsion/c-thrust[0] Failed to untie property propulsion/engine[0]/reverser-angle Failed to untie property propulsion/c-thrust[0] Failed to untie property propulsion/engine[0]/reverser-angle Does this help explain the problem? Dene On Sun, 2005-10-16 at 22:15 +1300, Dene Maxwell wrote: > Just an observation that may be of interest; > > I can fly approx 1500Nm over water at 300kts and not have a problem... > reasonable graphics and even land successfully (any landing you can > walk away from is a good landing!!!). > > I can't fly approx 400Nm at 300kts over land without the aircraft > crashing about 300Nm into the flight. > > Some background > NZWN (Wellington International,NZ) to YSSY (Sydney-Kingsford-Smith, > Australia) 1484NM in a A10 Thunderbolt at 300kts cruise... flight goes > great. > > YSSY (Sydney- Kingsford-Smith, Australia to YBBN (Brisbane > International, Australia) 410NM in either an A10 Thunderbolt at > 300kts or Cessna 310 twin prop at 180kts crashes at about the 300NM > mark. > > Interestingly I can fly the A10 from YSSY out to sea, then due north > to parallel to YBBN then line up for a landing no problems, total trip > is about 500NM. > > The problem seems to be triggered by flying over land for a prolonged > period. In all cases the majority of the flight is undertaken under > AutoPilot control at variably 5,000 to 10,000 ft ASL. > > I have tried reducing the screen resolution from 1280x1024 to 800x600 > but it makes no difference. > > The platform is a 1.8Ghz P4, Windows Me, 256M RAM, nVidia GeForce2 > MX/MX400 video card (32Mbyte). > > Any comments would be gratefully received. > Dene, You didn't say which version of FlightGear you are using. Using Flightgear CVS, I flew from NZWN to YSSY as you suggested and apart from noting a missing tile (known bug usually due to an airport lying across a tile boundary) I didn't have any problems. YSSY to YBBN: I started flown this route and 300nm out from YBBN , I'm still flying. 300nm from YSSY, still here... Preparing to land at YBBN... Not the best landing but still down in one piece. A couple of possibilities The mostly likely cause is that you have found a bug in 0.9.8. FlightGear 0.9.8 has a few major bugs here and there. Solution: You can either upgrade to CVS (a tricky task under windows which involved installing cygwin) or wait for version 0.9.9. The other (albeit unlikely) possible is that it is something in your hardware or software set up. Could someone with similar hardware and OS comment on this cross country flight? My hardware doesn't match what Dene is using. (I am still thinking that the problem was to do with a 0.9.8 bug) George Patterson -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.0/167 - Release Date: 11/11/05 _______________________________________________ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
