DWadsworth

My bad - FSUIPC was processing joystick inputs.

I'm running MT at 30% commercial, and 5% general. The problem has occurred with traffic set to 0%.

Since updating to P3D 3.3.5, 777 CTD on final approach and landing whenever A/T or A/P are disabled and inputs are made on the joystick or throttle. 737NGX works correctly and 777 autoland works as well. Manual inputs from takeoff up to final approach are not a problem. All software and drivers are the latest available. System: i7-5930K 4.1GHz, 32 G memory, 2x GTX 980 in single GPU mode on two monitors WIn10 14905 (although this problem does not seem to be Win10 version specific - has occurred on all Win10 versions from release of P3D). Saitek X52Pro with 7.0.53.6 drivers AS16 MyTraffic 6.0A ProATCX on separate computer AppCrash shows the fault modules as being either StackHash_e70a or PMDG_777X.dll. I have the detailed AppCrash dumps and a saved approach that reliably crashes during final. Thanks, Dave P.S. Can someone help me with how to paste text, etc. on AvSim? I cannot make it work. I'm using IE11.1. Must be a setting I'm missing.

Latest update, reinstalled P3D and PMDG 737NGX and the problem has gone away. Additionally, I ran sfc /scannow and corrected a problem with openCL.dll. Not sure which of the three things fixed the problem.

The problem is completely reproducible for me: the ProATC route is KHOU DCT LOA DCT DONIE DCT YEAGR KDAL SID LOA9 STAR YEAGR2, no transitions. I load the CO ROUTE and the legs show up as expected. As soon as I try to add the SID, I get the Program Pin Error. Manually adding the route works correctly.

I've reviewed the previous discussions on this, but cannot get the FMC to accept departure SID or arrival STAR without receiving this error. I have reinstalled the aircraft, and have tried long press menu button. Pro ATC/X is running on a client machine. This all works perfectly with PMDG 777. Pro ATC/X version 1.7.2.0. PMDG 737NGX P3D v 1.14 P3D v.3 Flight KHOU to KDAL. Are there any particular logs or other files that might help?

You need to install all three SimConnect applications. Go to the P3D executable directory, and go down to the folder "redist". Go into "Interface", then each of the following folders: "FSX-RTM", "FSX-SP1", and "FSX-SP2-XPACK". In each of these folders, go to "retail" then "lib", and then double click on "SimConnect.msi". This installs all three versions of SimConnect. Traffic Manager appears to use one of the older versions.

You were right, FSUIPC 4.946 fixed the issue.

New FSUIPC 4.946 fixed it.

I am encountering a problem with throttle control for both the 777 and NGX under V3. Both aircraft now run at a significantly higher ground idle speed with the throttle at idle. Setup: Win 10, P3D V3, Saitek X52 Pro, latest drivers, FSUIPC 4.945A, and freshly downloaded and installed 777 and NGX. Throttle calibrated in FSUIPC to provide idle at lower detent (with dead band) and reverse below detent. System worked as expected under V2.5. Under V2.5 the throttle behaved as expected and the N1 idle speed as ~22-25% for both aircraft. Under V3, the N1 idle is ~30+%, resulting in ground handling difficulties. Full power range is available including reverse. Flight idle may be higher as well. Any ideas on what is causing this problem or how to fix/work around it? Thanks

I have a bit different problem with an X52 under V3/Win 10. In PMDG NGX and 777, ground idle is now at about 30% instead of the expected ~22%. This seems to be a problem with PMDG. I have calibrated the throttle to go to reverse when pulled through the detent. The throttle behaves as expected and goes to full power and reverse. However, sitting at idle, the engines are running higher than experienced in V2.5. Everything worked as expected in 2.5. Off to PMDG...

+1

Yes, they work and the both the driver and profile editor work. You must follow their instructions, as the WHQL drivers will stay in place otherwise. The claims that I tested work.

980s as well are being affected. I have found that by selecting Single GPU in NVCP, both GPUs are working at about equal levels (20-40%) and my frame rate is much better. Note: I'm running Win 10 10130, and am using the NVIDIA Win 10 drivers, 352.86.

Rob mentioned switching from full screen to window and back to reset SLI. I did some testing and found that there is something going on between P3D and NVIDIA concerning SLI configuration. Using NVIDIA recommended SLI settings: Cockpit view - 33 fps, VC view - 21 fps, GPU1 8%, GPU2 27% Using Single GPU settings: Cockpit view - 74 fps, VC view - 30 fps, GPU1 30%, GPU2 22% Seems like the settings are backwards. Current solution is the set P3D to Single GPU and get a reasonable SLI effect. All the switching between using Alt-Enter did was switch which GPU was active when using the Recommended settings. I hope Rob adds this to his comments back to LM. P.S. On a single GTX980, using the same configuration I think I was getting ~40/30 fps. Configuration: Sensor Data: AIDA64 Test Case: PMDG 777-20LR at KIAH gate A14, P3D executed by opening the .xfml file, changed to unlimited fps and not black out second screen Display: 2x 1900x1200, 2x ASUS Strix GTX980 Processor: 4790k @ 4.6GHz, water cooled Memory: 16 GB Motherboard ASUS ROG Maximus VI Formula P3D FSUIPC, TrafficManager, GSX, FSDT KIAH, REX, REX Softcloud, Orbx Global, FreeMesh Networked ASN, ProATC X (Not running in these tests)