Jump to content

Sign in to follow this  
peter225

Co-pilot not doing his job

Recommended Posts

I am using FSL 320, and my co-pilot does not seem to want to operate many of the overhead switches and also will not turn off the AP.

He always says he is going to do it, but I have to follow him round and operate the switches manually. I have reinstalled both the 320

and MCE but it has made no difference. Any help would be greatly appriciated, thanks Peter

Share this post


Link to post
Share on other sites
2 hours ago, peter225 said:

I am using FSL 320, and my co-pilot does not seem to want to operate many of the overhead switches and also will not turn off the AP.

He always says he is going to do it, but I have to follow him round and operate the switches manually. I have reinstalled both the 320

and MCE but it has made no difference. Any help would be greatly appriciated, thanks Peter

Hi,

What MCE version are you running?

Using which sim? Prerpar3D V4, V3, FSX??

 

Share this post


Link to post
Share on other sites

Hi Thank for your reply sorry for delay been away all day.

MCE version is  2.7.70  and I am running fsx with acceleration

Share this post


Link to post
Share on other sites
10 hours ago, peter225 said:

Hi Thank for your reply sorry for delay been away all day.

MCE version is  2.7.70  and I am running fsx with acceleration

FsLabs A320 definitely fully supported under FSX, with Fo able to handle almost every moving 3D switch directly in VC.

I assume you installed MCE to default C:\Program Files (x86)\Multi Crew Experience\ folder. You have to do that when Windows UAC is enabled.

Since you have the DVD edition of FSX, make sure you set "fsx.exe" to run as administrator.

Go to \Flight Simulator X\MCE dlls\ folder and check you have "mcfslA3X.dll" as well as about 40 other dlls (1 per supported complex aircraft)

When that dll is missing, the default dll for unsupported aircraft (mcgeneric.dll) is loaded instead, and nothing will work with FSL A320 as almost everything except gear and flaps is using custom variables.

Should the dll be missing, go back to downloaded unzipped file and look under \Files\FSX\ folder.

Copy the entire <MCE dlls> folder and paste it to FSX main installation folder, overwriting anything that may be in that folder..

 

Share this post


Link to post
Share on other sites

Hi

Thanks for your advice, I can confirm that this Dll "mcfslA3X.Dll"  is in place, and underneth that is the same file with extention "ini"

Regards

Peter

Share this post


Link to post
Share on other sites
24 minutes ago, peter225 said:

Hi

Thanks for your advice, I can confirm that this Dll "mcfslA3X.Dll"  is in place, and underneth that is the same file with extention "ini"

Regards

Peter

If you have disabled Windows UAC, suggest you re-enable it to default 2 notches up the slider and restart your computer for changes to take effect.

Confirm the following...

When starting FSX, you're getting the Windows prompt to run as admin.

When launching MCE, you're also getting the prompt to elevate.

 

Share this post


Link to post
Share on other sites

Thank you I can confirm that putting the UAC to default has returned MCE to fully working. I turned the UAC off again

and it stopped working again but I did notice the following. In this state when the CP is checking for switches the FMC

flashes up three times and I have to manually start the FMC to turn the GPU on. I have turned the UAC to default but

would love to know why this has happened. Thank you once again for your help. Regards Peter

Share this post


Link to post
Share on other sites
1 hour ago, peter225 said:

Thank you I can confirm that putting the UAC to default has returned MCE to fully working. I turned the UAC off again

and it stopped working again but I did notice the following. In this state when the CP is checking for switches the FMC

flashes up three times and I have to manually start the FMC to turn the GPU on. I have turned the UAC to default but

would love to know why this has happened. Thank you once again for your help. Regards Peter

The days when you could take full control of the machine (Windows XP) are now over with Windows 10.

There are some hacks found on the Internet advising on how to completely disable Windows UAC (registry hacks).

As if Microsoft wouldn't know about those ways.:smile:

My guess, when Windows 10 detects Windows UAC or permissions system has been compromised in some way, it makes Windows more defensive (restricts privileges), all while giving you the "illusion" you have full control.

In this case, it won't let "mce.exe" interact with "fsx.exe" smoothly, blocking some but not all operations.

We recommend users don't tamper with folders permissions either.

All you need to do is keep Windows UAC at default, install MCE to default path (only takes 2 GB max including all recorded voice packs) and just set "fsx.exe" to run as admin.

See this thread to understand why messing with the protection system leads to all sorts of weird things happening. It could prevent a file from being generated inside a folder and things like that.

 

Share this post


Link to post
Share on other sites

One more little thing on this subject I am now getting a pop up box:

Failed to locate VoxKey commands profile!

custom commands will be ignored for this session

Share this post


Link to post
Share on other sites
Just now, peter225 said:

One more little thing on this subject I am now getting a pop up box:

Failed to locate VoxKey commands profile!

custom commands will be ignored for this session

This is an easy one.

Probably messed-up the Voxkey profile by accident.

Go to \My Documents\ folder and delete <Voxkey> folder

Run the app wizard. Windows menu Start->All Apps->Multi Crew Experience->run app wizard.

No need to go through speech training. You could even exit the wizard as soon as it starts. By then, it would have re-created a <Voxkey> folder with default settings.

Voxkey is just an editor.

Run it and add custom commands to the relevant simulator.

For FSX, open and edit the "FSX Demo.vkp" profile.

When done, close it.

At runtime, MCE will detect the running simulator (FSX, Prepar3D or FS9), then load the relevant profile, in this case "FSX Demo.vkp".

Whatever custom command is there will be made available for speech reco.

Speak any of those commands and whatever key combo is associated to it will be sent to the flight sim. 

Voxkey isn't suitable for items whose initial state must be known. It acts as a toggle, without checking anything.

You don't need to create custom commands for general interaction with co-pilot. There are tens of thousands of built-in commands for that purpose.

Currently 42 complex aircraft are fully supported.

Bear in mind, any custom command you create, must be different from all built-in ones by at least one character. Otherwise, the built-in command takes precedence.

 

 

Share this post


Link to post
Share on other sites

Sorry to be a pain in the A***, Vox sorted but I have found that MCE is working perfectly with Aerosoft A320/321 so am I right to asume this is a FSLA32X problem

Share this post


Link to post
Share on other sites
41 minutes ago, peter225 said:

Sorry to be a pain in the A***, Vox sorted but I have found that MCE is working perfectly with Aerosoft A320/321 so am I right to asume this is a FSLA32X problem

You have to be patient until Fo works out the current FCU HDG, ALTITUDE and VS before you can ask him to dial something with FSL A320.

You should se a text within the FS window telling you when FCU dialing is ready.

Apart from that, he should be able to click any other switch.

Which command are you having an issue with?

 

Share this post


Link to post
Share on other sites

As I said all works with aerosoft A320/321 except the APU button.  On the FSL A32X will not press any buttons at all, everything else he will do.

Share this post


Link to post
Share on other sites
9 hours ago, peter225 said:

As I said all works with aerosoft A320/321 except the APU button.  On the FSL A32X will not press any buttons at all, everything else he will do.

OK, will be looked at and if necessary, a new dll to go into \FSX\MCE dlls\ folder will follow.

 

Share this post


Link to post
Share on other sites
On ‎8‎/‎4‎/‎2018 at 11:23 PM, peter225 said:

Thank you will keep checking the forum

I just performed a check in FSX with Airbus A320-214 CFM Air Lingus livery and command "launch apu" executed as expected. A second repeated "launch apu" yields "apu already running" as expected".

Perhaps it's an issue connected to a specific variant or livery. Could you please tell me which one so I can check again?

Test was successful with "mcAsoftA3X.dll" in \FSX\MCE dlls\ version V1.0.4.3, digitally signed 21 January 2018.

As for FsLabs A320, it seems I have issues with installation itself, as I'm not able to click any button manually, even without loading MCE or any dlls in FSX installation folder. Will probably have to contact FSL, as a re-install didn't make a difference. I'm using V237 for FSX.

If yours is running OK, be aware of one thing...

FSL A320 is interfaced using a different methods than the ones used for Aerosoft Bus.

It relies on simulated clicks in VC, and it does work in FSX.

Because the click-spots are different depending on whether aircraft is using hi-resolution VC or a lower one, when MCE starts, FO tries to automatically workout the current VC setting.

At some point, you should see an on-screen message in red font (within FSX) telling you to keep FSX window in focus.

It is required so that FO can simulate a click on the "Hot Air" button. Then draw conclusions depending on whether the button was hit or not.

When the click doesn't happen, he'll use alternative known clickspots.

Basically, when he gets it right, all flat switches clicks will work. When he gets it wrong, none will be pressed.

A different technique is used for the external lights, FCU and ECAM. Are commands such as "taxi light on", "beacon light on" "fd on" "altimeter to standard", "ecam display doors" working, or is it every single command failing?

Go to FSX menu Options->Settings->Display.

Select <Aircraft> tab

Is option "high-resolution 3D virtual cockpit" enabled?

 

 

Share this post


Link to post
Share on other sites

HI, Just to let you know have not deserted this thread, pulling my hair out, using words you do not hear in church, but just may have got some success 'got to try everyrthing out first will keep you posted tomorrow or next day

Share this post


Link to post
Share on other sites

Well after a lot of trial and error I have come to the conclusion that it is my Windows 7 service pack 1 which is the problem. I had it working great for 1 flight yesterday pm, but when I tried later it had gone again. I did notice that when it is OK when it starts up you just get the red notices on the top saying co-pilot checking switches and then good to go. But when it is not going to work ie: pressing buttons the same red alerts are there but the MCDU flashes up three times in the left hand  corner. As well as that when you run the wizard at the end all she says is “nice to meet you captain  Pe” instead of  “Nice to meet you captain Peter Tyas” obviously something missing from MCE. Anyway to cut a long story short
I put FS2004 on my lap top, graphics not good enough for FSX then loaded MCE and guess what  Same Results  and both systems are running Window 7 service pack 1. So in my mind that rules out any fault in MCE or FSX so if you have any ideas on how I could clean this up before I do a complete reinstall it would be appreciated.

Share this post


Link to post
Share on other sites
18 hours ago, peter225 said:

Well after a lot of trial and error I have come to the conclusion that it is my Windows 7 service pack 1 which is the problem. I had it working great for 1 flight yesterday pm, but when I tried later it had gone again. I did notice that when it is OK when it starts up you just get the red notices on the top saying co-pilot checking switches and then good to go. But when it is not going to work ie: pressing buttons the same red alerts are there but the MCDU flashes up three times in the left hand  corner. As well as that when you run the wizard at the end all she says is “nice to meet you captain  Pe” instead of  “Nice to meet you captain Peter Tyas” obviously something missing from MCE. Anyway to cut a long story short
I put FS2004 on my lap top, graphics not good enough for FSX then loaded MCE and guess what  Same Results  and both systems are running Window 7 service pack 1. So in my mind that rules out any fault in MCE or FSX so if you have any ideas on how I could clean this up before I do a complete reinstall it would be appreciated.

Assuming the following...

- You installed MCE to default C:\Program Files (x86)\Multi Crew Experience\\ folder

- You set Windows 7 UAC to default 2 notches up the slider

- You set "fsx.exe", "fs9.exe" and any launcher app you might be using to start the sim to run as admin

- You are getting a Windows prompt to elevate these apps when you run them. "mce.exe, "fsx.exe", "fs9.exe"

I don't see a reason why you would need to wipe your system at this stage.

Try different supported aircraft.

If the issue is just with FSL A320, maybe the dll "mcfslA3X.dll" (the 32 bit one. I know the 64 bit one works OK) is screwed or something.

If nothing works with any aircraft, you may want to consider a complete re-install. This time, leave UAC at default as well as folders permissions untouched, and just set the flight sim apps executable to run as admin.

It's much safer, as you don't want malware to hit you as soon as you visit a rogue website, with UAC off.

 

Share this post


Link to post
Share on other sites

Tried your suggestion this afternoon but no luck. Had a problem about a year ago when I re-ran the wizard after a few speech problem it would not let me past the changing the SPI to English usa saying in a box that I had not got it when I had the wizard putting it to English usa. The only way I solved that was a re-install after many attemps by Ben to put it right. I will let you know the results and it will save me money re-installing and not going to the pub this weekend

Share this post


Link to post
Share on other sites
4 hours ago, peter225 said:

I will let you know the results and it will save me money re-installing and not going to the pub this weekend

Sounds like a good incentive 👍

 

Share this post


Link to post
Share on other sites

I GIVE UP!!!!!!!   Did a complete reinstall of windows 7 and FSX this weekend and all now seems to be fine except "he can't hear me"

Mic set up right plenty of green bar on mic set up, showing the right input device even checked in the MCE TOOLS assign sound device

just have to fly it myself

 

 

Share this post


Link to post
Share on other sites
6 hours ago, peter225 said:

I GIVE UP!!!!!!!   Did a complete reinstall of windows 7 and FSX this weekend and all now seems to be fine except "he can't hear me"

Mic set up right plenty of green bar on mic set up, showing the right input device even checked in the MCE TOOLS assign sound device

just have to fly it myself

 

 

Come on :tongue:

Giving up so close?

Nothing to re-install now.

Just need to make sure MCE has set the speech engine to listen on the correct audio device.

Go to <About> tab in MCE user interface and report what devices are listed under "Sound Out" and "Sound In".

Are you using a USB headset or a conventional one with 3 mm jacks?

 

 

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...