KevQA

Thank you so much for this explanation. I was wondering what all the flurry of DX10 threads were about. Several kind members of AVSIM pointed me to Steve's site and I installed his DX10 fixes. The performance increase was outstanding, especially when using Word Not Allowed's tweaks and getting the NVIDIA inspector settings good. I have many FSDT airports and I love flying at night, so the fact that night textures did not work at these airports was the deal breaker for me and I went back to DX9. However with the significant performance increase I got, I am considering uninstalling these airports and going back to the original FSX ones. If the developers could release a service pack to update the night textures, I would switch back in a minute.

Your right. The EFB uses SimConnect and not FSUIPC.

I started having this problem as well. It all began when I followed AOA's advice to delete all the keyboard shortcuts in FSX and create profile specific assignments in FSUIPC for the 737NGX. If my joystick and throttle disconnect, I just go into FSUIPC, click on Joystick Calibration, click the profile specific button, and select my NGX profile and everything comes back. Not sure what is happening but it seems like AivlaSoft's EFB is disconnecting and reconnecting to FSUIPC a lot as well. Using Windows 7-64 bit.

Thanks for this Paul! I am so 2011. I had no idea this was even going on. I went over to Steve's site and did some reading. I downloaded his latest zip file from avsim (3.2.2 it think). Installed it, selected DX10 in FSX. Updated my inspector settings from another post here at Avsim and ran my fsx.cfg through Bojote's tool and voila! Outstanding graphics and performance. I am going to go do a flight and see how it goes. Then I will probably start tweaking my fsx.cfg per Word Not Allowed's guide. Just for information, I am using a GTX470 and all seems good so far. Thanks for bringing me up to 2013, lol!

Your configuration is fine. You have DX11 installed on your computer. Make sure that DX10 is not checked in Flight Simulator and it will be using the "DX9" functions of DX11. You can always have a later version of DX installed.

You should never have DX10 selected in FSX. See this thread here: http://forum.avsim.net/topic/324786-nvidia-configuration-guide-inspector-2xxxx-drivers-version-20-explanations-of-all-settings/

As Ahmed said above, you should check you LOD setting in fsx.cfg. A lot of people changed this to around 6.5 and can cause you to run out of memory. You may also want to run your fsx.cfg file through Bojote's Tweaking and Tuning tool for FSX here: http://www.venetubo.com/fsx.html. That should fix you right up!

This post here should be able to help you out: http://forum.avsim.net/topic/324786-nvidia-configuration-guide-inspector-2xxxx-drivers-version-20-explanations-of-all-settings/

You should not be using DX10 by checking the box in FSX. It was a preview version and should not be used. Please see this post here: http://forum.avsim.net/topic/324786-nvidia-configuration-guide-inspector-2xxxx-drivers-version-20-explanations-of-all-settings/

From what I understand, you are never supposed to use DX10 in FSX. It is a preview version only. Please see this post here: http://forum.avsim.net/topic/324786-nvidia-configuration-guide-inspector-2xxxx-drivers-version-20-explanations-of-all-settings/

+1 for this! I had completely forgotten this. Too much time in airliners with FMC's :Thinking:

I am stuck with button control because I have previously run System Mechanic. This does something to Windows 7 that prevents FS2CREW voice from working, although the rest of Windows speech recognition works. In addition, I had also used the Windows 7 SP1 cleanup tool. Because I have used the cleanup tool, I cannot remove SP1 and therefore cannot do an "upgrade" install of Windows 7. Only fix: Complete "fresh" install of Win 7 64.

Nevermind. I called PayPal and gave them an earfull. They should be releasing my funds to you Bryan.

I purchased this morning and now paypal disputed the charge and asked me to change all my security information. My FS2CREW account shows up as refunded and I did not request a refund! Any idea what is going on?

You wont. I pulled 45 positive G's coming out of the dive after getting the Mach 1 achievement in the P-51.

Looks like the first jet was just announced too. Dessault Falcon 2000S :Hypnotized:

Right here: http://forum.avsim.net/tutorials/article/21-adjust-joystick-sensitivity/

That is correct. All the mission times in Flight are based on using the skip to next waypoint feature. We tried to get them to fix this in beta or at least also provide the non-skip time as a lot of people like to fly the entire flight. Yes, it took me about 4 hours as well. I think you will be happy with the xp though if you don't skip to any waypoints!

Try this:http://www.microsoft.com/games/en-US/Support/Pages/signinIssues.aspxYou have to have a windows live account AND and xbox account in order to use flight.

See Arwen's post here: http://forum.avsim.net/tutorials/article/23-differential-braking-with-joystick/

Also, if you have or get the Maule, use the checklists the first few times becuase the Maule has a -7 degree flap position that is used (in addition to others).

110.6 is a frequency for the McGuire VOR and has to be tuned on a NAV radio, not a COM radio.At some airports (more frequent outside the US), ATIS may be located on a navigation radio frequency. Unfortunately, MSFS does not allow for voice over NAV frequency equipment. It is also quite common, even in the US, to have broadcasts (TWEB, HIWAS) over VOR frequencies as well as communications with flight service personnel.You just have to pretend with this airport unless you are using something like radar contact where you can get the information.

Same here. And I flew pretty much during the same time period.

Absolutely outstanding tutorial Ryan. I always wondered what to do with all that weather data and I purchased TOPCAT this morning just to use with your tutorial.After flying with no weather, I launched another tutorial flight using AS2012 and had significant cloud cover and fog pretty much down to the runway. I had noticed that RWY 26 appeared to have glideslope information during the first visual flight so I set up for an autoland. I am sure all you experienced pilots know what happened next. Yes, I got fired as a PMDG 738 pilot because I landed about 60 feet to the left of runway 26 after destroying the lights, the antenna, and a whole lot of grass. Needless to say I turned my PMDG over to the maintenance team for a full airframe inspection.I learned a valuable lesson today in addtion to everything Ryan taught me. Read and understand the charts and all the quirks about the airport!What I failed to recognize is that when flying by IFR you can make a LLZ/DME approach from either west or east, both take you down the valley. Once in the valley, a final Visual Approach Procedure is required before landing. For both LLZ/DME approaches there exists a visual procedure for a rwy 8 and rwy 26 landing. Due to terrain in front of rwy 8, a straight-in landing is only possible at the east approach on rwy 26 (LLZ offset 5° from runway). The most difficult one is the west approach rwy 8 landing that requires two visual right turns at about 180° in the valley before landing. Landing on rwy 8 from either LLZ/DME approach is difficult because it is almost impossible to keep visual contact with the rwy during the right-hand circuit (in larger planes). NOTE: The LLZ/DME 26 is simulated as ILS/DME in FSX because you have glide slope available on some of the approach.Thanks again Ryan for all your hard work and hopefully I will get my NGX back from the maintenance team soon!

You can also zoom using the mouse wheel. You can find aerocaches from miles away doing that!