Good evening Brian,

 

Just got a new system, P3Dv3.1, PMDG/Aerosoft, all FS2Crew. All the titles work okey except for 777.

 

After the completion of descend check list when I start to descend I don't see that FO switches seatbelts signs to ON and he does not turn lights ON. As a result, I don't hear any other FO interaction before touchdown when I call for clean-up. It happens on each and every flight after I have new sim install. NGX and Airbus FS2Crew works OK. ANy idea what this might be?

 

Thanks

Dmitriy 

Hi,

 

Is the Fs2crew in descent mode?

The FO doesn't turn the seatbelt and the lights on when you start descending but passing 10000ft.

Also, what happens when you call for the approach checklist when passing through the transition level?

Does Fs2crew switch to approach mode?

 

The Fs2crew is conditional. To get the FO turning on the seatbelts signs and the lights on, you must be in descent mode and passing through the 10000ft. However, if the airport is at high altitude, it may be above 10000ft MSL (I believe it gets to 10000ft AGL above a certain airport altitude).

 

Then to be able to to trigger the landing checklist, you must be in approach mode.

 

To sum up:

_ Call for the approach brief

_ Wait for the FO to select Vref and flaps setting in the FMC approach page, to select the requested autobrake level, then call for the approach brief.

_ Check that Fs2crew main panel displays Descent.

_ Check the landing altitude to know when to expect the FO to turn on the seatbelt and lights on

_ Call for the approach checklist when you have passed the transition level and set the baro ref and check that Fs2crew displays Approach

 

And so on until the parking...

Edited January 30, 201610 yr by Budbud

BubBud,

 

Thanks for the response. I will definitely go through this routine again even though I have done it many times before. Also, I don't think that FS2Crew for 777 has Main Panel Such as "Climb", "Cruise" or "Descend". Old LevelD767 FS2Crew has that, but not 777. Perhaps I'm wrong.

 

Thanks again

Dmitriy

 

 

Also, I don't think that FS2Crew for 777 has Main Panel Such as "Climb", "Cruise" or "Descend"

 

Hi,

 

I'm not talking about panels called so but what is displayed on the main panel (only one main panel!).

 

But I'm using the voice version so the display may be different than the button version.

In the voice version, on the main panel you can see at what step you are may it be a certain checklist or a state like takeoff, initial climb, descent, approach, landing, clean up...

 

That is what I'm refering to. It gives you the state of Fs2crew and therefore you know what commands will be active or not.

 

For exemple, if the main panel displays "Descent", then the command "landing checklist" won't work as the commands are conditional on some steps.

I'm flying with the T7 right now so I can check the proper indications and I was wrong.

It is not "Descent", "Approach" and "Landing" but "Descent checklist", "Approach checklist" and "Landing checklist" sorry.

 

Sorry you can replace these in my previous posts to read correctly what I meant to say.

Dmitry,

 

Also ensure your FS units of measurement are set to "feet", not "meters" or any triggers that are altitude based will be way off.

 

And ensure 'Descent Mode' is on.  

 

The small flashing * (asterisks) symbol on the FS2Crew Main Panel display is your indication that FS2Crew is in Descent mode.

 

Best,

Hello,

 

I have made a couple of T7 flights in a recent weeks and here are my findings.

 

1. If you fly normal P3 session from XXXX to XXXX without saving and reloading the flight, FS2Crew works fine in a descend mode. No complaints.

 

2, However, if you save and reload the flight in P3D (which is typical for T7 long-hauls), you run into the problem I described in the initial post. No 10k landing lights switch, no 1000ft announcement, no "minimum' and "approaching minimums" announcements. I have asterisks flashing once AppBriefing and Descend Checklists are completed. When I reload the flight and activate FS2Crew main panel, I normally skip all the phases and get FS2Crew ready in Pre-Descend Mode.

 

So, your help would be much appreciated again

Dmitriy

Hi Dmitry,

 

Hard to guess.  I know from experience saving flights can cause issues with complex 3rd party planes.

 

However, it shouldn't affect FS2Crew - key word, shouldn't.  Computers can be strange.

 

 

FS2Crew pulls a lot of information from the FMC and the aircraft.  Was your FMC data current and was the FS2Crew Approach Brief Page setup properly?

Hi Dmitry,

 

Hard to guess.  I know from experience saving flights can cause issues with complex 3rd party planes.

 

However, it shouldn't affect FS2Crew - key word, shouldn't.  Computers can be strange.

 

 

FS2Crew pulls a lot of information from the FMC and the aircraft.  Was your FMC data current and was the FS2Crew Approach Brief Page setup properly?

 

Brian,

 

What do you mean by "FMC and Approach Brief setup properly". When I load a saved flight with T7 I have exactly the same situation in FMC as I had before saving a panel state. PMDG has done a terrific job in terms of optimizing saved flight situations. Also, as I mentioned above - all other phases of FS2Crew routine such as briefs, pre-descend procedures, after-landing procedures work fine with saved flight scenarios except for actual approach phase. Maybe I really doing something wrong, but I have no idea what exactly...seems like it's very small tiny item.

Are you a Russian?

 

Confirm your units of measurement in FS are set to "Feet", and not "Meters".

Yes I'm Russian that lives in US so I'm on feets inches and miles :-) I have no choice :-)

I will continue more testing and return. I feel that its my error, very tiny one, but cannot figure it out yet

Do all the other sounds work?

 

The trigger points for these calls are very simple.

 

I'm not sure if it's a sound issue or a trigger issue.