I have my MCE volume set so that the FO or Cabin crew isn't yelling in my face during pre-flight. The trouble is that depending on which airplane I'm flying, at that same master volume, he might be be hard to hear during something like the After Takeoff checklist when the engines are going hard. I wish that I could stick in a parameter into the beginning of some of these voxscripts that could alter the volume on a case by case basis, to make it a little louder or a little quieter.

 

Similar is the subject of .wav files, and I'm starting to call a lot of these from my voxscripts for things like cabin crew announcements, so I'm running into some volume problems when playing those as well. Just like for the voxscripts, some of the .wav files I'm using are not at the optimal volume. I can go in and modify the .wavs, but it would be much more convenient if we could instead just insert a parameter such as .9 to specify play at 90% volume or 1.2, for 120%.

 

Would something like this be hard to do?

Just wanted to say that I just found a perfect way of doing one of the things I'm trying to achieve, getting pre-recorded cabin announcements to trigger at the proper time at the proper volume.  I had previously been trying to do that within MCE.  Then I remembered I had this old program called Flight Deck Companion buried away somewhere years ago.  I ran MCE as usual, but I had FDC running on a networked machine.  Though a fairly big multicrew simulator in it's own right, the only thing I had FDC doing was automatically triggering the Flight Attendant cabin announcements, as it detected certain events, like gate departures or descent, or landings.  I always thought FDC was cumbersome, but when utilized for just this one specific task of handling the flight attendant .wavs, It worked perfecto!   This is probably a better way of achieving cabin crew realism than me trying to spawn an MCE FA voxscript, playing a .wav after a pause, from inside the FO's flows.

Still be interested in FS++'s reply for those us without FDC or similar.

Still be interested in FS++'s reply for those us without FDC or similar.

 

Will put it on the wish list for 2014.

 

Trying to keep VoxScript as simple as possible. Many assume because it has the "script" word in it it must require programming skills, when all you need is put a bunch of English sentences in a sequence.

 

Even considered adding support for events, like script waits for you to pull the parking brake or do something in the sim that fires an event. Unfortunately, it's not guaranteed to work across all aircraft (especialy the non-MS ones), so would become a hit and miss affair.

 

One friendly thing we may add is FO making some sort of statement anywhere in the script. Like reminders to do this or that.

 

statement=Can you check oxygen your side

statement=remember to set altimeter

etc...

etc...

I didn't want to start a new thread for this, but since you mention "wishlist 2014", I'll throw something out there completely unrelated to sound volume.  How about configurable pushback?  As far as I can tell, we have to explicitly command the ground crew to stop the pushback.  This is certainly adequate, but it requires one to monitor the pushback progress while typically starting the engines.  So while I'm heads down watching the fan rotation, he's pushing us off into the sunset, or worse, AI aircraft.  It would be better if instead of commanding "pushback to the left" we could instead command "pushback to the left, 200 feet" or something that would let the ground mechanic know when to stop on his own.  Or at least the distances could be set in the GUI or even by hand in the mce.ini to a suitable default value.

If I could respectfully interject here.

 

Users of AES or GFX(?)  already have this capability with FS2Crew recently also showing interest.  Is it really necessary for FS++ to duplicate these efforts at the expense of other innovations?

If I could respectfully interject here.

 

Users of AES or GFX(?)  already have this capability with FS2Crew recently also showing interest.  Is it really necessary for FS++ to duplicate these efforts at the expense of other innovations?

 

I wouldn't consider it "really necessary," but since MCE already simulates an interactive ground crew and a pushback, it's more just a wishful suggestion for an improvement, and doubt would come at the expense of something else, or more important.   It think it would be convenient in any case for those that don't have AES or GFX.  I do own a couple of FS2Crew modules, and I happen to like it's pushback interaction better, but overall, I prefer the flexibility and customizeability of MCE, and have started using it almost exclusively over FS2Crew.