Trachemys

NGX and P3d V3.4

Recommended Posts

Hi, I am thinking about this combo, PMDG NGX on P3D V3.4, but I have heard about many many issues, CTD, PMDG not supporting the V3,4, etc etc, what do you think? and what do you think about other PMDG products running on V3.4 versión? Thanks.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I didn't like the P3D V3.4, even with the latest fix... Got worse FPS than with the V3.3... Had to downgrade... Maybe the V3.5 will be better...

Share this post


Link to post
Share on other sites

No significant issues with P3D 3.4 and the NGX here, but I'm judicious with settings like AI traffic and road traffic in order to achieve smoothness in the sim.

Share this post


Link to post
Share on other sites

PMDG737NGX for FSX Acceleration and a Client update to P3D v3.4.18.19475 (HF2) all ok here.

Share this post


Link to post
Share on other sites

Working fine for me on 3.4. In fact it's working better than it was on earlier versions of P3Dv3.

Share this post


Link to post
Share on other sites

Hi Kyle, your YouTube videos are awesome, I own an old FSX PMDG NGX License, what should I do to be running it on P3d, I must purchase another p3d license?

​Cheers!!

Share this post


Link to post
Share on other sites

Hi Kyle, your YouTube videos are awesome, I own an old FSX PMDG NGX License, what should I do to be running it on P3d, I must purchase another p3d license?

​Cheers!!

Yes, you need to purchase it again.

Share this post


Link to post
Share on other sites

Just purchased PMDG737ngx again, for even more money and can't  even use it or P3D. Wrote up a ticket to PMDG support, nothing happening there. So, what's happening is, I have P3D v3.4.14.18870. Installed ngx, click on p3d and CTD. The event log is

-EventData

param1application-specific

param2Local

param3Launch

param4{C97FCC79-E628-407D-AE68-A06AD6D8B4D1}

param5{344ED43D-D086-4961-86A6-1106F4ACAD9B}

param6NT AUTHORITY

param7SYSTEM

param8S-1-5-18

param9LocalHost (Using LRPC)

This is the only add-on I have at this time for P3D

Rob Potter

Share this post


Link to post
Share on other sites
4 hours ago, Shopdog said:

Wrote up a ticket to PMDG support, nothing happening there.

When did you submit the ticket?  They usually respond within 24 hr.

I get nothing from the above Event Data paste.  I think I understand the problem description:  You launch P3D and you get a CTD, but what does P3D do before the CTD? Does it show the banner?  Does it open the Scenario Setup window or start with the fighter on the runway?  Did you ever get it to work to the point where you could select the NGX?  What is your default aircraft.

You left out a lot of information.. there are numerous types of CTD events, sometimes windows gives a message that the application has stopped working and will close and sometimes nothing. What is it?

Did you have P3D running before you ran the NGX installer?

Share this post


Link to post
Share on other sites

I submitted a ticket a couple days ago. Yes it shows the splash screen, no scenario screen, doesn't get that far. Was working great before the install of ngx. Also had AS2016 running before with no problems. I can't remember what the default a/c was. Yes did get the windows message that the application had to close. I was told by a PMDG tech to uninstall the client app which I did and re-installed, which worked until I closed the simulator and restarted and the same thing happened. I'm getting this fault:

 

Faulting application path: D:\Prepar3D.exe

Faulting module path: C\Windows\SysWOW64\ntdll.dll

 

Rob Potter

Share this post


Link to post
Share on other sites
5 hours ago, Shopdog said:

Wrote up a ticket to PMDG support, nothing happening there.

Please don't be disingenuous. You received a response from us a mere 18 minutes after submitting your ticket, and have continued to receive support from both Ryan and Paul (for an issue caused by something other than our code) over the following days.

NTDLL errors are not ours, and not caused by our products. Most often, they are caused by graphics card issues, but the error is very generic. This may be helpful: 

 

Share this post


Link to post
Share on other sites

Ok, I did what the tech suggested and it didn't work, so I responded back to him and haven't heard a thing in 4 hours after my response that it did not work. So Kyle since your on the support team what would you suggest? Everything was working fine with the other add-ons, what makes the ngx so different than other add-ons?

 

Rob Potter

Share this post


Link to post
Share on other sites
21 minutes ago, Shopdog said:

Ok, I did what the tech suggested and it didn't work, so I responded back to him and haven't heard a thing in 4 hours after my response that it did not work.

We don't run a 24/7 support operation, and it's also the weekend (you sent the message you're referring to at 0929 on a Sat morning - 0629 for Ryan). I don't think it's entirely reasonable to expect instantaneous replies all the time, particularly on the weekend. We still log in over the weekend to provide support (this post, case in point), but let's be a little realistic here.

22 minutes ago, Shopdog said:

So Kyle since your on the support team what would you suggest?

I provided a link to a guide that goes through common CTD issues. As I mentioned in the last post, a fault in NTDLL.dll is not caused by us. It's usually a graphics or core OS issue. Google it. You'll see thousands of other thread entirely unrelated to our products.

I'll copy the data out of it for you, however, for your convenience:

NTDLL.dll – The following is a quote from Microsoft Techs - “Heap metadata can become corrupted and it has been identified by Microsoft as one of the most common causes of application failures. When an application crash shows the faulting module as ntdll.dll along with the Memory Access Violation (0xc0000005), then Windows places the application on a watch list and, if the application crashes at least four times or more in an hour, the fault tolerant heap service will configure the application to use the fault tolerant heap service in the future” (Source - Chapter 10, Memory Management, Windows Internals, Part 2: Covering Windows Server 2008 R2 and Windows 7 by Mark E. Russinovich, David A Solomon, and Alex Ionescu). The service is part of the Security Center service so you need to make sure this service is turned on. If the ntdll.dll is placed on the watch list, this information will be shown in the Event Viewer (Admin Events). See also Increase Heap Limitation in the Actions to Take to Prevent Crashes section of this guide.

Several possibilities for the NTDLL.dll error are as follows:

  • Most likely cause is outdated or corrupted hardware drivers. Run a driver update program as discussed in previous section.
  • Use the System File Checker (SFC \scannow) to look for corrupt or missing system files. See previous section for details on running this program.
  • Recently update video card drivers? Reinstall or install the previous version.
  • System overheating. Check (not common but it can cause this crash).
  • Wrong timings/voltages set for your installed RAM. Use the utility, CPU-Z, to check or look inside the BIOS (NOTE: With newer Mother Boards and Memory Simms, this issue is not as common as it was with earlier systems but it can still happen).
  • CPU voltage too high or too low (only if you manually adjusted this in the BIOS). You might be able to fix by returning your BIOS to Optimized Defaults or lowering your overclock by one point from say, 4.4GHz to 4.3GHz.
  • Remove the UIAutomationcore.dll from the main FSX folder, if installed (applies to FSX users only). A known fix (could be the wrong version placed in the FSX folder).
  • Check your dll.xml for duplicate entries or entries where the software was removed but the entry in the dll.xml still exists. Fix.
  • Disable User Access Controls (UAC) (see the section above for more information).
  • Update hardware drivers for your computer (especially on new computer systems or if the Windows OS has been reinstalled or upgraded) (see Driver Update information in this guide).
  • Disable MyTrafficX, v5.4c or MyTraffic6a in the Scenery Library to see if this program is the cause of the ntdll.dll error. It is believed to be caused by an AI scheduling programming error. For MyTrafficX go back to the 5.4b version or make sure no external AI program schedule is activated (i.e., the 2012 or 2013 Schedules on the developers website). The default schedule appears to be okay for most. Check the developers support forums for updated information and possible bug fixes. For MyTraffic6, some have fixed it by renaming the MyTrafficmil.bgl to MyTrafficmil.orig.
  • Some have seen this error when changing to payware aircraft after using another payware or default aircraft.
23 minutes ago, Shopdog said:

Everything was working fine with the other add-ons, what makes the ngx so different than other add-ons?

How add-ons interact with your computer is entirely dependent on how they're built. If we call on your graphics card to render something and your driver is damaged, or outdated, it won't be able to render it and boom. Someone else may be using FSX-internal processes, or simpler methods.

Share this post


Link to post
Share on other sites

Ok Kyle, I did all of the above and "boom". So why with the same add-ons and even more so in my FSX version with this same exact plane I get no errors? Also, have seen a lot of other customers with the same problem with this plane and others, so we all have problems with our drivers, etc.

Share this post


Link to post
Share on other sites
43 minutes ago, Shopdog said:

So why with the same add-ons and even more so in my FSX version with this same exact plane I get no errors?

Not sure. This would point more to the sim environment than PMDG code, no?

43 minutes ago, Shopdog said:

Also, have seen a lot of other customers with the same problem with this plane and others, so we all have problems with our drivers, etc.

This would re-iterate the above (particularly with the "this plane and others" bit).

As I mentioned earlier, NTDLL errors are incredibly vague. It's like saying someone has a fever. All kinds of things can cause a fever. Solving the underlying cause needs to be done a many different ways. Your case may be different from others, but again, I point back to NTDLL error causes being numerous and wide-ranging.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now