Somewhere in the documents it clarifies that when you put a //1 in the checklist he won't verify the item is set as you say.

 

But I've also seen //2 and //3 in some of the checklists, and am unclear on those parameters.  What do those do?

 

 

In some of the checklists, the FO will read the checklist item, answer it himself, and then move on to the next item.  Does that have something to do with the //2 or //3? It's actually an FO behavior that I would like to utilize further in some custom checklists I'm making.

Somewhere in the documents it clarifies that when you put a //1 in the checklist he won't verify the item is set as you say.

 

But I've also seen //2 and //3 in some of the checklists, and am unclear on those parameters.  What do those do?

 

 

In some of the checklists, the FO will read the checklist item, answer it himself, and then move on to the next item.  Does that have something to do with the //2 or //3? It's actually an FO behavior that I would like to utilize further in some custom checklists I'm making.

 

The option that gets the FO to read the checklist without checking the item status is the "NoStateCheck=1" under [Checklist] section in mce.ini. It's normally undocumented and mainly useful for people running hardware simpits.

 

The //1, //2 and //3 etc... serve a different purpose

 

//1 means, the FO replies as well (it's there for compatibility reasons. When we only had FO to contend with)

 

Since we added support for Simcheck A300 (a 3 man crew aircraft)

 

//1 Captain replies

//2 FO replies

//4 Flight engineer replies

 

//3 both FO and captain reply

//5 Captain and Flight engineer reply

//6 FO and FE reply

//7 All 3 crew members reply

Thanks, I'm writing that down now

 

Just to clear, if I call the FO to read the Checklist and stick a //2 in there, he will both read the item, and reply to it, and then move on to the next item without any response needed from me?

Thanks, I'm writing that down now

 

Just to clear, if I call the FO to read the Checklist and stick a //2 in there, he will both read the item, and reply to it, and then move on to the next item without any response needed from me?

 

I think you have a point. Because it looks like he checks items silently, and unless it's not in the correct position, moves straight to the next item without uttering a word.

 

Will probably need to add the audio feedback.

 

Edit: Ignore above statement. Behaviour should be as expected.