Jim Young

One appears to be off a few minutes. I would use the PMDG. Why would you be concerned about flight time in a simulator? Best regards, Jim

Normal behavior. Moving the LOD(Radius) slider might help or changing the resolution to 2048 might help reduce this. The faster your aircraft, the harder it is for your computer to keep up.

All I did is uninstall the Prepar3D Professional Client and then downloaded the latest version and installed it. I did not have to mess around with any of my aircraft, none of my Orbx scenery, my scenery.cfg was still there with no changes, there was no changes to the P3D.cfg, there was no changes to dll.xml or exe.xml. Use Elaine's excellent uninstall the client and reinstall the new version topic - http://www.avsim.com/topic/484945-how-do-i-update-prepar3d-v3-using-the-new-installers/ I think the main change with the client update is the update of P3D.exe and that does not affect your aircraft or scenery. Best regards, Jim

You're right Greg. Uh, maybe someday soon.... Well, I have to check out the new PMDG 747 when it's released first. Thanks for the suggestion. :smile: Best regards,

The upgrade does not affect any of your current scenery or settings.

This you must not do under any circumstances. Just make sure "Run as Administrator for ALL Users" is selected. Do not check any of the other stuff above that or you will have further problems. Best regards,

Thought I would tag this topic with a Scam Alert! Hopefully not too many around the web bought the software before it was removed.

Your system is capable of running P3D but the thing you will have to be concerned about is Virtual Address Space (VAS). Microsoft Windows only gives 64 bit users 4GB's. Back in the old FSX days we had to keep our sliders down a bit in order to get it to run around 20-30 FPS. The problems today is everyone thinks they have fast systems (and they do) so they think they can crank up P3D settings plus any of the addon's setting. High settings might work with a flight around an hour or two but more than that you risk running out of memory (VAS). The more eye-candy software addon you have, the more likely you'll see crashes if you don't keep your settings down. An SSD will give you faster load times but I do not think you'll see any significant performance boost while running P3D. Scenery density. I would keep it normal or dense. Nothing higher. Depends how long the flight and the other addon's you will have enabled. If you have the PMDG 777 with PMDG's777, flying over photographic scenery, into eye-candy commercial scenery airports and with AS16 running, you won't get far. The enjoyment of flight simulation, at least for me, is to learn the various systems on an aircraft. Pilots don't spend too much time sight-seeing and trying to find people sitting on top of buildings. They are too busy making sure the aircraft is flying properly. I personally enjoy learning the various types of flight management. I learned the G1000 recently and I'm very proficient with the FMC in the 737, 767, 777, and 747. Of course it gets a bit more daunting when you have real world weather simulated by weather programs like OPUS and Active Sky. If you every have a crash, I highly recommend the AVSIM CTD Guide (see link in my signature). It provides some suggestions on how to avoid crashes and what to do if you do get one. Enjoy! Best regards, Jim

All four components.

It appears you have to update your Mouse drivers - http://forums.windowscentral.com/windows-10/372782-why-cant-i-copy-paste-windows-10-allows-me-copy-but-will-not-paste.html. If you cannot copy and paste there is nothing we can do. If you see a faulting module maybe that will help.

I use to have a couple of fixes for this in the AVSIM CTD Guide but took it out with the latest version as the "fixes" numbered into the thousands (okay a slight exaggeration but there are many). Even PMDG has no known fix - http://www.avsim.com/topic/350915-pmdg-737ngxdll-crash/. Okay that was some time ago but FSX and PMDG 737NGX has not changed over those years whatsoever. You have FSX installed in the default location. That's okay but you need to make sure UserAccessControls (UAC) is disabled (see page 24, AVSIM CTD Guide). The module loaded successfully (module 183) and it crashed during the tutorial. This might indicate high settings in your FSX.cfg and/or your display driver settings. Some have fixed this as they simply ran out of Virtual Address Space (VAS) or ran very low on VAS and the 737 gauge was the first to suffer. You will have to try again after lowering some fsx settings. Your system does not appear to be very powerful. I did a lookup for the system and it appears it has an i5 CPU with 4GB's of RAM. It is for some games, but not for FSX. You can play FSX but you will have to be very, very careful with your settings. It appears you have an NVidia Video Card as I see 3D Vision loaded but you did not indicate the GPU you have installed. FSX is now more dependent on the CPU rather than the GPU. A system with 3.2GHz is good but it all depends on the GPU too. Microsoft Visuals C++2005 and 2008 are properly installed. You also have MS Visual 2010 which is used by the PMDG 737. I did not see where Microsoft.net 2.0 loaded. You should have versions 2.0 through the latest installed. Look in C:\Windows\Microsoft.net\Framework for the visuals installed. I'm only concerned with version 2.0. They are mostly not backward compatible even though Microsoft states they are. FSX is an old game that started up with Microsoft.net 1.1. I would leave Active Sky weather disabled too during the tutorial. The uses a lot of resources too. You may have had it disabled but one of the modules used by ActiveSky loaded. Hope this helps.

You just copy the crash report and then come here, start a new post, right click and select Paste. You might have User Access Controls. In the AVSIM CTD Guide, page 24, there's an explanation of how to disable User Access Controls. Best regards,

Hi Bert, It is there when you first install it. After that, it disappears and you won't see "Apply" again.

I just went through an ordeal reinstalling PNW into P3Dv3.3.5. I suspect you are trying to install it into P3D too? You should not have runways crowded with trees and houses at KSEA and I suspect you had another KSEA on your computer (look in your MyTrafficX\Scenery folder and disable KSEA). If you have Taxi2Gate's KSEA, then there's a compatibility problem but there is a compatibility forum at FTX and it covers how to make that airport compatible and it looks great! Make sure after installing the PNW you install the latest Orbx Library as that has several updates. Make sure too you have the latest installer for PNW. The installer should show PNW180 at the end. If not, you'll have to download the latest installer. Oh! And read the manual as far as what you have to do after installing it and opening up FTX Central. It is important that you apply the region so it is not on default. Best regards,

I personally think you should pay a few dollars and get something like the FSFX 777 Immersion package - https://fsfxpackages.com/en/777Immersion/ Unfortunately I do not know of any "free" sound packages for the PMDG 777 (I did a search on Google for Free PMDG 777 Sound Packages). Most are old. Think you would be better off with what they provided with the software as I'm not sure if any of the older packages will work.

The exception code indicates heap corruption. The AVSIM CTD Guide (see link in my signature) provides some suggestions for fixing the NTDLL.dll crash. The suggestions were taken from places around the Internet, including AVSIM, where individuals had fixed their problems. Best regards, Jim

Hi Manny, My issue was with FTX/Orbx Southern Calif installation. Are you talking about FTX/Orbx KPSP? If so, the product will not work with FTX Southern California OR Megascenery as that is stated in the product description on the FTX website. The elevation issues between MegaScenery and KPSP are much different than what I discussed in my OP. My OP was totally concerning the installation of FTX Southern California. The elevation issues occurred because all of the elevation .bgl's that FTX places in Scenery/World/Scenery were installed in FSX's Scenery/World/Scenery and not into P3D's Scenery/World/Scenery as my P3D Scenery.cfg had the location of all of the default scenery linked to my FSX Scenery.cfg. So, anything in P3D's Scenery/World/Scenery could not be seen as the P3D Scenery.cfg was linking to the FSX Scenery.cfg. Sort of complicated. How all of my default scenery in P3D got linked to the FSX locations is unknown. I just brought it up as anyone having elevation issues with any of the FTX/Orbx products should check the links in the P3D scenery.cfg and make sure they are linked to P3D files instead of FSX files (if you also have FSX or FSX-SE installed). Best regards, Jim

The process monitor might help if you have a freeze or crash occurring at the same location like I had and as suggested in the guide. I use it mostly to see what's loading at startup (to the setup screen) then what's loading after I click on okay to load the flight. For instance, I have a flight from Chicago to Washington, DC. Why do I need to have something loading and taking up resources in Texas or California or in Europe? There is no "manual" but just a help file. That's Procmon html. Just double-click on it and you will see Process monitor. Double-click on Process Monitor and it will expand to all the contents. Just do not understand what you mean by "3 folders". Maybe you mean the Tabs, Contents | Search | or Index. Whenever you install a new product that uses the dll.xml or exe.xml, it will create a backup file. So those that have "before FSDT" or something like that is a backup. A backup file will not load so no need to place in a temporary folder if you plan on seeing if the dll.xml is causing your crashes. The same goes with the exe before FSDT backup. No need to move that. Same goes with the scenery.cfg. You will see many copies of the scenery.cfg. The only one that will ever load is the one with the .cfg extension. Anything else will not load. Hope this helps.

Very realistic! Best regards,

Nice sunrise. The skies and clouds cooperated very well with your flight! Thanks for posting. Best regards,

See the AVSIM CTD Guide for probably causes of freezes (depending on whether it happens at loading or during the flight). Link to guide is in my signature. Best regards,

Agree Steve as the dll.xml is loaded at startup where the crash is occurring. I've never seen a case where it crashes at startup. Hopefully he did not place the uiautomationcore.dll in the main P3D folder although I heard PMDG is recommending it. If he did, he might have put in the wrong one and that module handles memory management for the application.

I would not recommend setting a pagefile. It will definitely not stop the out of memory errors. My recommendation (see the AVSIM FSX Configuration Guide - link in my signature) is to leave it at System Managed Size. With FSX you could have tons of memory, a huge pagefile and you will still run out of memory. When it is telling you you are running out of memory it means you are running out of Virtual Address Space (VAS). Microsoft only gives those with 32 bit applications 4GB's. FSX is resource intensive and will run out of memory (VAS) fast with high settings and lots of eye-candy enabled. There is no patch to improve memory management with 64 bit operating systems. If a person has a 32 bit OS installed, then Microsoft only gives you 2GB's of VAS. There is a /3GB switch that allows that to be increased. Everyone should be running FSX on a 64 bit system by now. Please see the AVSIM CTD Guide for suggestions on preventing crashes (see link in my signature).

I have no idea what would cause this other than "Previous Flight" settings. Best to move your fsx.cfg to a temporary directory (or rename it), restart FSX and let the sim rebuild.

The Electronic Flight Assistant website is working for me. I even clicked on the logon and I have the option to logon.