novacane

Post the routes and runways you used on the two recent flights you tried after the hotfix.

Is your airspeed fluctuating while this is happening or is it just deciding to climb out of the blue?

There is a reset button at the center of the mins knob. It should set it to 200, however, I haven't gotten the 20000 bug so I don't know if it will actually work. Headsets are only $20 and it is well worth the experience.

I use it so I don't have to use 2d panels and I find using the hat switch or mouse too clumsy and slow to look around with. But ya, it is less helpful in a airline sim than a combat sim.It also makes flying in the pattern much easier too.

I can grantee that one of the first things that support will tell you is to make sure you have all your updates and service packs installed.

I've never used the TMLE, does it set the cfg to read only after it changes things or does it monitor the file for changes to the properties? If it does neither, you still have to worry about it being set back to 1024.Also, as a side note, setting the cfg to read only probably isn't the best to do either. FSX constantly is writing to the file to save different values, not just graphics settings.Best to set your sliders then set your texture load size and then leave the sliders alone.

Sure you can, they are DLL's, you can embed pretty much anything as a resource inside a DLL and use it as a stream to work with it. But ya, make sure you are running SP1 for Win7 or SP3 for winXP (whichever you have).

Why not just change TEXTURE_MAX_LOAD in the cfg to 2048? It essentially has the same affect and you don't have to manually re size the textures.

Submit a ticket. This might be out of the scope of the forums since I believe the fonts are embedded and it's probably windows that is falling back to a common typeface.

That is defiantly not the font that is supposed to be there. Here is what it should look like:

As long as they're unique, it doesn't matter what-so-ever. They are never seen in any part of the UI and are usually only used by addons and VAs to help detect what aircraft you are flying.

You have to either re-bind the key combination in the FSX controls dialog or, switch the order around in the panel.cfg file.They are under the Views category in the Key/Buttons tab.

Turn off HyperThreading if you still have it on. FSX and HT on the i5/i7 don't work well. When it is enabled my i7 920 OCed@4Ghz, it will blue screen.

Ya, it's what all the fuss has been about the last week. Try the hotfix.

Its the cabin pressurization warning. Check that the pressurization panel is configured correctly.

Also, make sure the ML button in ezdok isn't pressed. Your also going to want to unbind all the numpad buttons from FSX controls if you haven't done so yet (Engines, control surfaces, Views) so when you interact with ezdok it doesn't do something in the sim like change your throttle setting or make you do a barrel roll.

The crew training manual has a good comparison between the two auto land modes starting on the bottom of page 5.26 that compares the differences between fail pass and fail op. Basically, pass fail will indicate LAND 2 or 3 and perform the rollout in addition to the flare, fail pass will not. Fail op is what most people think of when they imagine an autoland.

Quick note about AirDisplay. If you connect to the device while in windowed mode and your screen goes black, press Alt-Enter to make it go fullscreen, then press it again to return to windowed. Also, I won't let me start flight sim with it's connected (it detects airdisplay as invalid video hardware) so just start FSX then connect.

I like using Medium 2.x, almost no graphical difference from High (still has wave animations) and runs a whole lot smoother. Low 2.x I don't believe has animations and all the 1.x look like FS9 water to me.

Matt is right, GS information does not display on the PFD unless your track is within 90 degrees of the selected course and a valid glide slope signal is being received. If you were to tune your course to 070, you should see it come up on the PFD. From a 73NG manual:

RNAV approaches are not able to use auto land, they have minimums. Auto land must be preformed using radio signals (and carefully aligned ones at that, CATIII aproaches). Even being 0.3 off (in the case of KDCA RNAV RWY1) in nav performance would be a bad thing for allowing the aircraft to fly itself to the ground.

Automatic shutoffs if it gets too hot. It's safe to leave them in the on position no matter the OAT. They should turn back on if more heat is needed.

The reason PMDG doesn't do weather radar is because it is impossible to simulate the input data that a radar collects inside flight sim. Other WXR out there may look nice but, they are only essentially cloud finders with precipitation intensity as the color. Weather in flight sim is not realistic which is why a weather radar in flight sim is not able to be realistically simulated. Ever notice it raining at 10k feet without a single cloud above you? Other radars out there are guessing on what to display on the screen based on the parameters presented at particular stations. Even external weather programs guess at the space between stations using interpolation and a bit of randomness to make the transition a bit smoother between extremes.

No need to press multiple buttons at once. LATERAL OFFSET is available from RTE and INIT/REF INDEX pages.ALTERNATE DESTS is available from INIT/REF INDEX, APPROACH REF, RTE and NEAREST ARPTS pages.NEAREST ARPTS is available from the ALTERNATE DESTS page.