Hi ,dear friends FS2Crew team!

All is ok for me - but one ... )

See corrections below!

 

Why my PM making 500 feet collout as soon as i message to him- "Cleared" ? Independently from real RA readings..

PMDG SDK - not sending RAltitude to FS2Crew?

This wrong not timed phrase is very bad for hearing in RA 1900feet , for exanple.

Usualy,in Vatsim, i hitting Landing clearence in more higher RA than 500feet.

And i have no reason to delay my "Cleared" message to PM to real 500 AGL.

Can you disable word "500 feet" to "checked" untill best times comes? )

Let he turn Landing Lights Оn )

Forever yours, Alexey Luzin

 

PS . Where are Byork? Is all ok with him?

 

Correction- just tested without my "Cleared" and PM says "5 hundred feet" collout in correct RA altitude!

Some strange for me ... what happens with Cleared collout- may be bug??? I tryed this 3 flights before- allways when i call Cleared- PM told me "5 hundred feet" in 1 sec after...

Strange things happens..

I just finished 2 test flights OFFLINE. All is Ok..

But i have stranges in final approach ( described above) in Vatsim under voice controlled online ATC .

I use soft mute key with Transmit ATC key ,as written in manual and i see- it works fine..

btw I have good PC spec and licensed FSX ,NGX and FS2Crew

Any ideas ?

I'm sorry, I'm not really sure what the issue is you're talking about.

 

On-Line or Off-Line makes no difference to the program.

Sorry to wake up an old thread but I've noticed every so often the FO's 500 feet callout on approach isn't correct looking at the actual altitude/height.

 

Did I miss something on my side or is this a known issue?

I'd have to double check the code, but it's predicated on the data taken out of the nav data base.

 

If it's inconsistent, it could be a nav data base error (landing runway elevation).

Hmm...just want to make sure we're talking about the same thing here. I'm talking about the callout the FO does when the aircraft reaches the point on final when it's 500 feet above the ground. I don't understand how that value could be read out of static data somewhere?

We use elevation above the runway as read out of the FMC, not AGL. Why? Because what if you're flying over a big hill or there is a big valley.

 

So we use runway elevation.

 

Pls ensure your FMC is completed in full with an arrival runway selected.

 

Cheers,

I'm still not sure I understand how this works...what exactly is it that triggers the FO to do the callout?

 

I do understand the problem you describe though flying over a high mountain for example.

Hi Richard,

 

It's based on height above the runway... Descent mode must be functional... perhaps that's it?... make sure you run the Descent checklist.

 

Cheers,

 

Hi Richard,

 

It's based on height above the runway... Descent mode must be functional... perhaps that's it?... make sure you run the Descent checklist.

 

Cheers,

Hi Bryan,

 

FS2Crew is in decent mode and the callout is always made by the FO just fine so no problems there. What I see though on most flights is that when the FO make the 500 feet callout he very seldom make that callout when the aircraft actually is 500 feet above the ground but most of the times the altimeter reads a slightly different value. That made me believe maybe it could be a local pressure thing but I always have the correct altimeter setting below TA.

 

Not a big deal, just wanted to know if it was something I did wrong or some setting I missed.