I spent two hours planning a route, calculating fuel, and entering fixes into the INS.  Then pushback was accompanied by much smoke, shaking and doors flying open and shut.  It looked like Hellraiser 5: The Final Flight.

Then, of course, the airplane crashed.

After a little dance of frustrated anger accompanied by a few choice words and some brand new words I invented for the occasion, I tried again.  This time, however, I "repaired" pushback, whatever that is supposed to do.

The funny part is that the exact thing happened again.

So that's how my Columbus Day morning has gone.  I'm about ready to bathe the dog, or maybe try the route again in the Airbus X.

This was EGLL UK2000 Heathrow to Antalya (or was going to be).

How long is it sane to keep trying to fly when one problem after another keeps you on the ground?

Tim Capps wrote on Oct 11^th, 2010 at 4:47pm:

How long is it sane to keep trying to fly when one problem after another keeps you on the ground?

I wish I could help you Tim, but I have not had a single CTD in this plane yet. However, I dont mess with the INS, Doppler etc either, I just load a FS FP and let the AP fly it. I also added the default GPS from the FS 172 to help with nav, my only 'mod'

Just to be clear, this wasn't a CTD, but a "crash" with the airplane falling apart on the tarmac.

Funniest reading around, Tim. Congrats!

Only the last part with that Airbus confused me as this is one plane .. ah, not here, not yet.

Ok, I just tried the AES pushback and it worked fine. Make sure to reload the plane after you click "repair" in the config tool.
Only then the changed values get loaded and I recommend this repair option on all aircraft in your hangar. For details on it, check the AES manuals.
There isn't much to go wrong with this setting as the default cfg is saved before as backup.
Might be your crashing pushback was airport depended then, my repaired one here went flawlessly and smooth.

Nice poll, I've voted.

JayG, I think you are getting banned because you are using the default GPS on that classic plane.  ;D Just kidding.
Hoping to see you in the skies then, in style.

Tim Capps wrote on Oct 11^th, 2010 at 5:34pm:

Just to be clear, this wasn't a CTD, but a "crash" with the airplane falling apart on the tarmac.

Gotcha, I solved that problem years ago, I turned it off in FSX  :)

Cool, I had the avionic's upgraded to enhance my SA  :D

I think it might be a problem with the scenery.  Anyway, I managed to get underway without AES and everything was splendid -- until the flip over from waypoint 9.  I don't know what I had done wrong, but the distance was like 5554 miles, so I punted.

This is one airplane to separate the men from the boys.  This requires a lot of work to manage.  It can get fatiguing after awhile.

JayG wrote on Oct 11^th, 2010 at 5:09pm:

I also added the default GPS from the FS 172 to help with nav, my only 'mod'

I too have added this to my 707. I use it to get info on my arrival airport (I don't want to waste paper by writing it down, nor time to write it in notepad!) ATIS, Tower etc. and also for info on navigational aids (VOR etc.). It isn't cheating! :P

@Tim. Sorry that AES is giving you problems. I can't help you because I don't have it. I didn't vote in the poll.


Quote:

until the flip over from waypoint 9

I always put another waypoint (#1) beyond where I'm going. After waypoint 9 it will head for waypoint 1. I have had it try to return to my first waypoint, hundreds of miles behind me, because I forgot to tell it that waypoint 1 is somewhere ahead instead of the actual one I did use.

e.g. YMML - YSSY

DOSEL   S37.09.9  E145.23.7  #1
EBONY  S36.10.9  E147.04.2  #2
ARRAN  S35.50.3  E147.38.4  #3
NONUP  S35.25.8  E148.17.9  #4
CULIN  S34.44.4  E149.23.4  #5
TARAL  S34.30.1  E149.56.0  #6
RIVET  S34.16.8  E150.25.8  #7
RISOL  S34.13.2  E151.12.9  #8
SIZZL  S34.06.9  E151.13.2  #9
SY     S33.56.5  E151.10.8  #1

Usually. By the time I reach SIZZL, I have switched the A/P to LOC, or even G/S AUTO, but it is there in case I haven't

Mark

I had a 21-waypoint route from London to Antalya and it worked fine.  you just really have to pay attention to detail I think.

Tim Capps wrote on Oct 11^th, 2010 at 11:50pm:

I had a 21-waypoint route from London to Antalya and it worked fine.  you just really have to pay attention to detail I think.

OK. Now I'm a bit confused. Are you just saying that the next waypoint after 9 was because of incorrectly entered data and that you had sorted it out already? :-?

Mark

I don't know what the problem was; but I can now consistently handle long lists of waypoints.  I think I was making it harder than it needed to be.  One thing that helped was to make a list of waypoints: 1 through 9, then start over 1 through 9, etc.  Just put them in in order, checking them off as you enter them.  No mystery.

I changed the value in my config file.  If you look at your 707 in slew, it is hovering above the ground.  By lowering the value it drops it a bit and now AES can handle it.

static_cg_height=8

Now AES pushbacks are as smooth as glass.

Thanks for the info! Will try it out, because I also had some troubles with AES+707.  :)

I had the same shaking to pieces episode using AES.  I tried the repair option and believe I reloaded but I will try it once more to be sure and if not will then lower the CG as you suggest.

Thanks,
Robert