So I was doing a FedEx run from my new SPIM scenery to my new KSFO scenery (REX uninstalled because my system is a bit on the (old) slow side. Cruising at FL350, and then started my decent, nothing exciting here with this baby until, at FL3250 or so, the plane started doing loops.:Silly:You read it right folks, loops, and boy were they a site to look at. I apologize, but I did not know how to capture it to replay it for you, but it would have been one heck of a sight.:Tounge:It went on for more than a minute, at which time I tried to intervene with no effect whatsoever. So basically, it was doing loops without loosing speed or altitude, and I had the contrails to prove it (no recording= only in my memory now).Heads up F-22 pilots, you would have been really jealous.You gotta love Microsoft right. I have seen quite a few quirky issues in the past with fs, but this one trumps them all.

FL3250

No wonder you were doing loops...(FL3250 is 325,000 feet for those who didn't catch that)Joking aside, that must've been crazy.

No wonder you were doing loops...(FL3250 is 325,000 feet for those who didn't catch that)Joking aside, that must've been crazy.

O.K. , try FL32.5 :Whistle:Yeah pretty crazy, and frustrating, as it was a long flight. I left it at cruise level in the morning and came back to it about 30minutes prior to decent. I even made sure I used the basic fsx "calm" weather so I would not come hope to any surprises.I know I know, I need to buy fsuipc to help smooth out the weather, but it will not happen until after (soon I hope, very very soon :() I get a new rig.

O.K. , try FL32.5 :(

It's just FL325. You drop the last two zeros (technically, divide by 100) and put FL in front of it all. Nothing too complex. FL32.5 would actually be 3,250'.

It's just FL325. You drop the last two zeros (technically, divide by 100) and put FL in front of it all. Nothing too complex. FL32.5 would actually be 3,250'.

Kyle, I was joking, but it is hard to show it online. I guess I chose the wrong emoticon.:wink:Thanks for the heads up either way.

Hi Waleed,That's a crazy one alright! At the risk of sounding unhelpful, I'd say there's not a lot we can do unless it happens to you again OR if someone else who has experienced this can chime in here. I certainly haven't seen that behaviour before.In saying that, I have (deliberately) barrel-rolled the MD11. Don't tell my chief pilot though. :(

Hi Waleed,That's a crazy one alright! At the risk of sounding unhelpful, I'd say there's not a lot we can do unless it happens to you again OR if someone else who has experienced this can chime in here. I certainly haven't seen that behaviour before.In saying that, I have (deliberately) barrel-rolled the MD11. Don't tell my chief pilot though. :(

Mark, I really doubt it is something that can be reproduced, or occur again easily. I believe it may be a one-off, but who knows.I have flown this baby (in pax form mostly) all over the place, and never encountered any serious issues (my "piloting skills" aside B)), so this was rather entertaining.I have been flipping between fs9 and fsx (slow computer, looking to build one in the next few weeks or so I hope :() for the past few months, and may have installed add-ons rather hastily this time around, and that could have something to do with it. I apologize if it sounds as a complaint post, as it was meant more for humor's sake.P.S. I do not fly "unprofessionally" like you mention in your last sentence :(, but rest assured that I will not complain to your chief pilot or the FAA at that.B)

I had problems with the elevators once, where they would get stuck in a fully up or down position , and the only way to rectify this was to apply full up or down pressure on the yoke. I found a solution, and that was to disengage both 'AFS ovrd off' switches on the glareshield (the two white ones below the 'Auto flight' button.) There is a downside to doing this, as it completely disables the Autopilot and Autothrottle until you turn both switches back on.

Kyle, I was joking, but it is hard to show it online. I guess I chose the wrong emoticon.:wink:Thanks for the heads up either way.

Yeah, my sarcasm often comes across incorrectly online, so I feel ya. I was just makin sure. I can't tell you how many times I hear "Center, Airline 123 with you FL100," when I'm controlling on VATSIM. My only thought is *Wow. Really? That's going to be somewhat difficult to get you down to land in the next 20 miles.* I'm sensitive to it I guess, since I hear it all the time.

Yeah, my sarcasm often comes across incorrectly online, so I feel ya. I was just makin sure. I can't tell you how many times I hear "Center, Airline 123 with you FL100," when I'm controlling on VATSIM. My only thought is *Wow. Really? That's going to be somewhat difficult to get you down to land in the next 20 miles.* I'm sensitive to it I guess, since I hear it all the time.

Kyle, I do not see that as sensitive since you have to deal with it online all the time. I joined VATSIM a short while ago, but am waiting to get a new system up and running before I get my feet wet, and give you folks some noob headaches here and there.P.S. I wonder what your comments might have included had this (Loops) happened in your sector :(

P.S. I wonder what your comments might have included had this (Loops) happened in your sector :(

All I see is a target in a 2D view, so the only thing I would possibly be able to catch is the descent indicator and a decreasing altitude. It's not in the picture, but would show where the "T" is shown on the second line of two of the data blocks in the picture (N191NC, for example has 240T251 in the second line, showing a temporary altitude assignment of FL240, while he's currently at FL251). If you reported having an issue, I probably would've just said something along the lines of "good luck" and "I'll keep the traffic clear."