Ray Hff

My flights tend to be short with most of my interest being in learning the flight characteristics of the aircraft. Probably the shortest was many years ago when I was learning helicopters. That great, now retired, site HoverControl had an add on for the Kallispell Montana Hospital. It has a helicopter pad in the parking lot and one on the roof. By flying from one to the other about fifty times, I learned helicopter landing. Average flight times were about 90 seconds. Short or long, FSX is entertaining.

Open FSX and look at: -Pilot Records -Logbook Also, if you search the Flightsim library for "logbook", you'll find a variety of programs for manipulating and displaying that information

Just search the library here and you'll find these castle files: Bavarian Castles Neuschwanstein And Hohenschwangau, Castle Of Beynac, Castle Of Beynac Fix, Seven Castles, Castles And Halls.

I don't have a clue after all of the above. Alternatively I did read this on another site: "Whenever I have seen this sort of thing, it was due to the elevator or ailerons being randomly assigned to some other joystick axis (in ADDITION to its normal assignment). I use the CH Products yoke & rudder peddles and when I make changes (which is rare), my computer has a bad habit of assigning random axis to the elevator or ailerons (the propeller pitch axes on the yoke gets assigned to the ailerons for example). Everything will function fine until you bump the pitch handle, and boom, it activates the control and the airplane flies out of control. And YES, you can have TWO axis assigned to the elevators for example (like the yoke and the prop pitch mixture lever). This means it may function normally for some time until you bump the other control also assigned to it - and then all #### breaks loose. You have to go to Settings/Controllers and check to see if they are assigned to more than one joystick axis. Not sure if this is your problem or if this will help."

It's likely the aircraft your using has an altitude bug that has to be set or an altitude entry that has to be made. When you start it's probably at zero and that's where it is trying to fly.

In my case, I purchased Windows 10 on a stick. Ran the installer. There were a couple really, really old games that refused to run on W10; but, FSX and 95% of everything else I had ran fine.

His FS9 drift gauge is interesting and also works in FSX.

Thank you for correcting the link.

Cockpit Commander is a tool that was made for FS9 but works just fine in FSX. As a pop up gauge, it really simplifies frequency entries, etc. See: https://www.flightsim.com/vbfs/fslib.php?searchid=79865946

The 50 and 60 Hz are screen refresh rates. In most cases, the media being transmitted is actually only playing at 24 FPS. Similarly a computer's screen refresh rate and a program's frame rate are often different. In my case, my laptop is set to refresh the screen at 40 FPS (Hz) and my desktop at 60 FPS; but, the frame rate, rate of change, for FSX is whatever I set it at. The screen refresh rate is still the 40 or 60. Some find FSX runs smoothly with the frame rate set at one half the computer screen's refresh rate.

For nearly all modern movies and scripted TV shows the standard rate is 24 frames per second.

I'll be with FSX for a long time to come. Three issues need to be defined for me to change: -Resolution of startup bugs -Actual incremental cost to change -Computer power actually required to run 2020 effectively (As for the last point, I don't want my next simulator to be another never ending exercise in tweaking.)

Interesting fly over: Istanbul

My first FS was on the Commodore 64. Here's an Eiffel Tower flyby.

Where do we find the high score?

You might be missing a wind layer. Working with weather, click on the advanced weather tab. Then, on the next screen click on the wind tab. There you can set one or even multiple layers of wind. Make certain the wind layer covers the altitude that you want it to. That might be it.

The system was set to stereo; but, I'm glad you mentioned it. Recently moved some things around and made a rookie mistake. Crossed a couple leads. Your mention of stereo made me go back and check the connections. Thanks. All better now.

I actually couldn't tell you because I'm uncertain how they were set up before. On the flip side, as far as I remember, changes made to past versions of Windows sound using the task bar sound link were not lost when you turned the computer off.

Following Windows 10 latest update, I lost all ATC and pilot voices. Checking just now, I discovered it also affects the Morse code identifiers. . Basically, when the computer is shut off, Windows 10 loses the latest sound mixer setting and this affects FSX. - A quick fix that works for me is: - Right click Speaker Icon on Taskbar Open Volume Mixer Click on Speaker Icon Click on the Advanced Tab Click on Restore Defaults - Then the voices and Morse code ID's work fine. - Until Windows has an update, this is the only fix I know of. - Please let us know if this works for you.

This thread is like a discussion with myself; but, I think I finally found an actual fix, but not a permanent solution. The things noted above seemed to work; but, that was not really so. After much trial and error, I found that the latest rendition of Windows 10 is resetting my sound every time I restart the computer. Every time I restart the computer now do this: -Right click Speaker Icon on Taskbar -Open Volume Mixer -Click on Speaker Icon -On Advanced Tab click on Restore Defaults Every time, after doing that, all works well. Even if I reset all the sound settings this way with Windows set-up pages, on the next restart, it will have to be reset again with the Speaker Icon on the Taskbar. Every time, this works; but why it doesn't restart correctly, I have not figured out. It is a fix, but not permanent solution.

Another day went by and I lost the voices again. I finally got the voice back and here's what worked. Took a copy of an old fsx.cfg file and restored the numbers in {PrimaryDevice} section of the current fsx.cfg file to those old numbers. It worked! How those numbers get changed I do not know.

For years I've run FSX with pilot's voice number 3 and everything worked perfect. Then one day, all voices stopped. After spending several hours trying many solutions, nothing worked. Then, this morning I switched to pilot voice 1 and the problem was solved. The voice response is back! Why, I don't know. Go figure?!?!?!? For the OP to this thread here are all the other solutions I found online and tried. None worked for me. Of all of these, maybe one will work for you. -Made sure your sound driver is up to date. -Made certain default communication was set to the default driver. -Made certain the the Microsoft Flight Simulator X/Sounds/ATC folder still held the USEnglishBig.gvp file. -Set the Voice volume to 100%. -Open Control Panel/Sound/Communications, Choose the "Do Nothing" option. -In Windows Sound and Audio devices, checked that Sound playback and Sound Rec under Audio use the default device (soundcard) and the same for Voice. I don't now why the pilot voice change worked but I'm glad it did. Hopefully one of these solutions will work for you.