Hi Bryan,I had a few good flights yesterday, back and forth between FSDT's Ft. Lauderdale and FT's St. Marteen with the Queen. Just a couple things I noticed which perhaps you might double check the next time you have the code open. The keys ini file was verififed to be in tact.

1. Doors and cargo hatches didn't seem to be operated by the crew anytime during the flows - I always had to manipuate them myself (keys were correct) Nevermind, I just remembered I had Doors disabled in FS2Crew options because these were AES airports.
2. Flow seems to automatically jump from starting engines to before taxi flow without cause, during pushback with AES (pushback = No in FS2Cew)
3. A stall in flow after "Recall" in the before take-off checklist - had to say next to get it to move on in the flow - noted on three seperate flights.
4. Continuing with a non-stop second (turnaround leg), FS2Crew main panel Descent Mode Dot continued flashing even though I continued with a new round of FS2Crew (45 minute countdown and Final Cockpit Preps) using the down-arrow.
5. One or two of the FO wavs late in the cockpit preps was heard over the PC speakers even though my Plantronics USB Headset was in use (and set in in FS2Crew GUI). All other FS2Crew wavs came over the headset as expected. Sorry, I can't remember exactly which ones - maybe cabin reports ready or something?

:(

Hi Al,Thanks for the feedback.1. Set pushback to 'yes' even if using AES. Just don't make voice contact with the FS2Crew pushback crew if using AES as there is no point. The mode should auto change to Before Taxi after the FO calls "good starts". I'll check to see how the mode could have switched before "good starts".2. I assume you mean the 'Before Taxi' checklist.The accepted responses for the 'Recall' challenge are: "Checked" or "Next"."Checked" is definitely in the grammar, so just make sure you're pronouncing it correctly. Double check the Green Bar to confirm that "checked" can be picked up.3. On the second leg, descent Mode will turn off again when you call for the "Runway Entry Procedure". So you're still okay. The sim is not adversely affected. Still, gonna have to fire my beta testers :( That one should have been picked up. In the next update, I'll turn off the flashing * during the after landing flow.4. That's not a bug. It's deliberate. The logic is the FO would not put on his headset until just before the doors close and he's ready to call ATC. So, during most of the pre-flight, even if Headset is selected, the FO sound will still come through the speakers; in fact, it'll come through the right channel as if the it's coming from a guy sitting to your right.Cheers,

Hi Al,Thanks for the feedback.1. Set pushback to 'yes' even if using AES. Just don't make voice contact with the FS2Crew pushback crew if using AES as there is no point. The mode should auto change to Before Taxi after the FO calls "good starts". I'll check to see how the mode could have switched before "good starts".2. I assume you mean the 'Before Taxi' checklist.The accepted responses for the 'Recall' challenge are: "Checked" or "Next"."Checked" is definitely in the grammar, so just make sure you're pronouncing it correctly. Double check the Green Bar to confirm that "checked" can be picked up.3. On the second leg, descent Mode will turn off again when you call for the "Runway Entry Procedure". So you're still okay. The sim is not adversely affected. Still, gonna have to fire my beta testers That one should have been picked up. In the next update, I'll turn off the flashing * during the after landing flow.4. That's not a bug. It's deliberate. The logic is the FO would not put on his headset until just before the doors close and he's ready to call ATC. So, during most of the pre-flight, even if Headset is selected, the FO sound will still come through the speakers; in fact, it'll come through the right channel as if the it's coming from a guy sitting to your right.Cheers,

Hey Bryan - glad you could use some of that info.

1. Now I understand better and thanks for double checking.
2. Now understand about the recall.
3. Let me know if I can help with a fiew lashings of the beta testers :(
4. Now I understand about FO and pre-flight except that most of the early FO announcements +45 to maybe +14 come through the selected headset - then it switches to PC speakers. (Let me double-check though - watching football yesterday while simming).

BTW, nice touch regarding the right-channel = closer seat. :Applause:Oh yea, BTW, how come I can select my Seitek Yoke button # 5 and # 6 for Red/Geen in the older FS2Crew, but voice version will not see any of my Yoke buttons? I understand the FSUIPC key workaround - I just thought it weird that I could directly select the buttons in the older versions, but not voice versions. Different DirectX API or something?Also, if you ever feel really motivated, I would like a hard-mute button selection added to the main GUI list as well (for all voice versions).

Bryan - just confirmed, FO audio during preflight @ T+40 comes through the headset. This was with the HS button "On" and USB Headset selected in the config panel. This is contrary to your above about FO audio over PC speakers until later in the preflight.

Oh yea, BTW, how come I can select my Seitek Yoke button # 5 and # 6 for Red/Geen in the older FS2Crew, but voice version will not see any of my Yoke buttons? I understand the FSUIPC key workaround - I just thought it weird that I could directly select the buttons in the older versions, but not voice versions. Different DirectX API or something?

I'm not sure. We used the same DirectX stuff.At any rate, I'm working on a simpler system that will do away with DirectX altogether. Cheers,

FYI, I addressed your issues in the V1.1 hotfix.Please check the pinned thread.Cheers,

FYI, I addressed your issues in the V1.1 Hotfix (except for the T + 40 headset audio which I can't reproduce).Please check the pinned thread.Cheers,

FYI, I addressed your issues in the V1.1 hotfix.Please check the pinned thread.

Thank you much Bryan for the timely patch FWIW, I completed the rest of that same flight last night TNCM -> KFLL and all FO audio with the exception of "Cabin Ready" during preflight and one other wav after landing, came through my headset. This is with the FS2Crew "HS" button illuminated and the "Plantronics Headset" displayed in the FS2Crew config panel. In addition to my system specs in my sig below, I have the Creative Soundblaster Titanium PCI-e card selected as my default OS audio in 5.1 surround mode. It also selected as my "Primary" audio device within the FSX audio options. Also, in the FSX audio options, I have my Plantronics USB Headset selected as the "Communications" device. This on a custom overclocked Win7 Ultimate x64 rig.Building and troubleshooting servers and workstations for a living, at this point I can't imagine why I'm hearing such a difference in audio output (it's almost backwards from your expectations).:(