I've only started using FS2Crew recently, and am still in the learning process. Using the tutorial, and FCOM is proving to be an excellent way to success. However, I am having one issue that is beginning to drive me nuts. I've searched the forum, and FAQ, and can't really find it addressed. So, please bear with me.

My FS2C is configured to use 777's ECL. I understand, to a degree, that due to SDK limitations, FS2C interacts with it using virtual mouse-clicks, and not direct control via the SDK. While I've read that, I definitely have not internalized what that means in terms of "you should / should not do X". Specifically...

On several flights so far, my FO has lost ability to show me the ECL. He does seem to be going through it, while I stare at the blank/black 2D popup, or in some cases some other screen (STAT, for example). While, sure, I can use "set and checked" wildcard responses, or paper checklist I prefer to not do that, unless I have to. Once or twice, I was able to "recover" the ECL into an usable state, by going through the previous checklist, asking FO to show display something else, etc, but I can't seem to find an exact pattern that would recover the ECL into the state that FO can reliably use it from that point on. 

What am I doing wrong? I am using P3Dv4, and to the best of my knowledge, the latest FS2C and 777.

P.S. I have tried the obvious of completely uninstalling FS2C, reinstalling it, and making sure it was configured, and working. 

Hi Marko,

Are you manually changing the source selectors on the 777's front panel?

That's the only thing that could throw it off.

 

Yes, I have been using those - should I just have my FO take care of that, instead?

 

Also, I believe I had the "777 FORCE ECL PANEL CLOSED" set to YES, which I believe was a larger culprit than me messing with the front panel on my own. I'm in-flight right now, and after changing the mentioned setting, checklist behaves as I would expect it to. Tentatively resolved :-)

 

P.S. I will try to throw it off deliberately with the front panel, just to see what happens.

It appears that manually selecting ECL, does indeed throw it off. As I expected, FO simply selects ECL, which turns off the screen. It will still go through it though, just not show anything.

I can think of a simple workaround, btw. When running checklists, instead of going directly into ECL, why not first send some other display request (STAT?), and then ECL. That way you will ensure that ECL will always pop-up, even if it was manually selected to be displayed.

Similar trick can be used for pretty much all display modes, making them more reliable to display. This is, of course, assuming you cannot programatically read what's being displayed... if you can, then when asking for "display X", and X is already displayed should be a no-op. And in the case of ECL, you should probably skip sending this instruction.

I'll consider that method.

We cannot "read" what is being displayed due to SDK limits, but I like your idea :-)

Yeah, I figured you can't read that, but you can cheat it ;-)

Btw. is this the right place to send suggestions like these, or you prefer tickets? 

It's a support forum, so here is fine.

I know it hans't to do something directly with the topic but one annoing thing is that after every checklist the lower DU becomes black, I know normal but is there a possibility that the FO selects tha last shown page, ENG after the before TO check for example ?

 

I think it goes black because the FO turns off the lower screen at some point in the flight.  Perhaps Bryan can clarify.