I've tried launching a flight about 5-6 times now since purchasing it yesterday evening... Have yet to even get off the ground...My First Officer keeps failing to respond... Four times now, I've had to abort the whole process when I get to the point of asking him about the departure brief... Furthest I've got was to lining up and starting a takeoff roll, but rejected the takeoff and shutdown FSX again after he fell asleep in the lining up checklist or just after it...Pretty much every time I've had to stop at the departure brief question, he's also failed to ask me how my day's going when first starting FS2Crew--he just goes right to work... When I got to the runway (once), he failed to let me know the checklist was completed on at least 2 of the checklists. I'm fully up-to-date on the MD-82 and FS2Crew as of right now, running on Vista Ultimate 64-bit...I know my speech recognition is recognizing me, as the messages are coming up showing the right command..Any idea what I'm doing wrong?

Hi,Sounds like you have an an audio problem.Please do this:1. Make sure you install SP1 and then manually install the latest version of the audio engine.http://fs2crew.com/cart/Updates/FS2Crew_Audio_Update.zip2. If you've selected "HS" for headset, make sure that the audio device for your headset is selected on the FS2Crew Config Panel in the simulation.Otherwise, just don't select HS and the FO should be audible through your speakers.Thanks,

Hi,Sounds like you have an an audio problem.Please do this:1. Make sure you install SP1 and then manually install the latest version of the audio engine.http://fs2crew.com/cart/Updates/FS2Crew_Audio_Update.zip

SP1 was already installed... I followed the instructions in the audio update to the letter, and now my whole system crashes with a blue screen of death as soon as the opening create-a-flight screen should show up (since the Maddog is currently the active aircraft)...

2. If you've selected "HS" for headset, make sure that the audio device for your headset is selected on the FS2Crew Config Panel in the simulation.Otherwise, just don't select HS and the FO should be audible through your speakers.

It doesn't seem to matter if I'm trying to put the audio through my headset (which I pretty much have to wear for the microphone) or the main speakers...I forgot to mention... Even when my first officer is playing deaf, I'm still able to interact with the person who comes in asking about my fuel load...

Hmmmm, I'm not sure what's happening there for you.Please email me directly and let me know about your system specs.I'll want to do a Teamviewer session so I can see it first hand.Thanks,

I'll have to run some more test flights when I have time (or attempts at test flights, since I still haven't gotten as far as cruise yet because of the sheer difference of the voice commander from all the other versions I own), but I think I may have resolved the issue...I did a full uninstall and reinstall of FS2Crew (including manually deleting the fs2audio.dll file from both c:\windows\system32 and c:\windows\syswow64 in between)... Still got the bluescreen automatic reboot. Edited my fsx.cfg to reset the default situation to another flight not involving the Maddog, and now everything works and seems to work perfectly in the 2 flight attempts I've had time to make so far... Including making it up to 11,000 feet on one attempt before becoming too overwhelmed with keeping up with reading the documentation and stuff and having to bail out and quit... And this is all with the original fs2audio.dll file...Thanks, though... I'll certainly get in touch if the problem comes back...

I'll have to run some more test flights when I have time (or attempts at test flights, since I still haven't gotten as far as cruise yet because of the sheer difference of the voice commander from all the other versions I own), but I think I may have resolved the issue...I did a full uninstall and reinstall of FS2Crew (including manually deleting the fs2audio.dll file from both c:\windows\system32 and c:\windows\syswow64 in between)... Still got the bluescreen automatic reboot. Edited my fsx.cfg to reset the default situation to another flight not involving the Maddog, and now everything works and seems to work perfectly in the 2 flight attempts I've had time to make so far... Including making it up to 11,000 feet on one attempt before becoming too overwhelmed with keeping up with reading the documentation and stuff and having to bail out and quit... And this is all with the original fs2audio.dll file...Thanks, though... I'll certainly get in touch if the problem comes back...

I can't explain that, but glad you appear to have it resolved.