Stack hash errors unless I reinstall standalone manager.

[asegm08]

I've noticed lately that when I install a new add-on for example Aerosoft scenery or anything that changes the DLL I have to reinstall the add on manager or else I get a CTD error where a stack hash is the fault module.

As soon as I reinstall the add on manager all is fixed and I get no more error.

Is this because of the position of the add-on manager in the DLL XML.

Thanks using P3D 3.3

[virtuali]

As soon as I reinstall the add on manager all is fixed and I get no more error.  Is this because of the position of the add-on manager in the DLL XML.

Possibly.

The other addon is causing this, most likely because it uses a different/wrong version of Simconnect and/or a different/wrong version of the VC++ runtimes libraries (LM suggest to use the 2013 runtimes, which is what we use), might change the loading order so, by reinstalling the Addon Manager, which will restore itself as the first one loaded, might fix this, because by loading it before other 3rd party modules that use the wrong/outdated version of the libraries, force the sim to load the correct ones, which is what we use.

[asegm08]

As soon as I reinstall the add on manager all is fixed and I get no more error.  Is this because of the position of the add-on manager in the DLL XML.

Possibly.

The other addon is causing this, most likely because it uses a different/wrong version of Simconnect and/or a different/wrong version of the VC++ runtimes libraries (LM suggest to use the 2013 runtimes, which is what we use), might change the loading order so, by reinstalling the Addon Manager, which will restore itself as the first one loaded, might fix this, because by loading it before other 3rd party modules that use the wrong/outdated version of the libraries, force the sim to load the correct ones, which is what we use.

Should I uninstall the other simconnects or the VC++ libraries?

[virtuali]

Should I uninstall the other simconnects or the VC++ libraries?

If the errors goes away by reinstalling the Addon Manager, that's the only thing you can do. You (or we) cannot do anything to fix potential conflicts *between* the different version of the libraries that might happen if another module use a different version.