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.

Hi,

 

1. Did you turn up the crew volume on the FS2Crew Main Panel?

 

2. Please check the Level-D support forum regarding TCAS fail, autoland issues.

 

Make sure you have all updates installed for FS2Crew 767 and the LDS 767. Re-install them to be sure.

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?

Look in your App Data -> FS2Crew folder.

 

You'll see some config files.

 

There should be a VOL entry and you can edit that directly.

 

Cheers,

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.

Headset looping:

 

Are you using a headset or a built in mic?

 

You want to keep your microphone away from your speakers, otherwise you could wind up getting looping.

 

Basically the speech recognition system "hears" the FO talking, and thinks it's you talking.

 

Also make sure you run the Voice Training.

 

You should generally expect plus 90 percent accuracy results.

 

Cheers,

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.

Try getting a USB headset... they tend to work best.

 

Cheers,