Gerald,

It appears that 3.0.0.0 is attempting to add MSFS data during installation even when you select no during installation.

On installation of 3.0.0.0 the installation ask if you are using MSFS 2020, since I'm using FSX I selected no. After installation was complete, I started FSX and MCE.

1st issue, None of my voice scripts are being seen, on my default aircraft. I started to import them but I have over 40 scripts and the import function only allows one selection at a time (too time consuming). As I was troubleshooting it appears that there is a folder "other piston aircraft Asobo" in the C:\Users\~~~~\Documents\Multi Crew\Experience\MyVoiceScripts\Copilot\Aircraft, folder which, the one script I tried importing, went to. This is not my default aircraft and I did not see a way to direct MCE to see my default aircraft. Since I'm running FSX, not sure why this folder was created.

Second issue, I had MCE starting when FSX starts, this is no longer occurring.  The option to start automatically in the GUI was deselected and was unable to be checked. I tried editing the mce.ini file by changing the 0 to 1, but on restart it went back to 0. There was also an entry at the bottom of the mce.ini file referring to MSFS checklist which again since I'm running FSX I'm not sure why that entry is there. 

I did an uninstall and reinstall just in case I accidentally said yes to having MSFS installed but the same issues occurred. 

Any help is greatly appreciated.

 

Tony J

 

 

 

 

 

2 hours ago, Fighter Guy said:

Gerald,

It appears that 3.0.0.0 is attempting to add MSFS data during installation even when you select no during installation.

On installation of 3.0.0.0 the installation ask if you are using MSFS 2020, since I'm using FSX I selected no. After installation was complete, I started FSX and MCE.

1st issue, None of my voice scripts are being seen, on my default aircraft. I started to import them but I have over 40 scripts and the import function only allows one selection at a time (too time consuming). As I was troubleshooting it appears that there is a folder "other piston aircraft Asobo" in the C:\Users\~~~~\Documents\Multi Crew\Experience\MyVoiceScripts\Copilot\Aircraft, folder which, the one script I tried importing, went to. This is not my default aircraft and I did not see a way to direct MCE to see my default aircraft. Since I'm running FSX, not sure why this folder was created.

Second issue, I had MCE starting when FSX starts, this is no longer occurring.  The option to start automatically in the GUI was deselected and was unable to be checked. I tried editing the mce.ini file by changing the 0 to 1, but on restart it went back to 0. There was also an entry at the bottom of the mce.ini file referring to MSFS checklist which again since I'm running FSX I'm not sure why that entry is there. 

I did an uninstall and reinstall just in case I accidentally said yes to having MSFS installed but the same issues occurred. 

Any help is greatly appreciated.

 

Tony J

 

I suggest the following. 

No need to import files.

Windows Start-Multi Crew Experience-Restore factory settings.

Next, don't run the sim and run MCE.

The app wizard will run instead.

It will check that you're all setup.

Go through the wizard quicly. No need for speech training following an update.

The flows should be identified as per detected airplane.

There is a crucial file "Voxscript.ini" that when accidentally deleted from\My Documents\Multi Crew Experience\ folder causes MCE not to know where to direct for specific flows. Discovered this very recently. Restoring to factory settings, among other things, restores that file when you run the wizard.

Confirm all OK now. 

 

Gerald,

Attempted suggestion above, however it made things worse. After restoring factory settings, I started MCE with sim off. The app wizard started and made it through step 8. When selecting next it would then loop back to step 6 and do the same thing running the SAPI dialogue then the attenuation settings over and over again. Also none of the other issues above were addressed. When installing 2.9.8.3 everything works correctly. Again I am running FSX, and appears that the installation of 3.0.0.0 tries to add MSFS 2020 data.

 

Tony J

 

9 hours ago, Fighter Guy said:

Gerald,

Attempted suggestion above, however it made things worse. After restoring factory settings, I started MCE with sim off. The app wizard started and made it through step 8. When selecting next it would then loop back to step 6 and do the same thing running the SAPI dialogue then the attenuation settings over and over again. Also none of the other issues above were addressed. When installing 2.9.8.3 everything works correctly. Again I am running FSX, and appears that the installation of 3.0.0.0 tries to add MSFS 2020 data.

 

Tony J

 

Will be checked with FSX.

However, the wizard stalling at step 8 is an indication of something amiss, like speech engine not properly detected.

If you have V2.9.8.3, try running the wizard that comes with that version.

If it stalls just as the new one, then issue is with speech engine detection.

Be aware, tools like "IOLO system mechanic" are known to kill the speech engine in a subtle manner. It still shows up on the panel, but when a software tries to communicate with it, it fails silently, the result, the wizard still thinks it's not installed or selected.

And this wizard thing is completely independent of what simulators you intend to use.

Just so that you know.

MCE installs and runs as an external process.

Best to accept default installation path.

If it detects FSX installation, it will add these to FSXroot folder

fsInsider.dll

fsInsider.ini

<MCE dlls> folder

No files related to MSFS go into FSX, and not even "aircraft.cfg" nor "panel.cfg" are touched. Remove the added files above and you are back to pre-MCE installation.

The same is done when a specific version of Prepar3D is detected, except that fsInsider64dll goes in instead of fsInsider.dll.

In early days, when detecting which MSFS specific edition the user was on could have been tricky, we added that dialogbox asking wether you used that sim, so that if the automatic detection of the path fails, one could ask you to point the installer to the correct folder.

The other folders that are added are the new ones to support planes in MSFS. Those <ASOBO this> <ASOBO that> in \My Documents\Multi Crew Experience\My voicescripts\Copilot\Aircraft\ folder.

They don't do anything on their own. They just host flows for specific planes if and when they are detected. You could delete them all

If the plane isn't detected properly, then it's very likely you won't see the flows, even though they are there.

You can prevent the wizard kicking in by editing mce.ini

C:\Users\you_user_name\Appdata\Roaming\Multi Crew Experience\mce.ini

Open the file in Notepad and change "TrainingCompleted=0" to "TraainingCompleted=1"

While you are there, you can also see that the "start wit the sim" option is disabled by default (happens when you restor to factory settings). You will be able to enable it with FSX.

Next time you run MCE it will see that and run straight away. But it won't run as expected if

Will have a go at FSX today (as you never know what an update can do on less used things) and get back to you.

 

 

18 hours ago, Fighter Guy said:

Gerald,

Attempted suggestion above, however it made things worse. After restoring factory settings, I started MCE with sim off. The app wizard started and made it through step 8. When selecting next it would then loop back to step 6 and do the same thing running the SAPI dialogue then the attenuation settings over and over again. Also none of the other issues above were addressed. When installing 2.9.8.3 everything works correctly. Again I am running FSX, and appears that the installation of 3.0.0.0 tries to add MSFS 2020 data.

 

Tony J

 

Although no issue was found with scripts location when running under FSX, we are glad you raised the alarm, as there was a glitch with aircraft position detection (relative to nearest runway as we switched database very recently, and was mostly checked in MSFS).

Please download this patch, then manually replace 3 files in \Multi Crew Experience\ installation folder.

http://www.multicrewxp.com/Latest-Beta.zip

 Let me know if you're still struggling with the wizard and whether you used registry cleaning tools like "IOLO system mechanic", "IOLO registry mechanic".

Edited November 19, 20223 yr by FS++

Hey Gerald,

 

Thanks for the update. I've downloaded the update but have not installed it yet. Currently I'm  on 2.9.8.3. I ran the app wizard on this version with no problems. I do not have IOLO system mechanic, and have no other registry cleaning program running in the background. I'll give the beta a try and report back. Incidentally, My flying partner is running FSX with MCE also, and he had the exact same problem when installing 3.0.0.0.

 

Thanks for the continued support.

 

Tony j

42 minutes ago, Fighter Guy said:

Hey Gerald,

 

Thanks for the update. I've downloaded the update but have not installed it yet. Currently I'm  on 2.9.8.3. I ran the app wizard on this version with no problems. I do not have IOLO system mechanic, and have no other registry cleaning program running in the background. I'll give the beta a try and report back. Incidentally, My flying partner is running FSX with MCE also, and he had the exact same problem when installing 3.0.0.0.

 

Thanks for the continued support.

 

Tony j

The patch can only be applied to V3.0.0.0 because it assumes additional files and folders are already there. See "Instructions.txt"

 

Hey Gerald,

 

I was able to apply the patch today to 3.0.0.0 and everything seems to be operating normally now. I also ran the app wizard with no issues.

Thanks for the continued outstanding support of this great product.

 

Tony J

 

 

On 11/20/2022 at 8:24 PM, Fighter Guy said:

Hey Gerald,

 

I was able to apply the patch today to 3.0.0.0 and everything seems to be operating normally now. I also ran the app wizard with no issues.

Thanks for the continued outstanding support of this great product.

 

Tony J

 

 

Tony, because you´re using MCE / PF3 combination as me, may i ask if you struggle aswell from the issue, that the FO doesn´t seem to beeing "heard" by the facility very often.? Then you get the request "Traffic at FL123, squawking 1213, contact blabla on 123.45" on and on?

 

5 hours ago, BerndB said:

Tony, because you´re using MCE / PF3 combination as me, may i ask if you struggle aswell from the issue, that the FO doesn´t seem to beeing "heard" by the facility very often.? Then you get the request "Traffic at FL123, squawking 1213, contact blabla on 123.45" on and on?

BerndB,

Not very often. That may be because I do not use the MCE copilot to talk with ATC. I've found that when the PF3 VCP has control of the radios he's pretty spot on when responding to ATC. I use the MCE copilot to run flows and checklist, and the PF3 VCP to handle most of the ATC communications. It seemed to happen with me when I would use my voice to respond to ATC. I think it depends a lot on how things are configured in both programs.

 

Hope that helps,

 

Tony J