I hope you can help me.

I am using FS2crew voice for some years now and it worked fine, but in the last days something wired happened:

When using the “SET HDG XXX”, “SET FL XXX” commands the numbers go on running.

In general I know about this issue. it happened from time to time in the past and a solution is also mentioned in the manual (switch “voice” off and on again).

But now it happens every time. Switching “Voice” off and on helps at first. The running stoppes, but with the next command it runs away again.

Often I have to do it 3, 4 times till it works normally again and the numbers don’t run away anymore...

Maybe not important but I recognized one thing:

Normally the numbers change slower when reaching the commanded value

e.g. hdg 300 current, “SET HDG 160” - first numbers are changing fast till maybe 170 then changing slower for the last few steps till reaching 160

now they still slow down before reaching the selected value, but pick up again and keep on running

also only happened with HDG and ALT/FL not with SPD (so far)

all other commands work perfectly

I’ve tried countless times even with preselected flights and switching the FS2C panel to the right situation.

I am also looking at the green bar in case the system understands something wrong or picks up things it shouldn’t. The commands are also correctly spoken. (as confirmed at the green bar).

I also did a reinstall of the software incl. SP but nothing changed. (it works fine with the ifly737 voice btw.)

Can you please tell me what is the general reason that these numbers sometimes (in my case always) run away. Since you mentioned it in the manual there must be something behind.

My specs.

Win 7 prof (all updates)

FS9.1

LevelD (all updates)

FS2Crew voice for LevelD767 incl. SP

As mentioned, didn’t have this problems before, don’t have this problem with the ifly737

I have my own system just for FS so nothing changed except the regular Win updates and a recent IVAP update.

Thanks for your answers

cheers

Stefan

If I start fsx with the new fs2crew configuration manager and select any of my leveld aircraft. I get a panel initiation failure pop up and fsx crashes. With many pop up windows flashing. I think they are the gauge approval windows on first install. They come up and go so fast that I can't read them.

If I start fsx with the fsx.exe icon and choose any leveld aircraft, they load just fine. I only get one menu for the fs2crew, I guess it's the main one once I click in the alt gauge. Does not see my headset, USB, and no language selection. Just blank. I can however control with voice my MCP . I don't here the copilot or fa.

I uninstalled and reinstalled fs2crew several times. I cleaned up my fsx.cfg file and removed all fs2crew entries. I also removed from the fsx file folder all fs2crew entries in the aircraft folder.

I am stumped. Don't really want to remove the leveld aircraft. Again.running as administrator .

Any thoughts will be greatly appreciated .

Frank

I just watched the Demo Video and find that the "Before start checklist" "Before take off Checklist" and "approach Checklist" seems something "Old"

As I know,based on some AFMs and QRHs from different Airliners and ages, Boeing and many Airliners changed their SOP at about 2005, for the entire Boeing fleet.

One of the most obvious modification are the checklist was reformed. So the Checklist along with the SOP from the demo video is not the same as what I know, the new SOP is more like something FS2Crew using in 737NG.....anyway,I think you can get more information about this than I do.

Since I also fly the IFLY 737NG, I do want the new SOP for 767 as well because it is intentionally maintaining fleet commonality.

I haven't purchase this product yet, Because I wander if there is a future plan for new SOP on LD767. And if it is,as new product or upgrade for this one? THX.

We currently have cabin crew seats for departure....'

But we don't have seats for landing.

Was that left out deliberately or was it z challenge to code that in..?

Thanks

Hari

I've installed FS2 Crew LDS 767 and the update and even though It confirms the installation is successful I do not get any messages when starting up FSX (gauge etc(and this is after trying all of the below)). When in a flight after selecting the FS2 Crew panel in the LD menu, clicking the vertical speed indicator doesn't bring up the FS2 Crew menu. The only way i can do it is if I select it through the views menu and even then all the panels appear black.

I have tried:
deleting the FSX.CFG file,
reinstalling visual C++ 2008 redistribute package
reinstalling FS2crew several times

using registry fix

I have also tried following the manual to no avail. 

I also tried a few other ways which I can't remember.
I have been through pages of forums with the same issue but the solution for them hasn't worked for me.

FS2 Crew doesn't show up in the start center, It's as if the whole system doesn't detect it being installed.

I hope this is all the info you need.

Please help ASAP as I'm dying to get started.

Thanks in advance.

Dean.

dean.walkinshaw@hotmail.co.uk

melcec

Exactly what the title says... Whenever I say absolutely anything, my F/O replies with "check".... the funny thing is that he also says it when I say "hello". This means that I can't carry on the flight anymore with FS2crew as I don't think there is a fix to it... I tried everything (even gone as far as disabling then re-enabling the mic and the voice recognition - still not resolved).

I noticed there is another thread about this on this forum but there was never any resolution, and I've also heard many other people experiencing the same issue, so I was just wondering if this issue will be fixed up any time soon!

p.s - Love the product (great development Bryan), just a few issues!

Additional info: already tried re-installing both the level-d sim as well as FS2crew = no success :(

Best Regards.

Hi,

I use fs2crew voice commander for level d 767 on fsx with fsdreamteam gsx.

I want to use gsx push back, I have disbale push back required in fs2crew config menu but I still need to say disconnect to ground' to before I can get gsx to push back.

Which doesn't sound right, is there anyway that step can be eliminated and I can continue calling push back via gsx menu ?.

You have a great product, if it can interface with gsx better, it will be a great experience for flight simmers...

Thank you.

1. How do I turn on the PA Panel? I've tried to click on the PA button in the pedestal and around it and no luck. Any ideas?

2. Master Panel - how do I turn that on? When I put the mouse over the Captain's airspeed indicator a finger icon shows up, but when I click nothing happens? Any ideas?

3. FA/Cabin announcements. This has worked in the past, but since I reinstalled on new machine it doesn't work. I've tried to use the scroll with the mouse and it doesn't work. Again, any ideas?

Love the product - have both the Wilco 737 and Level D. When I get the PMDG 737, I am def getting the FS2Crew version!

All the best,

Joe

Joe

When I install the fs2crew voice again after i completely install the fs2004 again ... I recognize a serious problem. The FO ist not turning on the APU, Bleeds, Seatbealts etc. pp. when I´m on the Before Start Procedure or Runway Procedure. Even if I acclerate the aircraft on take off it says v1 and rotate at 60knots and other stupid things. Before that I did not have the Problem. I also install the SP1. My current version is the 1.5 Voice FS2Crew Level D.

Greetings

Dominik

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.

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.

long time no hear from you ;-). I hope everything is running smoothly for you. Here is my problem:

although I noticed another thread regarding the issue of the copilot always repeating "check" on every command, this thread was too old to reply to ;-).

I have already downloaded SP1 but keep getting this problem. Is there any way to check that FS2CREW has indeed updated to SP1 and I have the correct files in place? Using Win7 btw.

All the best, Benny

I'm running Windows 7 64bit, Having this issue with FS9.

I just made total changes with fs9 "Assignments" and suddenly two flights after, I found the FO didn't do Before Star Procedure properly, "set sixty percent didn't work either".. some worked but many didn't, like Packs, APU, Fuel Config, Hydraulic, as a result I had to do it semi-manually. is editing too many key assignments causes these? I just want to make sure before I reset it to default. Thanks

regards