738Captain

You can't. The J41 is not license for use in P3D.

Track or Heading on the ND?

I'm about to do my first flight in the 777 after updating to the latest version, and I have encountered the same problem. Luckily, I solved it! The 777 is sending the WX.PLN file to the Steam folder in My Docs instead of the default FSX folder. And ASN is looking for the file in the FSX folder. Redirect ASN to the Steam folder and it should solve the problem.

Fly Tampa CYYZ. Especially in winter, you see snow blowing across runways and taxiways. I have to commend Fly Tampa, they made that effect look realistic. As well as the night lighting, buildings, textures etc. Everything about that package is great. The only down fall is the performance (VAS and FPS). Which to my understanding is not Fly Tampa's fault.

I think you might find this interesting. After installing FSX SE, I used the same setting I uesd in FSX Box Edition, including the Autogen setting. I did my test flights in the Caribbean. I think we can agree it's less Autogen intensive than cities like DFW, ORD and YYZ. But Here's the interesting part, like I said before, after removing KB2670838, the Terrain.dll CTDs stopped. Since then, I have successfully completed flights between MIA, DFW, YYZ and ORD without a single Terrain.dll CTD.

Well in my case it was, and a few others as well. I know this because I kept getting CTDs, and every time it was the Terrain.dll.

I remove FSX box and did a clean FSX SE install recently. I started getting a CTD caused by the Terrain.dll, so I did a search and found a post on the FSX Steam forum saying to remove KB2670838. When I did, the CTDs due to the Terrain.dll stopped.

I'm very well aware of the problems with the update, that's why I'm asking if anyone found a solution other than removing it.

Is this still an issue? Has anyone found a solution besides removing it? KB2670838 was causing my FSX SE to crash with a Terrain.dll error.

+1

http://i255.photobucket.com/albums/hh135/frdabdool/New/ScreenHunter_2623%20Jul.%2013%2004.46.jpg

I'm having a problem with DX10. Around mid-day to mid-afternoon in FSX, I can't see the lower DU, radio or nav displays on the pedestal in the NGX. I tried uploading a screen shot, but it doesn't seem to be working.

Correct! Clear the failures after saving the panel state.

Load one of the default panel states. Shutdown the engines, setup the aircraft and save it. Then clear all the failures.

Check the PMDG Operations Center.