A320 FMGS B42/43

**asessa** · 11-23-2015, 05:20 AM

Hi Jl, i tried last release

1. The AutoLand annunciator always blink (CockpitSonic FCU)
2. When i changed the rwy for landing (according to the twr) no altitude constraints were recalculated
3. When i activated the ILS button , Glidescope and Localizer on the PFD always blink

finally, yesterday i tried P3Dv3 and i have too many low frames with your suite.
Without JH running i have 29.6 fps at Zurich, 13.7 frames with JH! (see the images)

With JH active

Without JH

**jeehell** · 11-23-2015, 06:38 AM

Hi

1. make sure you did not accidentally push it, or that it is not always forced pushed in.
2. You will have to live with it until VNAV is reworked, this is not a new issue.
3. Some other people reproted that, and it may seem that Hardware Connect causes the issue. I have not been able to reproduce it. I can only tell you to try play with graphics settings, or even try to deport the hardware on a remote computer...

Regards,
JL

**asessa** · 11-23-2015, 06:47 AM

Originally Posted by jeehell

Hi

1. make sure you did not accidentally push it, or that it is not always forced pushed in.
2. You will have to live with it until VNAV is reworked, this is not a new issue.
3. Some other people reproted that, and it may seem that Hardware Connect causes the issue. I have not been able to reproduce it. I can only tell you to try play with graphics settings, or even try to deport the hardware on a remote computer...

Regards,
JL

1. It didn't pushed .. How can i test if it is always pushed in ?
2. Ok
3. Do you mean the blink of PFD Glidescope&Localizer or the fps killer?

Best regards

**jeehell** · 11-23-2015, 06:53 AM

in 3. I meant the issue about FPS in P3D V3

Regarding the ILS scale flashing on PFD, it is linked to issue 1. I guess. No idea how to check that...try pushing it yourself first...