vonmar

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.

Jason, Thanks for you additional reply. I seldom use the hud either but I ran into heavy fog at KSFO on final approach last couple flights ... so used it on repeat flights .... that's when I noticed the HUD problem. Thanks to your screenshot an reply I took another look at my PMDG aircraft. Found the problem (screen shots). Still using EZdok. Janet Livery PMDG737-600 HUD is bad. PMDG737-700 House (and Alaska) livery HUD is ok. I have no idea why Janet livery has a bad HUD in FSX and P3D?

Jason, Thanks for the reply and your screenshot. Much appreciated. Do you use Ezdok? I noticed your HUD is much larger than mine. Are you able to change your e.g. Baro knobs (EFIS panel) behind the HUD (lower right corner of the HUD? BTW, I am just using my normal VC view in my screenshot of the HUD (zoomed in and out) ... not individual EZDOK cameras to show the HUD. I set up EZdok cameras to show specific views of e.g., the overhead panel and the throttles.

I just took another look while zooming in and out and took two screenshots. You are correct, the HUD does zoom (entire hud and data) in and out. But the data in the HUD is clipping in the same way at all zoom levels. I was hoping another pilot with EZdok could tell me which setting is off.