The version I'm using is still the .43 "experimental" version you linked to earlier.

 

Try this experimental package.

 

http://www.multicrewxp.com/MCE2547.zip

 

Reset "MaxConcurrentTasks=4" and see if flows are executed in a timely manner.

 

Besides the fix for the known glitch, one new thing in this build...

 

If user holds the PTT down in order to talk to ATC or Vatsim, the next scripted action is suspended until the PTT button is released.

 

This is to prevent FO's voice coming in the way when the script is verbose and you're struggling to hear that ATC instruction or your team mates.

Installed 2.5.47, and reset concurrent tasks back to 4.

 

Did two short flights in 737, both starting at the stand with engines running, first mce flow being After Start Flow.

 

First time I ran, the After Start flow did not proceed in timely fashion.  30 seconds to start the first item (engine generators), and then about 10 or 20 seconds between each item.  I reran it, and he did better the second time after I lost patience and demanded "Pay Attention."  The rest of the flows ran mostly smoothly, but sometimes the delay between items was clearly a little longer than the "Pause=X" specified in the script, which is generally not a problem provided its only a small difference.  I realize it is possible that Pay Attention is acting as a placebo, and that he was just about to do the next item and get busy again regardless, but at this time I still stand by the contention that Pay Attention actually is helping.

 

The second time I flew (exactly same flight) he did a little better off the start.  Had to say P.A. several times for several flows, but aside from Trav's normal bumbling, it was overall it was a pretty good flight.  Maybe a little worse MCE flow performance than in version 2.5.43 when I tried it out with the concurrent tasks to 10.

 

Might be percieving a little performance hit.  I run with the fps externally limited to 30, and normally during cruise the fps is actually being held back, but in this case it looked like it was struggling to make 30 most of the time.  Probably nothing unusual and maybe just a little fps paranoia on my part because you mentioned the solution might come with a perf penalty.  I should know better than to ever hit Shift-Z because it causes my eyes to burn in torment!

 

I don't think this new version made things better, but you also need to keep in mind how much better the flows are going overall compared to when I started this thread a while back.  I'm out of time to run more flights at the moment, but if you want I can turn the concurrent tasks back to 10 and run some more tests later.

 

 

I'm out of time to run more flights at the moment, but if you want I can turn the concurrent tasks back to 10 and run some more tests later.

 

Thanks for feedback. Will see what conclusions can be drawn.

 

The perf penalty I was referring to earlier relates to MCE's own threads execution (within mce.exe), not FSX.