gollum65

It's a mic on a wired headset, although I only use the headset for the mic. May have to start plugging in the headset speakers as well and use those. I have no real way to keep the mic away from the speakers. The furthest they can get is about 2 feet. Yes, I did the voice training but I'm going to do it again with some ambient noise in the background. Hopefully that will get the computer to better pick my voice out from the in cockpit sounds of the LDS. It does pretty good recognizing single word commands but when I have to say phrases, such as how much fuel is loaded, it can't figure out what I'm saying.

Well I'm making progress at least.... I did figure out the IRS & Autoland issues, which in turn fixed the autopilot not working. I also figured out that in order to hear the FO I have to set FS2Crew to headset mode. That causes three other problems though. First, he hears everything he says and tries to repeat it, so I get a lot of looping. Second, if I have it on HS mode my speech isn't correctly identified so I have to turn off HS mode to issue commands then quickly turn it back on to hear the FO response. And third, I'm getting a lot of broken speech from the FO, although it seems as I turn the volume lower it seems to get better. But, at least I can get off the ground and flying with FS2Crew....and a fair amount of frustration.... Thanks again for your help.

Thanks for the response. I believe I might have turned up the crew volume, which is a problem since I don't have a mouse wheel (I use a trackball) so not sure how I'd turn it back down. Can I do that in the configs or something?

Hi all, I'm having some problems that are probably very easy to fix but I can't find the answers.... 1) My FO voice is so low and muffled I have to turn off the FS sound, boost the FS2Crew FO volume to 10 just to make out what he's saying. If the engines are running I can't hear anything. It's like he's talking through a very big pillow. I've tried all 3 FOs, the USA, UK, and EUR and they all sound the same. 2) But ok, so I can mute the FS sounds and stumble my way through the preflight and even get off the ground. Here's where the big problems start, on wheels up.... a) The lower left EHSI never comes on. It just reads "Tcas fail" and does nothing. The transponder & tcas are supposedly set by the FS2Crew FO so not sure what happened there.... B) The "No Autoland" warning is always illuminated on the autoland status gauge. c) Once I get the plane off the ground and run through gear up, lnav, vnav, flaps in, and center on command, even though all the indicators are properly lit on the MCP and the EADI, the autopilot never takes over the plane. This causes it to porpoise as it tries to climb, alternating between a space shuttle rocket till almost stall then to a nose dive till enough airspeed is built up to start climbing again. And the aircraft never turns on course. It just stays on the MCP heading even with Lnav enabled. And the worst part is I have no control. It's a complete dead stick to me. I'm just a passenger. I can fly the LDS 767 without any of these problems if I don't use FS2Crew and start it up myself and fly it as perscribed by the LDS checklists, developers, etc... Thanks in advance.

Ok, I believe I solved my own problem. I ran across the notes in the manual about how having 2 sound devices could be a problem and how the SB X-FI Extreme Audio drivers could be a problem so I just disabled the Soundblaster. Now FS2Crew seems to load...or at least I get to the "Before Start"message, which I never did before... Sorry to waste everyone's time.

BTW, FS2AUDIO.dll was in my system32 folder. It was 540kb and dated April 12, 2010. Just to be sure I dropped it into my recycle bin and installed FS2Crew again. It did reinstall the dll with the same date and file size, but I still get the crash. And yes, I do run FSX in windowed mode. Also, I've tried running FS2Crew in varying panel states in the LDS 2d cockpit and it always crashes as soon as I hit the VSI to start it.

Hello, I have a recently installed and fully updated version of FSX on Windows Vista Home Premium installed into it's default folder. I also have the LDS 767 for FSX with it's required updates and REX Essentials with it's updates. They all run perfectly. This morning I installed FS2Crew for the LDS767 Voice Commander Edition and it's SP1 update. I ensured that I waited until both installers completed, told me the product was installed, and the "Exit" button came up. I can start FSX, load up the LDS 767, and even import the FS2Crew panel state, but when I click on the VSI gaugue to start FS2Crew I instantly get a crash to desktop and Windows says the error is in module FS2AUDIO.dll I've reinstalled FS2Crew and its SP twice. I've reinstalled DirectX and even installed the SDK just in case. I've run through Windows Update and allowed it to update anything it wanted. I installed the most up to date video card drivers and audio drivers. I've taken all these steps this morning and I still get the CTD. My Specs: AMD Phenom II Quad Core B35 Processor @ ~2.9 GHZ 4 GB Ram Windows Vista Home Premium DirectX 11 NVidia GForce 9800 GT Soundblaster X-FI Extreme Audio VIA HD Audio Sound Chip Yes, I've always run dual sound devices and I keep both drivers up to date. I've never had a problem. One is for my mic while the other handles speaker output. I also always start FSX as an Administrator, along with REX and pretty much any other program on my computer. Here's the text of the complete error: Faulting application fsx.exe, version 10.0.61472.0, time stamp 0x475e17d3, faulting module FS2AUDIO.dll, version 0.0.0.0, time stamp 0x4bb01ad3, exception code 0xc0000005, fault offset 0x0003ba97, process id 0x708, application start time 0x01cd95bde0f6d643. Any help would be appreciated.