dfreemanfso

Good evening all. I posted this in the P3D forum yesterday and have not received a response so I'll try here. I know this is long and I am hoping it’s something stupid on my part, but I can’t seem to lock down this issue. Background: In order to install P3D V3.1, I deleted all P3D V.2 software and associated add-ons from my hard drive. I left FSX on the hard drive (K drive) as a backup so I could still fly if I had issues with P3D. I did delete all of my FSX add-ons in order to leave space on my hard drive for P3D. I had run P3D V2.5 with the same add-ons on the same system with no issues besides OOMs which are to be expected. Problem: I installed P3D V3.1 on about 3 JAN. I installed a registered FSUIPC, the ORBX products, REX, and ASN in the days following. I flew some quick flights with several default aircraft out of a few different default airports to test ORBX, REX textures with soft clouds, ASN etc; I had no issues. However, after installing the PMDG 777 and Aerosoft A321 and trying flights with them, I started getting CTDs. They were about one to two minutes after takeoff with PMDG and about 4 minutes after takeoff in the Aerosoft Airbus. I can sit on the runway in either aircraft without the CTD for as long as I want. The fatal error occurs with or without ASN running, at different airports, and different weather conditions; I have not tested with default weather textures. The Windows event log reads as follows: System - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Level 2 Task 100 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2016-01-07T21:35:48.000000000Z EventRecordID 24459 Channel Application Computer Dave-PC Security - EventData Prepar3D.exe 3.1.2.15831 5672b60a sim1.dll 3.1.2.15831 5672b60a c0000005 000cafa4 12b8 01d149924c58740a K:\P3D Main\Prepar3D.exe K:\P3D Main\sim1.dll 9d9f5ec1-b586-11e5-9607-00268317052a Did something not get deleted properly from P3D V.2 that is causing a conflict? Registry errors? Is there an issue with installing al my P3D V3.1 and associated add-ons direct to my K drive and not C/Program Files (x86)? Graphics card drivers? P3D settings? (I have not touched the .cfg) and am running 3.1 with roughly the same settings that I ran 2.5 Hardware: Win 7-64 English i7 26K OC to 4.3GHz ASUS P8P64 MOBO 8GB DDR3/1600 memory GTX 780 - Driver 347.88 232 GB SSD for P3D/FSX and supporting software 111 GB SSD for Windows and small programs 3 monitor with TH2G Software: P3D V3.1 Installed in separate drive K/P3D ORBX Global Base Installed in K/ ORBX Global Vector installed in K/ ORBX Trees Installed in K/ REX Texture Direct with Soft Clouds and P3D V.3 service pack Active Sky Next with SP4 Beta for P3D V.3 No add-on Airports Norton Internet Security PMDG 777 base pack (No add-on liveries installed) with the latest PMDG installer as of 05 JAN 16. PMDG Operations Center is also up to date. Aerosoft Airbus X latest downloader with no add-on liveries installed. In the mean time, I'm going to install P3D 3.1 again, and try both airplanes with no other add-ons, then apply each add-on and continue to test. Thanks, Dave

Update - I had the same error with the Airbus X, so I don't consider this a PMDG issue. If you have any ideas let me know...time to wipe everything and reinstall one at a time :mad:

Good evening all. I posted this topic in the P3D forum but wanted to double tap PMDG as well. I know this is long and I am hoping it’s something stupid on my part, but I can’t seem to lock down this issue. In the meantime I’m going to install another third party aircraft and see if I have the same problem. That will help me determine if this issue is strictly with PMDG… Background: In order to install P3D V3.1, I deleted all P3D V.2 software and associated add-ons from my hard drive. I left FSX on the hard drive \K as a backup so I could still fly if I had issues with P3D. I did delete all of my FSX add-ons in order to leave space on my hard drive for P3D. I ran P3D V2.5 with the same add-ons on the same system with no issues besides OOMs which are to be expected. Problem: I installed P3D V3.1 on about 3 JAN. I installed the ORBX products, REX, and ASN in the days following. I flew quick flights with several default aircraft out of a few different default airports to test ORBX, REX, ASN etc. prior to installing the updated PMDG 777 product – no significant issues noted. After installing the PMDG 777 I loaded the airplane from the main menu, ensured error logging was turned off in P3D, and ran the Simconnect .msi installers in specified P3D folders in accordance with PMDG’s guidance. The PMDG aircraft will sit on the runway for as long as I want it to and all of the systems work fine (buttons knobs etc). However, about one to two minutes after takeoff, P3D has a fatal error (see log). The error always occurs at the same time. The fatal error occurs with or without ASN running, at different airports, and different weather conditions; I have not tested with default weather textures. The airplane performs fine in flight with no systemic issues prior to the fatal error: System - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Level 2 Task 100 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2016-01-07T21:35:48.000000000Z EventRecordID 24459 Channel Application Computer Dave-PC Security - EventData Prepar3D.exe 3.1.2.15831 5672b60a sim1.dll 3.1.2.15831 5672b60a c0000005 000cafa4 12b8 01d149924c58740a K:\P3D Main\Prepar3D.exe K:\P3D Main\sim1.dll 9d9f5ec1-b586-11e5-9607-00268317052a Possibilities that I don’t know how to fix: Did something not get deleted properly from P3D V.2 that is causing a conflict? Registry errors? Is there an issue with installing al my P3D V3.1 and associated add-ons direct to my K drive and not C/Program Files (x86)? Graphics card drivers? P3D settings? (I have not touched the .cfg) PMDG settings? (I haven’t altered anything from the original download through the ops center) Hardware: Win 7-64 English i7 26K OC to 4.3GHz ASUS P8P64 MOBO 8GB DDR3/1600 memory GTX 780 Driver 347.88 232 GB SSD for P3D/FSX and supporting software 111 GB SSD for Windows and small programs 3 monitor with TH2G Software: P3D V3.1 Installed in separate drive K/P3D ORBX Global Base Installed in K/ ORBX Global Vector installed in K/ ORBX Trees Installed in K/ REX Texture Direct with Soft Clouds and P3D V.3 service pack Active Sky Next with SP4 Beta for P3D V.3 No add-on Airports Norton Internet Security PMDG 777 base pack (No add-on liveries installed) with the latest PMDG installer as of 05 JAN 16. PMDG Operations Center is also up to date. Thanks, David C. Freeman Lawton, OK USA

Hi all, I've had the NGX for years and for some reason recently ran into this issue. I set the autobreak to RTO prior to taxi. As I taxi to the runway the breaks engage without me breaking. I then disengage the autobreak and it's fine again. Am I applying too much thrust to break away from the gate making the autobreak want to engage? I'm not sure why this is happening. Could it be an issue with my Saitek rudder pedals not being set to a good sensitivity/null zone? The autobreak functions fine on landing. David C. Freeman

Well Shazam - I knew it was something small and stupid. It's amazing the things you take for granted when you re-install FSX after 5 years.

Hello everyone, I have enjoyed PMDG since the beginning and have never had any issues until now. I recently did some hardware upgrades and decided to re-install a clean FSX to include PMDG's products. Only problem is that the livery installer is not installing liveries. So let me explain in excruciating detail what I am doing so maybe someone can tell me what I'm doing wrong. This make so little sense to me that it must be a simple mistake. 1. Download the repaint file and unzip it to a temporary folder, ensuring that it is for the right variant for example: PMDG_737NGX_800WL_AA 2. Run the PMDG Operations Center as an administrator from the windows start menu 3. Select product 737NGX and click on livery manager 4. Select variant - PMDG 737-800 NGX WL 5. Click green + button to add livery 6. Navigate to the location of the PMDG_737NGX_800_AA.ptp file and double click on the file 7. Watch the files load - I can now see the American Airlines with winglets displayed under liveries. Next, I close the operations center and open FSX. There is no American Airlines 738W airplane available. I know that the path to FSX is correct because when I open FSX/SimObjects/Airplanes/PMDG 737-800NGX WL, there is a folder called Texture_AA and the aircraft cfg is edited to show: [Fltsim.1] title=Boeing 737-823NGX American Airlines Winglets So, I am really confused - it's almost like everything is happening the way it's supposed to except that the textures don't show up. I'm at a complete loss and have no idea of what to do next. I had no issues loading repaints before I upgraded my computer. Also, I re-downloaded the 777 and have the same issue - I cannot upload repaints. The only thing I can think of is that the ops center and my FSX are running of separate SSDs, but I doubt that's the problem. DAVID C. FREEMAN Win 7 64 ASUS P8P67 Deluxe, I7 26K Sandy Bridge OC'd to 4.3Mhz 8GB DDR3 1600 memory GTX 780 GPU 240GB SSD For FSX Only 120GB SSD for OS and programs 3 monitors with TH2G

Hello everyone, I have enjoyed PMDG since the beginning and have never had any issues until now. I recently did some hardware upgrades and decided to re-install a clean FSX to include PMDG's products. Only problem is that the livery installer is not installing liveries. So let me explain in excruciating detail what I am doing so maybe someone can tell me what I'm doing wrong. This make so little sense to me that it must be a simple mistake. 1. Download the repaint file and unzip it to a temporary folder, ensuring that it is for the right variant for example: PMDG_737NGX_800WL_AA 2. Run the PMDG Operations Center as an administrator from the windows start menu 3. Select product 737NGX and click on livery manager 4. Select variant - PMDG 737-800 NGX WL 5. Click green + button to add livery 6. Navigate to the location of the PMDG_737NGX_800_AA.ptp file and double click on the file 7. Watch the files load - I can now see the American Airlines with winglets displayed under liveries. Next, I close the operations center and open FSX. There is no American Airlines 738W airplane available. I know that the path to FSX is correct because when I open FSX/SimObjects/Airplanes/PMDG 737-800NGX WL, there is a folder called Texture_AA and the aircraft cfg is edited to show: [Fltsim.1] title=Boeing 737-823NGX American Airlines Winglets So, I am really confused - it's almost like everything is happening the way it's supposed to except that the textures don't show up. I'm at a complete loss and have no idea of what to do next. I had no issues loading repaints before I upgraded my computer. Also, I re-downloaded the 777 and have the same issue - I cannot upload repaints. The only thing I can think of is that the ops center and my FSX are running of separate SSDs, but I doubt that's the problem. DAVID C. FREEMAN Win 7 64 ASUS P8P67 Deluxe, I7 26K Sandy Bridge OC'd to 4.3Mhz 8GB DDR3 1600 memory GTX 780 GPU 240GB SSD For FSX Only 120GB SSD for OS and programs 3 monitors with TH2G

Strange...it almost seems like performance has no correlation with system specs. I tried to take a look at what was hitting the FPS the most by switching between my Coolsky MD-80 and the NGX. At a default airport with no traffic the Cool sky maxed out at 30. The NGX dropped to 22. AT FSDT's ORD without Traffic, Coolsky gets 17, NGX gets 13. If I add the traffic at ORD, Coolsky gets 13 and NGX gets 9. I really think the big culprit is the FSDT ORD scenery. My FSDT DFW scenery goet 17-18 FPS with traffic and the NGX. Going from full screen to window'd mode didn't make much difference. At least while I was changing aircraft, moving to different airports, going from full screen to windowed mode, and using the menu and such, I got no CTDs. That is something to be happy about.

I think it's the three monitors.

After having CTDs and big freezes on my first few NGX flights, including on final into LGA, I thought I would apply some fixes and see how things went. Here is what I did... 1. Applied the hotfix2. Deleted ENB series3. Verified I had the latest UIAutomation file in FSX Main4. Downloaded and used game booster III5. Lowered cloud draw distance from 100-706. Lowered autogen from extremely dense to very dense I started out at FSDT's DFW with 12-13 FPS on the ground with Ultimate Traffic II running at 75%. Prior to departure from DFW, I turned off all traffic to ensure it wasn't eating my system on departure. The traffic looks good around the gates, but I really don't care if I see it while on the runway and enroute. On the takeoff and initial climb out of DFW, I was getting 18-21 FPS which quickly went up to my limt of 30 in cruise. Enroute, the only time I lost frames was when REX loaded. I am going to turn the REX load times down. I'm afraid if REX decides to load on final in a dense scenery area, it will crash. On descent in to FSDT's ORD, frames gradually dropped to around 12-15 on final. I think ORD is a little more detailed than DFW, thus even lower frames. After landing, I turned my traffic back on and got under 10 FPS during taxi. That is low, but should be expected with UT II at 75%, at FSDT's ORD in the NGX. Plus I'm running three monitors. Other than the taxi at ORD, I didn't notice any freezes or major chops. I'm really glad there were no CTDs this time, but this is just one flight. The next test will be going from FSDT's LAS with Mega Scenery X to FSDT's JFK. Going into NYC, I think I will have to lower my autogen even further. Dave

Nice vids...ENB is great. My NGX has had many errors with the ENB dll file. It sounds like a lot of people are having trouble with ENB. I think a big part of my problem is my three monitors overloading my graphics card. It works fine on one screen.

Takeoff and landing is what is upsetting the NGX, and I kind of have to do those. That being said, I do see your point. It all depends on what the individual can accept as good enough though. Sure, I could turn down all my sliders, delete all my add on scenery and traffic, and the NGX would run like a dream. The goal is to get it to the best place I can without a significant performance loss. I am going to reduce some autogen and cloud draw distances when I use the NGX and see how that works. Lastly, we paid a decent ammount of money for this product. "Not doing things to upset it" is not a good enough answer for a $70.00+ product. Way too many people are having crashes and freezed right now. PMDG has always been awesome and this will all be fixed. I should have waited a couple of months to buy, but I had the FS9 73s and they were the best. This product will get there too.

I have the GTX580 1.5. I am running 3 monitors and it is not as smooth as silk...freezing and CDTs. When I go to windowed mode on 1 monitor, there are no issues. As others have stated, the 1.5 should be fine unless you are going with multipe, or a single large high res monitor.

The error file- d3d9.dll, is the ENB file. Hopefully deleting ENB will fix my CTDs. It would be great if PMDG could do a fix to support ENBSeries. I think FSX, by default, is way too bright at night, and ENB is a good fix for it. Dave

Ok...I think there are updated drivers for the NVIDIA that I can download. I thought I had the UIAutomationCore issue fixed, but I'll double check that. I'll also delete ENB (although I like it). I also have the hotfix installed. We'll see if that helps. Thanks, Dave