PilotEdge Forums

I flew the I-10 on Monday (12/16), but apparently it did not record on PEaware. I checked each of my callsigns (in case I logged on incorrectly, DUH!) but the flight is not listed under any of them. I also remained connected to PE for about 15 minutes after completing the flight. Is there a problem with PEaware?

Henry

Hi Henry, the I-10 is tough on PEaware because of the destination change. I did alter your destination in the strip to SBP if memory serves (I was controlling during your nicely flown I-10 attempt), hoping that PEaware would catch it, but it sounds like it didn't.

No problem... I was just making sure I was not screwing something up. And, thanks for your help with the I-10. I was pleased with it... except on the initial inbound turn on the FLOUT5 departure when I tried to turn RIGHT to 040 as you instructed, but my autopilot (I'm pretty sure it's "possessed") decided I should turn LEFT... Always something! I'm hoping to fly the I-11 this afternoon.

With large heading changes, I turn the heading bug 40-60 degrees to the right to start the turn, wait a few seconds then dial in the actual heading that I want. Using that technique, it'll never second guess you and turn the other way.

Keith Smith wrote:With large heading changes, I turn the heading bug 40-60 degrees to the right to start the turn

...or more generically, you probably turn the heading bug 40-60 degrees in the direction you were instructed to turn, then dial in the actual heading after the turn gets started.

-M

Thx Mark! Yes, this really works better for right turns, which was the OP's case

Thanks for the advice Keith and Mark. I know that you have to move the bug progressively, and keep the initial moves relatively small until the turn is established. However, as I said, my autopilot is possessed! Sometimes, when I hold down a left-click on the HDG button (or repeatedly "tap" the button), the bug advances normally, but then makes a 40-60 degree jump... and, of course, this happens when (1) I'm flying a rating test, and/or (2) when my attention focuses on something else for a few seconds. Then, of course, I FRANTICALLY try to correct the error instead of just doing it in a normal fashion. ARRRGGGHHH! What can I say? I guess that's why I fly a computer instead of a r/w airplane!

Maybe, now that I've passed the I-11, I won't be quite so tense... thanks to all the controllers for their patience!

Hank,

You're getting bitten by a "feature" of the way many knobs turns are treated in FSX. When you hold down the mouse button for a direction (+ or -) for more than a couple of seconds, it accelerates the knob "turn" by a big factor (I don't know how much but it seems like a factor of 4-5 at least). Even clicking the mouse button to turn the knob left or right will invoke the acceleration "feature" if you click the button quickly many times in a row. There are two cures for the issue: (1) use the mousewheel for turning knobs, and move it the needed in small increments -- about 10 degrees at a time, then pause for a second and move it 10 degrees again, etc. (2) since I know you have a Saitek multi-panel try to use that for tuning and setting the OBS course rather than the 3D mouse knob. SPAD lets you set the acceleration factor with very fine levels of control so that you can get the OBS to move faster then normal when you really spin the knob, but it never goes out of control like you're describing -- each turn can be set to advance the OBS (for example) by about 20 degrees per turn of the nob instead maybe five degrees you get with acceleration set to zero. You sort of have to play with the acceleration factor for a bit, then once you've got a comfortable slow tune/fast tune setting that feels good, you never have to touch the acceleration slider again.

Thanks for the tip, Mark. I will definitely give that "hidden gem" a try.