InTheAir

Hello Zach, Not sure about that one, hopefully somebody else will know how to fix that. Maybe there are still some rogue files associated with the liveries you're trying to install. Are there any liveries that you can install?

Do you have any messages or alerts in the Operations Center? When ever you uninstall a PMDG product, all the liveries are preserved and just need to be "repaired" after a reinstall. The Gear icon top right will have your fix. Click the drop down arrow and choose repair.. IIRC. Has worked for me every time.

Funny you say that, I opened a ticket at precisionmanuals.com regarding this issue and even linked to this thread.. it was closed without a single response from PMDG support. Quite the opposite of what you'd expect yes? Has anyone here read this update from PMDG? Looks like they may have found a bug in THEIR code. cedarjet201, lets try the new update and see if that fixes things.

Knowing that v4 is still very new as are the 3rd party updates there are bound to be issues and testing will surely bring fixes. With that in mind, I've personally recreated a CTD using a default aircraft at Dubai so this isn't just PMDG aircraft that are affected although the problem I had prior was uniquely so. I'll try to recreate that problem and report back if I do. ** Also, disabling 3d people didn't matter, still ctd. Will try to figure out what is causing the ctd, I'm able to load into the gate, when looking around the ctd occurs.

All their updates were installed, Dubai doesn't have a 3d grass option but does have 3d people. Thanks for your reply Chris I'll try disabling the 3d people and see if that works.

cedarjet201, Just an FYI, I completed a T7 flight from FSDT's CYVR to Flightbeam's KSFO HD without issue. Next, installed FlyTampa's Dubai and was able to get off the ground in default Kuwait but when I got close to OMDB, CTD'd without error message. Not saying it's definitely Dubai but I had zero problems prior to installing it. When I was getting the insta CTD that prompted this thread, the scenery / airports that were installed are: FlyTampa - St Martin / Midway / Tampa / Dubai FSDT - Vancouver / Zurich / GSX Flightbeam - Phoenix / San Fran HD ORBX - FTX Global / NA NRM / NA PNW / NA N. Cali / NA S. Cali / EU England / AU Australia I'm able to fly the T7 with everything above installed except for FlyTampa scenery. Regardless of who's at fault here, it seems weird that a particular P3D airplane developer's products would conflict with airport's and or sceneries? No other developer's aircraft are having this problem as far as I know so why is this one?

Uninstalled all add-on airports and slowly started adding them back.

The T7 is now loading into P3D v4 with all her amazing glory and I think it's time to go flying. Thanks PMDG777, downscc, carlito777, and tooting for the help trying to narrow things down, turns out it was an airport. Trying to figure out exactly which one it is.

Installed a 1080 ti and had the latest drivers prior to reinstalling the T7 with the new full installer released recently. P3D v4 works beautifully with my A2A aircraft and at every airport tried so far. The only problem I've run into is with the T7 exclusively as that is the only time P3D v4 has crashed.

Graphics drivers are up to date, FSDT is all up to date and FSUIPC isn't installed yet.

Other addons A2A Comanche and T-6 Just tried uninstalling again and rebooted. Downloaded the T7 installer again just in case.. long story short I got it to spit out an error report. Error 7/9/2017 11:00:30 PM Application Error 1000 (100) GENERAL: Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: ntdll.dll, version: 6.1.7601.23807, time stamp: 0x5915fdce Exception code: 0xc0000005 Fault offset: 0x000000000004eaab Faulting process id: 0x2854 Faulting application start time: 0x01d2f941b9ae2ade Faulting application path: H:\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 13e00fc0-6535-11e7-b062-902b343e858d DETAILS: Prepar3D.exe 4.0.28.21686 594a7255 ntdll.dll 6.1.7601.23807 5915fdce c0000005 000000000004eaab 2854 01d2f941b9ae2ade H:\Lockheed Martin\Prepar3D v4\Prepar3D.exe C:\Windows\SYSTEM32\ntdll.dll 13e00fc0-6535-11e7-b062-902b343e858d Information 7/9/2017 11:00:39 PM Windows Error Reporting 1001 None GENERAL Fault bucket 528700061, type 28 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 4.0.28.21686 P3: 594a7255 P4: ntdll.dll P5: 6.1.7601.23807 P6: 5915fdce P7: c0000005 P8: 000000000004eaab P9: P10: Attached files: \AppData\Local\Temp\WER76C5.tmp.WERInternalMetadata.xml These files may be available here: \AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_aea41cc9165798801f6adec3e31c79cb211ef632_22b796d2 Analysis symbol: Rechecking for solution: 0 Report Id: 13e00fc0-6535-11e7-b062-902b343e858d Report Status: 0 DETAILS: 528700061 28 APPCRASH Not available 0 Prepar3D.exe 4.0.28.21686 594a7255 ntdll.dll 6.1.7601.23807 5915fdce c0000005 000000000004eaab C:\Users\JonI5\AppData\Local\Temp\WER76C5.tmp.WERInternalMetadata.xml C:\Users\JonI5\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_aea41cc9165798801f6adec3e31c79cb211ef632_22b796d2 0 13e00fc0-6535-11e7-b062-902b343e858d 0

When mentioning the "uninstalling", I was referring to P3D v3 and related content, I'll update my original post to reflect that. Everything installed in V4 works except the T7. The time in the event log for those reports were close to when P3D crashed, I see now that there wasn't an application error reported for the crash. Those errors are not related so thanks for pointing that out, can't explain why I'm not getting any report.

Hi Chris, There were two errors reported: Error 7/8/2017 6:44:16 PM LoadPerf 3011 None Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code. Error 7/8/2017 6:44:16 PM LoadPerf 3012 None The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section. Thanks for taking a look,

Hello PMDG, P3D v4 is at version '4.0.28.21686' and has been working as expected. Here's what I did if memory serves (starting with the P3D v4 install), uninstalled everything on my system related to P3D including all scenery and airplanes. Used Add/Remove programs utility when possible or original installers to remove files and manually cleaned up files that weren't removed then ran registry cleaner and rebooted. Next, started installing everything I could find from developers that had compatible updates including a couple planes from A2A, the T7, some scenery regions from ORBX and a few airports from FlyTampa, Flightbeam, and FSDT. Also installed are precipitFX and PTA. Regarding installing the T7, the first install was downloaded on June 29th and installed but had not been run yet (was waiting for new graphics adapter to come in). After new card was installed and the latest update was out for the T7 I once again uninstalled the T7 and reinstalled with the new installer. Current situation is that when I try to run P3D v4 with the T7 selected at any airport I get instant CTD with zero progress loading into a scenario. Then, P3D v4 will not load with any plane default or not and same thing happens, instant CTD. A quick repair of the P3D v4 Content will get it working again but still no PMDG 777. Not sure if I did something but I've tried installing the T7 several times. Any ideas? Thank you, Jon Preston

They (P3D Devs) have said in their forums that many enhancements have been done to increase performance. Lets not forget the CPU is used in FSX to calculate a lot of the rendering functions, now imagine that all of this is handled by the GFX card via D3D11. That frees up the CPU to do more important tasks and I would also imagine maybe some new tasks. Dividing up those tasks to multiple cores should be easier now too.

I agree with a lot of what you're saying but I also believe that this is nothing but good news for all of us student pilots. Just wanted to add that there is a HUGE point being missed, many of our existing add-ons will work in P3D V2. This plus moving the graphics rendering to the GFX card utilizing D3D11 is huge. The LM Dev team seems extremely capable of getting P3D to where most people want it to be and this first step is absolutely in the right direction.. in my humble opinion. The amount of work that was required to get over to DX11 and still maintain compatibility with existing add-ons had to have been many 1000's of hours of coding. My hat goes off to the LM team.

Thanks for that, I was looking for this exact quote earlier. I hope they drop legacy support and require d3d11 cards. Focus on the future and forget about d3d9 and 10.

I was one of those on the fence regarding FTXG and decided to get it after getting the A2A 172. I have no regrets at all, FTXG looks great day and night. I also haven't noticed any loss in frame rates. Good luck.

I'm a long time SFX user and have suffered FSX crashing due to switching between full screen and windowed mode many times. I have a question for you and anyone else who experiences this. How are you switching modes? Are you using the Alt+Enter method or do you use the "View" menu and click the "Full Screen" option? I always and I mean always used to use the Alt+Enter method in FSX for switching. Recently, after purchasing the A2A 172 I was still getting the crash after a hour or longer flight. It was never really a big deal since it was at the end of the flight and I anticipated it. Out of curiosity, decided to try using the menu option instead and ever since, not one single crash. Tested this with the A2A 172 and FSX running for longer than a day. After it was running for that long I did some pattern work and changed back and forth many times with no crash. I'm convinced that Alt+Enter is the culprit. I've put several more hours on the 172 since then and still no crash. Hope someone else finds this useful. BTW, I'm still using 1.4, haven't tried 1.5 yet. Maybe today.

Very excited to say the least and truly hope V2 lives up to the hype. If I need a PMDG fix, I'll always have FSX around. The C172 Trainer from A2A installed into Prepar3d v1.4 with no problem. The time and maintenance log files are common for both simulators by the way, very cool IMHO. :good:

Thanks for the comments. Wasn't planning on getting FTX Global but It was worth the wait and I'm pretty happy, FSX looks good.

Here's a few shots taken recently during a shortish hop from KPIE to the East coast of FL in nasty weather. Due to the settings I use, my FPS are 30-50 in busy areas in good weather and low 20's (sometimes lower in certain situations) to the 30's in bad weather. Ground scenery shadows are enabled plus AA is set in NVins at 32x. Credits go to A2A for the C172 Trainer | skyhawk from A2A forums for his amazing N1780C repaint | REX Essentials Plus HD/OD 4096/2048 FTX Global | ENB Series and SweetFX | Gabriel Teles sky textures and ENB color palette FSX looks amazing if you ask me, ENB and SweetFX help a lot though.

Since PMDG is so busy with the T7 release, maybe they won't mind a little help. Short answer is yes.. Here is thread that was answered recently: http://forum.avsim.net/topic/411507-double-installations/?view=findpost&p=2696450&hl=%2Binstall+%2Btwo+%2Bcomputers

If memory serves.. warning, it has failed me before so take this with a grain of salt. Capt. Robert owns a DC-6 and it is or was his favorite aircraft or something to that effect. Again, my memory gets fuzzy but I believe that to be why. They, as in RSR, also mentioned that there was talent being utilized on the DC-6 project that wasn't necessarily directly tied to the T7 development. DC-6 development could have been happening all the while. Of course, someone official will eventually let us all know whats going on.

Great find Ryan, thanks for sharing.