Bryan, some questions/requests.1. Departure and Approach briefs. Since it's just a case of me saying whatever I please, I sound like Beavis: "Uhhh... uh, uh.. ummm, Uhhh... we'll takeoff and then climb up, and we'll turn left, or uhhhh, maybe right... uhhh...." Maybe your MD FO could write a script for the Departure and Approach briefs?2. PA announcements - I cannot seem to get the FA to respond to any of the "I'll keep you informed" etc messages.3. I can't seem to locate the appropriate response to give to the ground crew, at the end of the flight, after they advise that the chocks are in and it's okay to release the parking brake. Can you advise?4. In appendix D, "PAs for the Cabin Crew". I'm confused on how to use these commands to close the doors etc. Do I call the FA first? I tried to just say them and nothing happened.I miss the canned stuff (dep/appr briefs; PA announcements; FA dialogue) like you had with the LDS 767, PMDG 747, and ATR... just my opinion. The Voice control is okay Bryan, but I think I prefer the buttons primarily because they work 100% of the time. With voice, it seems like about 25% of the time, I either forget the command, mess it up slightly, or it doesn't understand me. Additionally, I notice pauses in FS when the voice module "listens". There's one in particular during the Taxi Check ("Set and Checked") that results in a good 1 sec pause which is pretty significant. I really wish you could do the button thing, but I know that's well out of scope. Again, just my preference. James

Additionally, I notice pauses in FS when the voice module "listens". There's one in particular during the Taxi Check ("Set and Checked") that results in a good 1 sec pause which is pretty significant. I really wish you could do the button thing, but I know that's well out of scope. Again, just my preference.

I notice that only at one point during the taxi check. The command is for the APU, and when I say "Both Off", everything stops for about 1-2 seconds, and he doesn't actually turn the apu off.Other than that, it's really about learning the "script", running the voice training, and practice. I put together a quick word document that combines the flows and the checklists, so that I don't have to keep flipping pages in the manual. That really helped!Thanks!

Bryan, some questions/requests.1. Departure and Approach briefs. Since it's just a case of me saying whatever I please, I sound like Beavis: "Uhhh... uh, uh.. ummm, Uhhh... we'll takeoff and then climb up, and we'll turn left, or uhhhh, maybe right... uhhh...." Maybe your MD FO could write a script for the Departure and Approach briefs?2. PA announcements - I cannot seem to get the FA to respond to any of the "I'll keep you informed" etc messages.3. I can't seem to locate the appropriate response to give to the ground crew, at the end of the flight, after they advise that the chocks are in and it's okay to release the parking brake. Can you advise?4. In appendix D, "PAs for the Cabin Crew". I'm confused on how to use these commands to close the doors etc. Do I call the FA first? I tried to just say them and nothing happened.I miss the canned stuff (dep/appr briefs; PA announcements; FA dialogue) like you had with the LDS 767, PMDG 747, and ATR... just my opinion. The Voice control is okay Bryan, but I think I prefer the buttons primarily because they work 100% of the time. With voice, it seems like about 25% of the time, I either forget the command, mess it up slightly, or it doesn't understand me. Additionally, I notice pauses in FS when the voice module "listens". There's one in particular during the Taxi Check ("Set and Checked") that results in a good 1 sec pause which is pretty significant. I really wish you could do the button thing, but I know that's well out of scope. Again, just my preference. James

Hi James,Make sure you run the Voice training. We have non native English speakers getting very high response recognition rates, so if you're only getting 25 percent something is wrong. I get over 95 percent accuracy. You might also want to consider using a headset if you're not already.1. Briefs... Samuli, if you're reading this, can you please write a MD80 specific brief people can use.Important: If you're doing a brief, make sure you hold the MUTE button down!!!2. "I'll keep you informed".... See first comment.3. Say "Go Ahead" when the Engineer contacts you at the end. He'll tell you that the chocks are in so you can release the parking brake.4. You just say them, but, generally speaking, you should never need to ever use them as FS2Crew controls all the doors. They're mostly there for backup in case a door gets thrown out of position somehow.5. Preference for the old button system: I know what you're saying. But some people love the voice system. It's boils down to personal taste. In the upcoming Jetsteam version I'm probably going to release two separate versions: One voice, one old style. 6. Your pauses... not sure. It sounds like your voice recognition system isn't working well that great and that may be a contributing factor. Again, definitely run the voice training. With even an ordinary headset you should be getting a response rate well over 90 percent. Best,

Jeff,Turning the APU and APU air off is something you would do. The FO will not flip the switch during taxi.You're just announcing what you're doing.So when the FO says:"APU AIR AND MASTER SWITCH".You'd reach up and set the APU air and Master SW as you desire based on the conditions, etc.You can reply either: "BOTH OFF"OR:"AIR OFF" if you want to leave the APU running but only turn off the air.Best,

Hi James,As a reply to your question about the briefing, the briefings have normally a very similar structure. Varying from airline to airline. And depending of course of aircraft characteristics and differences.basically the briefings consists of 2 main parts: Normal ops and abnormal ops.-Normal ops includes the normal departure with all considerations (limitations, etc....)-Emergency briefing is divided into 2 parts: -Before V1 (RTO) -After V1 (Wx, terrain in the surroundings, MSA & obstacles. Explanation of single engine profile, duty split, etc...)here comes a typical (invented) example:- TO RWY 15, Basud 5T departure. Climbing initially 7000'. Initial climb on rwy heading, after BS or 3.5 miles BLM, turn right heading 258, at radial 196 BLM turn left heading 074 to intercept R315 inbound WIL to Basud. (normal SID)- In case of any failure or malfunction before V1 you call it out or point it out, I decide either we continue, or abort by calling out "reject". i'll extend the spoilers, apply reverse thrust and maximum braking.You check the spoilers are out, otherwise call "no spoilers", and inform the tower. Once stopped, we analyse and decide about further action.- After V1... (PF briefs) we continue climbing to 1800' then with a right turn back to BLM holding pattern. Minimum acceleration altitude 2500' (normally 1500' AGL), climbing to 4500'. (check MSA, obstacles, observe WX hazards, etc...)I'll fly and take ATC, you check parameters and perform actions & memory items....Of course in the simulator you don't need to make it so complicated.I hope this helps as a TO briefing.