vonmar

I use FSUIPC (newest version/Installer for FSUIPC4.DLL version 4.959) for all axes control / calibration / all aircraft. Hand fly PMDG737-600 ok then when trimmed, A/P engages ok. Routes LNAV/VNAV Approaches, Autolands ok.

PMDG737-600 problem entering a hold (screenshots). Current Navigraph navdata AIRAC cycle : 1613 APPROACHES APPROACH ILS09 FIX SARGS AT OR ABOVE 2000 FIX GATTO 2000 RNW 09 HDG 095 INTERCEPT RADIAL 120 TO FIX PGY FIX OVERFLY PGY AT OR ABOVE 5000 TURN RIGHT DIRECT FIX CAPUS HOLD AT FIX CAPUS RIGHT TURN INBOUNDCOURSE 088 LEGTIME 1 TRANSITION MZB FIX MZB FIX GATTO AT OR ABOVE 2800 FIX PI001 AT OR ABOVE 2000 SPEED 210 FIX OVERFLY PI002 AT OR ABOVE 2000 SPEED 210 FIX PI003 AT OR ABOVE 2000 SPEED 210 KSAN, rwy09 ILS missed. LNAV route to holding fix CAPUS looks ok on ND but 737 never entered the holding pattern. At the holding fix (CAPUS) the aircraft turned right, flew away from the fix about 3nm and started doing clockwise circles ...

"Is there any known compatibility issues with the newest P3D version (v.3.4.18.19475) of the 737NGX and the latest upgrade of P3D?" All ok here. "I have to call a window of my PMDG and I place it on the second screen so that it stops flashing." Do you use SLI?

Pmdg737 working ok here.

From Chaseplane site: "ChasePlane is currently in Alpha. That means that ChasePlane is not a stable" Before posting problems it would be good to mention your PC/P3D setup (currently testing software) and addons ...

There is no problem with FSUIPC 4.959 and P3D HF2

Edward, Which aircraft?

Noel, Which P3D version?

Which effects .. examples .. names ?

My test so far .. VAS usage is less by 78MB as previous flight .. same route, PMDG737 (P3D HF2).

Ok, that will work.

The link ... where is it going to?

Was your link to your AVSIM post here or did you mean to do P3D forum?

Nvidia site has older drivers as well as current one. Why not download a fresh copy of an older driver?

mine is 376.09 it is ok.

Jovabra, Which Nvidia driver version are you using?

Right, then normal speed should be no problem if already tested with fast slew?? Edit: but in my question to denali's post ... I was just wondering if his first test was a normal or slew speed ....

Are you running out of memory at high slew speeds?

Aggressively purging of scenery regions to prevent running out of memory at high slew speeds

I found the problem in EZdok causing the PMDG737-600 (-700, -800, -900 were all ok) HUD not to display properly in my main VC view. Somehow the one main Virtual cockpit "Pilots view" (not a specific HUD view camera) camera became corrupted for the PMDG737-600. Then when I brought down the HUD the HUD itself was too small and the data did not fit in the viewer properly. I deleted the one Pilot view camera from the Ezdok camera addon Virtual cockpit for P3D and created a new one. That one newly created camera (screenshot) in P3D also fixed the HUD problem in FSX (PMDG737-600). Thanks to Kyle, Jason, Andrew, and Jonathan ... all your inputs helped me locate the problem. Much appreciated.

No. I just see the problem with the PMDG737-600 (all liveries I tested) in FSX and P3D.

Could you show a screenshot of your PMDG737-600 HUD (expansion pack for FSX / P3D) like when ready for takeoff or at the gate.

Today I tested the PMDG737-600 (P3D) House Livery (screenshots). The HUD is bad. I only see the HUD failure in the PMDG737-600.

Andrew, Did you test one of the PMDG-737-600 liveries to see if the HUD was ok?

Today I installed the PMDG737-600 Westjet livery and it also has the HUD problem (screenshot). At this point I think it may be a problem with all PMDG -600 liveries.