1 hour ago, BerndB said:

Hi Gerald, it seems in the case of the "autodiscovery" there is still something different to the former version. As you may remember i´am using Jeehell in a homecockpit where the aircrafts are NOT installed in the P3D/Simobjects. For P3D 4.5 i have created an add-on xml which "injected" the Jeehell aircraft folders into P3D that it can find it and so MCE did with P3D 4.5. 

Now in P3D V5 the developer of Jeehell has already implemented the add-on xml which works exactly the same way as i did manually in 4.5.  But MCE can´t find the aircraft as it does in V4.5.

I have updated MCE to the actual .43 version but it don´t find the ac. I also tried to replace the fsinsider.dll and the patch files but MCE still can´t find the ac. Only if i copy the aircraft folders into the root folder "simobjects" MCE find the aircraft right away and everything is fine. But this is not how it should be. For several reasons it must be the case that MCE finds the simobjects also if they are injected via an add-on.xml. Because LM mentioned in the SDK that generally no add-on should be installed into the P3D root directories. This is for what the add-on xml was stated.

But at least because this xml variant worked in the pairing MCE-P3D4.5 but doesn´t with V5, my guess there is something not right yet in the simobjects discovery method of MCE.

cheers

Bernd

Go to \Multi Crew Experience\ installation folder.

 

Make sure you have "mce.exe" (V2.8.4.3) AND "dccalls.dll (V1.4.4.1)

Should also have fsInsider64.dll V2.8.4.3 in \Prepar3D v5\ folder

Unless it checks out, you need to ignore the patch and re-install.

If the Jeehell bus writes aircraft path to "Add-ons.cfg" in C:\Programdata\Lockheed Martin\Prepar3D v5\ folder, MCE should find it.

Eventually, manually add the path in sequence to that file.

No need to re-install aircraft or sim.

 

Edited April 30, 20206 yr by FS++

6 hours ago, FS++ said:

Go to \Multi Crew Experience\ installation folder.

 

Make sure you have "mce.exe" (V2.8.4.3) AND "dccalls.dll (V1.4.4.1)

Should also have fsInsider64.dll V2.8.4.3 in \Prepar3D v5\ folder

Unless it checks out, you need to ignore the patch and re-install.

If the Jeehell bus writes aircraft path to "Add-ons.cfg" in C:\Programdata\Lockheed Martin\Prepar3D v5\ folder, MCE should find it.

Eventually, manually add the path in sequence to that file.

No need to re-install aircraft or sim.

 

Hi Gerald, as always a prompt reply from your side, which is one main reason we never get nervous if sometimes MCE seems not willing to do what we want.

I´ve just cheked the files you mentioned an all of them are matching with the version no. you gave me. I added the path into the add-ons.cfg and then it works, but this is not 100 % the right way.

I think i found the reason. The Jeehell add-on.xml, beside many other add-ons, is not adding the path to the add-ons.cfg in "Programdata" folder. You know there is another add-ons.cfg in %/User/appdata/roaming/LockheedMartin/Prepar3D v5\ folder and this one MCE seems not to discover, because into this config many add-ons are adding their paths.

Or maybe i´am completly wrong. But the most important point is it works for me now.

Cheers

Bernd 

19 hours ago, BerndB said:

Hi Gerald, as always a prompt reply from your side, which is one main reason we never get nervous if sometimes MCE seems not willing to do what we want.

I´ve just cheked the files you mentioned an all of them are matching with the version no. you gave me. I added the path into the add-ons.cfg and then it works, but this is not 100 % the right way.

I think i found the reason. The Jeehell add-on.xml, beside many other add-ons, is not adding the path to the add-ons.cfg in "Programdata" folder. You know there is another add-ons.cfg in %/User/appdata/roaming/LockheedMartin/Prepar3D v5\ folder and this one MCE seems not to discover, because into this config many add-ons are adding their paths.

Or maybe i´am completly wrong. But the most important point is it works for me now.

Cheers

Bernd 

You're right in principle.

Could eventually have dll updated to look into the other folder if this turns out to be a frequent issue.

For now Jeehell seems to be the odd one out. Good to hear the workaround got it sorted.