When I use pushback, I usually (always?) get an EXTREMELY slow wav playing as pushback commences. It's like an old 45 being turned at about 1 rpm ! It's too slow to decipher what is being said, but it has certainly happened when I run over the mechanic, I'm not sure but this may be the only time it happens. FSX & al addons are otherwise running smoothly.

 

This brings me to the second issue, possibly connected - I seem to keep running the mechanic down.

I know this has been posted and discussed, but I cannot seem to stop it happening.

 

I have removed GSX to see if it cures it, and set mce.ini back to native, but I am still getting the slow playback sound.

 

I have MCE, FSCaptain, and GSX(currently removed). Could someone please clarify, do all three of these have the pushback option, and how can I ensure just one process is taking place? Can I choose which version I use?

Is the slow playing file connected to this issue?

 

I am getting good response from the ground crew - I say 'mechanic you can leave now', and he responds something like 'pleasure working with you, we are disconnecting'. Should I then wait longer? Is there a further signal (other than Travis saying 'I think we killed the mechanic').

 

I'd appreciate any help in resolving these 'minor' issues. The sound thing is a mystery to me, and it just takes the edge off the flight when I taxi to the active with blood on the wheels.

Is the slow playing file connected to this issue?

Perhaps it's just the mechanic coming back from the dead, getting tired of being run over :lol:

 

No need to be concerned with FsCaptain or GSX. In fact we encourage people to use those. Zero known compatibility issues.

 

It turned out a couple of mechanic William recordings were in the wrong audio format. That's why you're getting that strange phenomenon.

 

Voice pack will be fixed in next update (Saturday or Monday). For now, use mechanic Clive or Andy, as they aren't affected.

Perhaps it's just the mechanic coming back from the dead, getting tired of being run over :lol:

 

 

 

nice one!

Perhaps it's just the mechanic coming back from the dead, getting tired of being run over :lol:

 

 

Yes, it does actually bring to mind something from The Omen or similar

 

 

 

No need to be concerned with FsCaptain or GSX. In fact we encourage people to use those. Zero known compatibility issues.

 

It turned out a couple of mechanic William recordings were in the wrong audio format. That's why you're getting that strange phenomenon.

 

Voice pack will be fixed in next update (Saturday or Monday). For now, use mechanic Clive or Andy, as they aren't affected.

 

Ah ok thanks, I'll switch mechanic for now, and hopefully the message will clarify whether he is being run over or wishing me a good trip 

OK that has cured the devil talk thank you.

But the suicidal mechanic just will not get out from under my plane.

 

Please can you tell me what I am missing:

 

'Ground, Cockpit'

     'Did you want something, Captain?'

'Ground, Cockpit, ready for pushback'

    'Yep, we're ready, just give us a shout'

'Ground, Cockpit, push back to the right'

    Yes, OK, we're gonna push to the right this time'

'Ground, Cockpit, stop the pushback'   (had to say this or it would just keep going I think) 

    'Stopping the pushback'

 

Now I try many many combinations to get them to stand clear.

This one will make you laugh:

 

'Mechanic, stand clear, I'm driving away'

    'Yes, we shall call the fire engine for you'

 

I did manage to get one response:

Mechanic you can leave now'

    'ok, we are disconnecting, have a good trip'.

 

But when I moved forward, I STILL ran him over.

 

I just cannot find a sequence that results in me being sure it is safe to move, and if I do move, it turns out they are still under the plane !  lol

All running perfectly now. I wish I could outline what happened so that this post might help someone, but I am really not sure why it is now working again.

 

But I have tested my startup/pushback/taxi procedures over and over, first using FSCaptain for the pushback, and then using MCE for the pushback, and both methods work equally well.

 

Somehow along the line, I was triggering more than one of them, causing one to run in the background without my knowledge.

All running perfectly now. I wish I could outline what happened so that this post might help someone, but I am really not sure why it is now working again.

 

But I have tested my startup/pushback/taxi procedures over and over, first using FSCaptain for the pushback, and then using MCE for the pushback, and both methods work equally well.

 

Somehow along the line, I was triggering more than one of them, causing one to run in the background without my knowledge.

 

Good to hear that.

 

FYI if you want to use some fancy personal sentences like

 

'Mechanic, stand clear, I'm driving away'

 

You can do that too.

 

Just use the Voxscript tool which will translate the sentence above as an alias for "ground you may disconnect now" which is one of the expected sentences.

I'd like to but for some reason I just do not find it easy. I have tried to follow the voxscript.pdf but it makes little sense to me.
Sorry if that seems stupid, but there seem to be gaps in the instructions, as if it assumes knowledge that I do not have.

For example, it says

 

First you create your command, and it can be absolutely anything you want.

Example: “Please configure air con for bleeds off take” or “Let’s configure the

aircraft for bleeds off takeoff”

You then write one or many replies you’d like to hear before co-pilot executes the

script. One of them will be chosen randomly at run time.

Optionally, you can write one or more statements co-pilot would utter upon

completing the task.

Then you write the sequence of commands that are part of the script.

 

But it does not say where I do this - do I use notepad or Word? If I attempt to edit a script, in the MCE interface, I can not find any script relating to pushback or indeed any script for the mechanic. Even if I could, I would be reluctant in case I 'broke' the file.

If I knew where they were, I would back one up and then edit it.

 

It goes on to say:

 

Pack one off

Pause=2

Pack two off

Pause=2

Bleed valve one off

Pause=1

Bleed valve engine two off

Pause=2

Bleed valve APU on

 

It goes on to explain what Pause means, but there is no mention of 'pack one off' or what it does.

 

I'm sorry but it appears to be written by a) someone who certainly knows what they are doing (obviously), explaining to someone who knows what a) is talking about.

 

Don't mean to offend, it is meant to be constructive criticism, or else the other answer is I am stupid, which is equally likely, I just need an idiot's step by step guide to making a simple script that works.

Pack one off

 

Pause=2

 

Pack two off

 

Pause=2

 

Bleed valve one off

 

Pause=1

 

Bleed valve engine two off

 

Pause=2

 

Bleed valve APU on

 

The above are normal voice commands you'd speak to get the FO to perform one thing at a time. VoxScript is actually a misnomer. Should have been named VoxFlow.

 

All it does is allow you to create a custom voice command and have the FO execute a chain of commands in the order and pace you specify. This way, people flying for VAs can have accurate procedures irrespective of the airline they fly for.

 

Just be aware, there are scripts intended for co-pilot, others for Mechanic, Purser, and even FS user interface.

 

Go to Command tab of the UI and click <Voxscript>.

 

You will see a list of voice commands that trigger various scripts. Those are intended for the FO.

 

To create a new script for the mechanic, first switch to <Mechanic related scripts> at the top.

 

After that you can create a new voice command.

 

The recorded mechanic voice pack isn't as rich as the FO's, therefore in terms of random replies, don't expect much, unless a TTS voice was assigned.

 

Edit the script to add the existing voice command "Mechanic you may disconnect now", and your custom command will become an alias for the latter.

 

Will see how we can improve on the documentation. Might be too late for the next update though.

Just be aware, there are scripts intended for co-pilot, others for Mechanic, Purser, and even FS user interface.

 

Go to Command tab of the UI and click <Voxscript>.

 

You will see a list of voice commands that trigger various scripts. Those are intended for the FO.

 

To create a new script for the mechanic, first switch to <Mechanic related scripts> at the top.

 

After that you can create a new voice command.

 

The recorded mechanic voice pack isn't as rich as the FO's, therefore in terms of random replies, don't expect much, unless a TTS voice was assigned.

 

Edit the script to add the existing voice command "Mechanic you may disconnect now", and your custom command will become an alias for the latter.

 

 

Thanks for the reply Gerald, the main problem for me is that when I go to the Mechanic related scripts, there are none at all. So I can't open one and edit it.

I am really struggling to understand, if I create a new one called 'Ground crew stand clear', how do I know what to put in each box? I can type in an 'available reply', a 'completed task statement', or I can 'edit script commands', which brings up an empty sheet. But I have no clue what to put in any of them. Again I'm sorry, I must seem really dense. I am certainly no computer language programmer, but I am not a stranger to editing config files and the like, so I really think it should be something I can cope with.

I'd really like to get to grips with it but I am totally lost.

 

Anyway, I appreciate your trying to help, but please don't waste any more time on this on my account, I am enjoying the program perfectly well as it is, I might try some again with a bit of trial and error to learn this when I get chance lol.

 

 

if I create a new one called 'Ground crew stand clear', how do I know what to put in each box? I can type in an 'available reply', a 'completed task statement', or I can 'edit script commands', which brings up an empty sheet.

 

I know for most people the word "script" suggets some programming involved. I can assure you it's nothing like that.

 

All you have to do is type existing (built-in) voice commands and put them in the sequence you want.

 

In our Mechanic intended script, don't use the "available replies" or "completed tasks statements". Just go to the Edit commands area, click the button "Add new command"

Type the existing command "mechanic you may leave now", press OK and save twice.

 

Your newly created voice command "ground crew stand clear" will act as an alias for "mechanic you may leave now".

 

 

If one thing, maybe documentation doesn't explain it well.

Hey Gerald, since the topic has drifted to Voxscripts, did you guys ever give any consideration to the "overidde" defaults ability that was suggested by a few?  You know, to use a dumb example off the top of my head, I could create a script called "Go Around" that executes the contents of a custom script instead of triggering the default Go Around command that is already built in to MCE.  Not a major necessity, but having such an option might save the user from having to remember an intentionally non-standard or awkward phraseology in certain situations where they want the crew to do something different from the hard-coded generic MCE behavior.  

 

 

did you guys ever give any consideration to the "overidde" defaults ability that was suggested by a few?

 

I'm afraid this isn't technically possible. At least not now.

I hate to resurrect this post but my 'running over the mechanic' problem has just reared its head again & it is driving me mad.

I uninstalled/installed some addons due to another problem (not mce related), and having arrived back at my full installation, everything runs smoothly except this.

 

Can you please tell me

1)is there a particular order that I should install, and/or load MCE and GSX in order to get them to interact properly?

 

2) what exactly do the two lines relating to this in mce.ini do ? I have set the mechanic line to 'native' and 'GSX'; and the GSX/AES line to '0' and '1', and any combination of these, and it makes no difference that I can see.

 

It is NOT caused by the voice recognition, or the commands I am giving - when it works, it works perfectly so I know what commands to give.

 

This problem seems to arise either from the sequence that I install MCE, GSX (I believe just those two but what about FSDT Las Vegas, does that have any pushback involvement?) OR from the sequence that the programs are initiated, OR from another setting that I am missing or only accidently setting.

 

Finally, it leads me to ask if it would be possible to have, in a future update, a means of finalising the pushback process beyond any doubt - for example a 'mechanics stand clear' command that not only elicits a verbal response, but also switches the process off.

Obviously I do not understand the programming, but if it is possible to tell Trav to switch nav lights on, then is it not possible to tell the pushback sequence to end in a similar way, either by switch or voice?

 

It is such a minor point, but after going through flight plans, boarding, clearance, pre-flight checks, and pushback, it just spoils the immersion to then grit my teeth, start to taxi & run over the mechanic.

Can you please tell me

1)is there a particular order that I should install, and/or load MCE and GSX in order to get them to interact properly?

 

2) what exactly do the two lines relating to this in mce.ini do ? I have set the mechanic line to 'native' and 'GSX'; and the GSX/AES line to '0' and '1', and any combination of these, and it makes no difference that I can see.

 

Hi Antonmorse,

 

I run FSX + GSX + MCE. So :

 

1/ Normally if you installed GSX it loads with FSX, right ? ok, now you launch FSX/GSX then you choose a plane or any save situation.

Wait to be in the cockpit at the terminal and only after that you launch MCE. NOT before ! Wait a short moment (the time for MCE to load characteristics of the plane). When the message "Ready to go" is displayed (up left screen message) you are ready to go also ;-).

 

2/ Again if you have FSX/GSX.

Open Mce.ini file.

Under

[OPTIONS] you must have 

GroundServicesMode=GSX 

under

[MECHANIC] you must have

PushWithGSXandAES=1

 

No more no less ! Have you these setting ?

 

Hope this help.

 

Regards,

 

Richard Portier