Ray Hff

When the 100,000 pound aircraft they're flying is headed toward the ground at 140 knots or so, they probably feel much better being in total control.

See: https://www.usatoday.com/story/travel/columnist/cox/2014/08/11/autopilot-control-takeoff-cruising-landing/13921511/

I have no other idea.

I'd try these settings: Under Settings - Controls, Calibration: Sensitivity and null zone Simple Controls Sensitivity - all axes: 127 Null Zones - all axes: 1 Keyboard Sensitivity Set all, ailerons, rudder and elevator, to 64 And, Under Settings Realism Flight Model Set all 5 parameters to the maximum "realistic"

I'm really not sure; but, looking at the default A321 panel.cfg, you might experiment by eliminating the line "child_3d=1".

You can add one or more points to a GPS routing by using Flight Planer entry rather than GPS entry. 1. From the Free Flight screen, click on Flight Planner. 2. Enter your origin and destination. 3. Click on Find Route. 4. On that screen, using your mouse, drag the route line on the map to near your next point (it only has to be close). 5. Then on the righthand side of the screen, double click the waypoint you just entered in order to open the Edit Waypoint screen. 6. From there you can numerically edit the coordinates to the exact location you want and give it a name. 7. Click on okay on both that screen and the next screen. 8. Save your route. When you go fly, the multiple point route will be in the GPS.

The process for whatever gauge you're interested in would be the same as what you just did for the Boeing autopilot. If you want to learn more, this might help: https://docs.microsoft.com/en-us/previous-versions/microsoft-esp/cc526956(v=msdn.10)?redirectedfrom=MSDN

I would try changing the first line to: BACKGROUND_COLOR=0,0,0 And, changing the last line to: gauge00=B737_800!autopilot, 5,5,350,70

I use Microsoft Edge. As a test I downloaded a file 5 minutes ago and had no issues. It worked fine.

Not sure; but, might have.

Found it, thanks to your question about the scenery.cfg. file. Thank you. I thought it was fine; but, that was not so. Upon review, this section: [Area.115] Title=Addon Scenery Local=Addon Scenery Layer=115 Active=TRUE Required=FALSE Was totally missing. All the sections were there in numerical sequence except this section was totally missing. Sections from start to 114 were there and sections from 116 to the end were too. I manually put it back in and all's well. My only question now is what did I do that caused that? I'll need to think a lot about that.

To be precise, this is FSX Acceleration that I am using. All of my scenery, original and many, many add-ons are in place in the correct directories. All of my scenery functions perfectly except that which is driven by the bgl files in this directory: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Addon Scenery\scenery When any files are added to or removed from that directory, FSX is supposed to pole the directory and register what is there. Now, following any change in that directory, it appears to be ignored by FSX and FSX at this point recognizes nothing in that directory. All my regular scenery, both default and add-on scenery, works fine. Files in the noted directory do not. The add-on directory contains over 200 sub-directories and they all work. The problem directory contains over 100 of which all used to work. They're still there but they go unrecognized by FSX. And yes, the scenery.cfg is intact. PS I've been at this for more than a decade and it's the first time I have had this issue.

While I've had good look with add on scenery over the years, all of a sudden FSX stopped using any of the bgl files in the scenery directory: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Addon Scenery\scenery Any thoughts?

The free version is here: https://www.fsrealwx.de/index.php/downloads/archive/fsrealwx-lite

The real weather in FSX is no longer supported. Your only option is to download an add on such as FSRealWX or something similar. FSRealWX is at: https://www.fsrealwx.de/

It's somewhat peculiar that a debate rages about the value and sustainability of FSX when even FS2004 is still viable as evidenced by 41 new files having been uploaded here in just the month of June alone!

There's an old saying in the industry that I spent a lifetime in. Putting it to use in my personal life has saved a fortune. In my life, the same applies to FSX. It is: "Use it up. Wear it out. Make it do or Do without." Following that advice is like money in your pocket!

I've been with FSX since the beginning and all of its predecessors before that. With a strong compliment of added aircraft and added instrumentation, it is en excellent flight simulator that I'm sure I'll use till the my computer fails. It's hard to beat as a flight simulator for flying and for gaining an understanding instrumentation and navigation. For those rare times when I want to look at things, I forgo FSX in favor of Google Earth's new "on the web" experiment. It's a great sight seeing simulator.

https://www.faa.gov/regulations_policies/handbooks_manuals/aviation/phak/

I don't know if any of the aircraft have the call out triggered by that; but, on many a light will come on on the dial when dropping below the bug's altitude.

Miatamariner, thank your for your astute response. There was a small but significant change in the later cab file. Problem solved! I appreciate you help, Ray

Thanks for checking. 1.8 is the one I'm using so I've got something else going on.

I like this GPS. It's very clever; but, I ran into one snag. On the "Nearest" screen, after clicking the "direct to" block, it turns green and the red box appears for the ICAO code entry; but, the gauge will not allow any entry. Conversely, by tabbing over to the Airport side, it does accept airport names. Any thoughts?