Bobsk8

I found the problem, and it wasn't the Northern CA scenery. I have been trying out an ATC Demo program the last couple of days, and on a flight this morning I was approaching a small airport, KSLE, and the FPS started slowing way down again.. I also noticed that the display on the ATC program was jerky, so I went into the Windows Task manager and saw that they ATC program was using over 40% of the processor. Didn't leave much left for P3D and AS16.  I just restarted the flight using my normal ATC program, and flying out of KHWD I got a solid 30 FPS.   

I got the G44 this morning, and installed the GTN 650 as a pop up. Works perfectly. What a great aircraft for a good price. Flies like a dream.  
 

You can uninstall 3.3 client and install 3.2 client providing you have it.  

I think I may have found the root of my problem. In the GSX add on manager there is an updater that is supposed to check to make sure you have the latest add on manager update. I just found out that this is not quite true, or at least my understanding of it but I am not a computer programmer. Prior to installing P3D V3.2 I made of list of things that had to be updated such as ASN, etc. On the list was the add on manager for coutal. So while I was running P3D , I went to the Couatl Live Update menu, and had it check  auto updater and it said I had the latest update, which was 2 days ago, so i thought I was good to go. As it turns out, this is not what is needed for P3D V 3.2  The bglmanx.dll has to be updated and the only way that can be done is to install a new copy of the  add on manager, or reinstall GSX.  So thinking that I had made all the modifications needed, that is why I couldn't figure out what could be wrong. It was a few people on Facebook that pointed out that they had a similar problem, and when they disabled the Add on  Manager, the problem went away. What made it more difficult is V3.2 would work fine for maybe 10 flights, loading up with zero problem, and the next 5 times I would try and fly, it would crash each time on startup. Anyway, I just downloaded the Add on  Manager, and the bglmanx.dll was replaced with a new version. And I didn't have to reinstall P3D, or format my harddrive, or buy a new GPU and CPU.... :wink: 
 
 
And that's my story. 

With the help of a forum member in the P3D forum on this website, I found what is causing the slow shutdown with the PMDG aircraft, It is FSUIPC and it's default of saving the last flight. Apparently saving the last flight with the PMDG aircraft takes much more time ( up to 30 seconds)  than any other aircraft, and the screen that says " are you sure you want to exit P3D  after you exit P3D ( or something similar) will not pop up until this save is finished by FSUIPC. I do not have autosave checked in FSUIPC, so this is the default condition of paid FSUIPC.  What I did was to add the line   SavePreviousFlight=No      in the FSUIPC.ini file under modules in the P3D folder under [General]. Now the shutdown is immediate with the PMDG aircraft. 

You are genius.  That fixed it.....

Just saw this tonight when I got home. New Version for V3 just released today.   http://www.simforums.com/forums/ezca-v1187-p3d-v3-available-for-download_topic53929.html

I brought up the config manager but could not find anywhere to re enable FS2 Crew.  I have version 1.0 of the config manager. What is the menu item?