loop_n_roll

Thanks for the info. I'll continue my eval until time runs out.

Using the demo version for FSX I've found I can really mess up what I'm saying, but the program responds as expected. Have I set something wrong or will the program really respond to incorrect voice input?

Thanks,I'll give that a try.

I'm trying the demo for FSX. When taxiing to the runup area, VOX tells me I'll tune away to open the flight plan when I get to the runup; however, it tells me to contact tower for takoff clearance before I've called to open the flight plan. From then on it's out of sequence and I have to exit FSX to start over or just close the panel and fly without a controller. Similarly it tells me to exit the runway on landing and then has me contact ground before I exit the runway. If I don't get on it right away, it again freezes up.Any thoughts.

I hate to fan the flames; but I'm having a great time with FSX on a less than stellar system. I use the original with SP1 (haven't tried acceleration yet) and Ultimate Terrain X and really enjoy the flying. I've not turned on FS9 in over a month.I believe this whole problem is like the FDA releasing a new drug. They require test after test after test before a drug is released into the market. Then after millions have used it (far more than the few hundred involved in the "beta" testing) a small percentage of problems show up. While the percentage is small, since millions are now using the new product, the absolute number can be quite large even though the testing was perfect.So it is with programs: many problems won't show up until the product is released and millions of copies are sold. Further they have to work with an infinite combination of processors, motherboards, memory types, graphic cards, operating systems and add-ons. Yet we users expect them to all work the same and to perform perfectly on all combinations.Heck, it's a wonder they work at all.

While surfing I ran across a site that had plans for modifying a standard keyboard to work as a flight control console. I think it had "downloadable" and printable template you could lay over the keyboard. They charged about $9 for the download. Of course, I forgot to bookmark the folder and now I cant find it. Anyone know what I'm looking for?

I thought I'd posted this before, but cant find it. Please forgive if it's a double post.I'm thinking of getting the MegaScenery Phoenix package. What kind of frame hit can I expect with this kind of detail scenery?What other scenery package would you suggest to improve the entire North American continent?

Bell417,I've tried your settings with pretty good success; however, I'm unable to find the downloads mentioned in your message. Can you enlighten?

How does one take a picture of the FSX screen to post on the forum?

Anyone seen this. It's like a piece of jigsaw puzzle has been left out of the puzzle. Other pieces are in the right place, but not connected to the main puzzle. I tried to capture a picture without success.

Well I didn't think I had the blurries until I started reading this thread. Then I asked my wife, "Does this look blurry to you?" Guess what, she said, "Yes". Then I started looking harder. Even at slow speeds the blurries exist and I can see the scenery "catching up" as I fly past. My only solution is to fly with my glasses off. Hope this can be remedied.

I've searched and realize this has come up several times but is there any setting in a cfg file that will help me taxi straight?With 0 wind and weather and no control input most of my planes want to turn left then I over correct and take a snake-like path down the taxi way. I've tried calibrating the pedals (CH products) and increasing and decreasing the null zone to no avail.

Thanks. Found it.

In tips and tweaks there are references to the file fsx.cfg. I cannot find that file. Did SP1 take it away? Anyone know where it is.

Gerrit,I can't find the FSX.cfg file. I'm using XP home edition. Can you guide me to it? A search on the hard drive fails to find it.

Jeff,Thanks. Using your information I turned off the controller(s) and had a nice smooth taxi so it had to be the controller. I next realized I could set a null zone on the brakes and when I increased that only a little, the plane(s) began to taxi smooth. As many times as I've seen the null zone setting, I never moved it. Thanks for pointing me in the right direction

Ji,Thanks for the info.

When taxiing the default Mooney or Cessna I have to put in a lot of throttle to get it started. Then when I throttle back, it wants to come to a stop. It's hard to keep a smooth, constant speed. Any tips? Am I doing something wrong?Also, what view do most use to taxi? I find it difficult to guage turns and keep it on the center line.

I'm pondering adding 2 more 17" LCD monitors with the Triple Head to Go for use with FSX and sometimes with FS2004 and X-Plane. Should I consider the digital or analog version? Do all LCD monitors take a digital input? Your expertise is appreciated.

My hard drive has 2 partitions; one for programs and one for Flight Simulator. I had to reload Windows and in the process forgot that FSX stores some info in the Documents and Settings folder which was wiped out. Now I can't reload FSX. Get a message saying the setup.exe is not a valid 32 bit program. Help.

My last computer had 1gig memory and a 128meg video card. It could run FS9 at with all sliders at 100% with no difficulty. My newer computer has 2gig memory and a 256meg video card and I see no difference in FS9 performance. FSX is another story.

Jim, Thanks. I'm afraid you have far surpassed my meager abilities with your detailed reply. Think I'll wait for the new programs.

Actually, I'm pretty happy with mine and haven't flown FS9 since SP1 came out. I get good frame rates in detailed scenery areas and 30+ rates while flying at altitude. I don't run all sliders at 100%, but I'm happy.

Jim,Thanks. Is there a way to turn of the back course in FSX? AFCAD would do it for us in FS9 but how can it be done in FSX?

In FS9 the ILS would often capture the back course instead of the desired approach. I solved this by turning off the back course for the runway using AFCAD. Has this problem been solved in FSX?