Hi Folks.

 

I have just purchased MCE & am in the process of setting up. I am having a problem with the way i want to set up my sound and i don't know if i am trying to do something that can't be done, so i would like some opinions or advice please.

 

I am using a separate sound card and a USB headset and i would like to speak to ATC & MCE through my headset mike, receive ATC directions/chatter through my speakers & receive mce talkback through my headset earphones.

 

I am running W7, 64bit.

 

One question: Can this be done?

 

Thanks,

This has been talked about before, although it has been quite awhile ago. What I remember about the discussion is that the sounds, e.g. engine, could come through the speakers and voice can be directed to the earphones and the mike esp. with FSX. I don't know why you would want ATC directions/Chatter to come through the speakers as ATC and other radio communication is always through the headphones.

 

Try a search and see if the subject is still available.

 

Jim D.

This has been talked about before, although it has been quite awhile ago. What I remember about the discussion is that the sounds, e.g. engine, could come through the speakers and voice can be directed to the earphones and the mike esp. with FSX. I don't know why you would want ATC directions/Chatter to come through the speakers as ATC and other radio communication is always through the headphones.

 

Try a search and see if the subject is still available.

 

Jim D.

 

I don't want all the chatter coming through my headphones constantly. I would rather just have my F.O. only, so that there is no confusion when he repeats back what i have asked him to do 90% of the chatter is nothing to do with me or my flight and sometimes i do not intend comunicating with ATC, my F.O. will. The times when i read back, i can read the dialog, i don't necasserily have to actually hear every word ATC says.

 

That's just my preferrence (right or wrong)

Regards,

The only thing I can think of then is to turn off ATC altogether in FS or FSX.

 

Jim D.

The only thing I can think of then is to turn off ATC altogether in FS or FSX.

 

Jim D.

JIM.

On playing with the volumes setup, it seems i can reduce the volume of ATC independantly from MCE., so this works out well as i now have the atc talkback much lower than my F.O.

 

Regards,

Glad that you found a solution that works for you.

 

Have fun.

 

Jim D.

Hi Folks.

 

I have just purchased MCE & am in the process of setting up. I am having a problem with the way i want to set up my sound and i don't know if i am trying to do something that can't be done, so i would like some opinions or advice please.

 

I am using a separate sound card and a USB headset and i would like to speak to ATC & MCE through my headset mike, receive ATC directions/chatter through my speakers & receive mce talkback through my headset earphones.

 

I am running W7, 64bit.

 

One question: Can this be done?

 

Thanks,

 

Certainly.

 

Use the provided “Assign sound device” tool for that matter.

 

Click Start->All Programs->Multi Crew Experience->Tools->Assign sound device.

 

When the window appears, select “USB device” in both Output and Input list boxes, then click OK. Let the wizard adjust things automatically for you.

 

Co-pilot will be heard on USB headset, and you’ll be using USB mike.

 

Now, to hear FSX ATC sounds through the speakers, go to FSX menu

 

Options->Settings->Sound…

 

When the Sound dialog appears, select the built-in sound device in “Voice” list box.

That’s where the ATC chatter will go.

 

Important: To save you some head scratching, suggest you plug the USB headset well before you start either FSX or MCE.

 

Otherwise, with USB headset missing, MCE will direct the FO voice to the speakers.

 

You can check what Input and Output sound devices MCE is using, by looking at the <About> tab of the user interface.

 

Hope this helps.

Thanks Gerald, but if i change the device in that dialog box, as soon as i exit that dialog box, it reverts back to the same settings as before.

 

The same thing happens with the assign joystick button for the RTT, will only assign to Saitek yoke button #11, no matter what button i press and it will not change.

 

What with the problems i am having with getting GSX to work with MCE, i am starting to wonder if i have a corrupt install.

 

Regards,

Thanks Gerald, but if i change the device in that dialog box, as soon as i exit that dialog box, it reverts back to the same settings as before.

 

The same thing happens with the assign joystick button for the RTT, will only assign to Saitek yoke button #11, no matter what button i press and it will not change.

 

What with the problems i am having with getting GSX to work with MCE, i am starting to wonder if i have a corrupt install.

 

Regards,

 

If the assign sound tool is always doing the same thing it means you are already set as you intended.

 

Currently, only joystick buttons 1 to 12 are accepted for PTT. The reason, many people are using CH throttle quadrant which has buttons 13 to 16 always on.

 

A similar issue arises with some Saitek joysticks that have some ALWAYS ON buttons. When you try to assign a different one through the UI, you simply can’t, because there is already one showing as pressed.

 

There is a work around though.

 

Open your mce.ini config file, found in

C:\Users\your_user_name\AppData\Roaming\Multi Crew Experience\mce.ini

 

Look at the [Joypad] section.

 

Leave the listed joystick name as is, and change “JoyButton=11” to “JoyButton=whatever_number_from_1_to_12”

 

Save the file.

 

It’s crucial to have the PTT set-up properly, otherwise if the assigned button registers as pressed, all voice commands for talking to FO will be disabled, and you would only be able to talk to ATC then.

 

Regarding GSX interfacing…

 

Nothing will work, until the GSX menu can show options related to various requests for catering, fuel and boarding.

 

Gate selection is not currently supported.

 

If you don’t have the relevant menu, chances are you aren’t parked properly.

 

There are specific airports where you may need to make the first menu selection manually, as John pointed out.

 

Simon (or any other agent) will handle requests for catering, fuel and boarding.

 

The idea is that like in the real world, you speak to the ramp agent, and he will do the rest.

 

Example, “Simon we need catering”. MCE will then make the menu selection, and when the catering van turns up, the purser will automatically open the service doors.

 

Another example. Say “Simon we’d like to start boarding”, and presto things happen.

 

Read GSX&AES commands document.

Start->All Programs->Multi Crew Experience->GSX&AES document.

 

MCE reads the info that GSX displays in the green bar (only reads it). It’s almost like having an SDK without Umberto needing to write one.

 

GSX tells you, open doors, MCE purser will do it

GSX tells you, close doors X, Y, purser will do it

GSX tells you, boarding has started, and mechanic will open the cargo doors.

Etc…

Etc…

 

Opening and closing doors is a challenge because it has to be done for every complex supported aircraft. We have done it for a number of aircraft, but you may come across one where the purser might not know how to handle the doors.

 

Requests for pushback have to be made to the mechanic.

 

You need to first establish contact with mechanic. Say “Cockpit to ground” (or any other dozen variations, see manual).

 

When ready for pushback say, “ground, are you ready for pushback”

 

When you want the push to happen say, “ground pushback left” or “ground pushback to the right”.

 

At some stage MCE mechanic will transfer you to GSX mechanic. He will assist you with start-up though. When pushback is complete, don’t forget to release him.

 

Say, “ground you may leave now”

Hi Gerald.

I answered your above response in my other thread regarding GSX.

Regards,