October 19, 20178 yr Followed instructions from this thread Unfortunately, it's still doing it. One incident per flight (not every flight) and the only work around is to close MCE and restart it. Do you have a de bug log or something similar? Thanks for any help.
October 19, 20178 yr Commercial Member 1 hour ago, jimble said: Followed instructions from this thread Unfortunately, it's still doing it. One incident per flight (not every flight) and the only work around is to close MCE and restart it. Do you have a de bug log or something similar? Thanks for any help. Debug log is only used for troubleshooting start-up issues. Which doesn't apply here. This involves setting "Debug=1" in "mce.ini". There is a performance penalty when that mode is set. While there was such an issue (FO occasionally not responding) in one of the previous builds, the latest appears to be more reliable. Make sure you install this one Unless at least 3 or 4 other people (on the latest build) chime in with the same issue, it could be something with your hardware. I give you an example. When MCE starts, it establishes a connection to the speech engine, itself set to run on a specific audio device. If you have an unreliable USB connection for instance, the audio device built into the headset could go missing for a few milliseconds, and that's enough to cause MCE to lose all its connection to the speech engine, and could even cause an "App Hang" on MCE side. This is one of the reasons we don't run the speech engine inside the simulator process. The slightest hiccup and your flight goes up in smoke. At least with this design, you're guaranteed to have your FO on arrival, and won't ever have to restart your flight. If confirmed, will be looked at. Gerald R https://www.multicrewxp.com
October 19, 20178 yr Author Oops i'm running 2.7.29. I'll get it sorted and see how it goes. Sorry about that and thanks for the reply.
Archived
This topic is now archived and is closed to further replies.