Balint Szarka

I seem to have gone down the same way as you Ray. I had SODE jetways and SODE objects reloading repeatedly after the update from v1.8 so I uninstalled v1.8 and have gone back to v1.7.1 which work nicely again. I don’t know what’s gone wrong with the 1.8 version…

Unfortunately it doesn't seem to work neither in the 757, nor in the 767. I tried writing set takeoff flaps or select takeoff flaps as a script. None of them seem to work, except the voice command. That works.

I have just replaced all the provided files but the FO still doesn’t automatically set the takeoff flaps when assigned in the script. When I test it via the GUI, he says “setting takeoff flaps, confirm flaps 5” - I do answer yes but nothing happens either. Not like my aim would be to announce set takeoff flaps, I would rather want him to do it automatically when I say before taxi procedure, which for the moment doesn’t seem to work, for me at least…

I believe so, but to be sure I will replace them again and see if it works. Yes all characters are lower case. I do use Notepad++ to edit the scripts but I am aware of the drawbacks of doing so (causing to insert extra lines, and having to be careful of writing everything in lower case)

I have just tried with select takeoff flaps in my script and it didn’t do anything with the flaps…

The voice command set takeoff flaps works now, however in a script it does not. Is this the intended way for it to work? Otherwise thank you for your continued work.

Looks like that doesn't work. I just tried. So then I just have to work around it then. Thank you for your help.

Dear Gerald, First of all thank you for fixing the problem with Lower EICAS being put to STS on the 757. Very appreciated your help. I come to you or anyone else who might know whether there is such a command as set takeoff flaps? As I browsed around other planes within MCE main folder to see what could possibly be possible for the CS 757 as well, as there seem to be a lot of undocumented features. The set takeoff flaps command is quite handy to have as stock Boeing procedures usually call for the pilot monitoring to set take off flaps. I understand that every plane has different things that MCE can accomplish with but I am wondering if set takeoff flaps command would be a general command that the FO could interpret based on the selection made in MCE window (monitor weight, speeds, takeoff flaps and so on)? I have tried to write it in one of my flows prior take off but the FO doesn’t seem to touch the flap lever whatsoever when he goes through this line.

That's amazing, the issues seemed to be indeed fixed now. Thank you very much Gerald 😊

Hey again and sorry for the delayed response. I was away from my flight sim PC for a while. I just checked and here is what I found: I went on to check the only variant of the 757 I used so far to set up MCE. Which was the CS_B757-200-III_RB535E4B. That particular plane and livery had [fltsim.2] title=CS 757-200 United Airlines N41140 sim=cs757-200_RB535E4Bw written there. Which I guess is the expected answer, isn't it? I also checked the other engine variants of the 757's and all had a very similar text in that field.

Oh great 😌 thank you 😊 That’s very promising! 👌

While I do have some checklists that mention recall but none of my checklists have EICAS Status page mentioned. The FO just presses the Status page upon completion of any checklists which is rather annoying especially if the FCOM calls for the lower DU to be blanked like most Boeing aircraft. You think that it could be a bug?

I see, but the 757 doesn’t have Electronic Checklist. It’s a little annoying that upon completing the checklist he pushes the STS button though… Some real life checklist / flow will finish with a certain display selected however this automatic switching overrides it no matter the user’s selection. Thanks for tips on what to read on the forum. They are very helpful

Deleted

First of all I am a newbie to MCE however I am learning a lot and grasping most of the things I read on the forum here and refining my own procedures based on some real word ones. My issue with the virtual FO is that on completion of every single checklist it presses the Status button on Captain Sim’s B757. I am aware of a command that one could assign to press either Engine button do display the secondary engine indications as well as the Status page on the lower EICAS however I am not using them in either flows. And obviously the checklists shouldn’t trigger them. Could anyone help with it, why is it happening?