CFF-Explorer:

http://m.download.cnet.com/CFF-Explorer/3000-2383_4-10431156.html

 

Use the Resource Editor and open the configuration file.

thanks, now investigate.... B)  :ph34r:

I think what you are going to find is that just about every addon uses SimConnect for FSX SP2/ACC to communicate with whatever sim that one is using. SimConnect is just a communication channel and as long as the addon has its specific version installed, the connection should work correctly. Rob's original premise is interesting though. What if one uses the native ESP SimConnect to establish a network-based communication with P3d and then simultaneously on uses an addon like an A2A aircraft locally that uses a legacy version of SimConnect? In theory, everything should still talk to each other correctly, but you never know with good old MS.

 

Side by Side assemblies were developed by MS to overcome the hurdle of constantly providing a bloated version of a runtime library that was increasingly backwards-compatible with every possible app ranging from now back to the early Oolitic. SxS was designed for Visual C runtime libraries and things like common controls (COMCTL.DLL), which only impact one app at a time. But SimConnect allows communication among apps and libraries, so that makes it a bit unique.

I found four sim.dll's and also this esp one. In my opinion if no program is using it ....toedeldoki :rolleyes:  I don'see why it should be installed. I am running networked though, so I have to be carefull, ASN, EFB, wideview, AIcontroller. And even when a program is not networked, they still can use simmconnect.

Would be interesting to know if Simconnect ESP is installed together with Prepar3d v2.5. Two of the previous posts suggest that it is not installed together with Prepar3d v2.5. I have it installed on my system but that may very well be a leftover from Prepar3d v2.4 which was previously installed. If Prepar3d v2.5 doesn't install it by default then I would guess it's pretty safe to uninstall it if Simconnect for FSP Acc/SP2 is still installed. Just a thought...

Would be interesting to know if Simconnect ESP is installed together with Prepar3d v2.5. Two of the previous posts suggest that it is not installed together with Prepar3d v2.5. I have it installed on my system but that may very well be a leftover from Prepar3d v2.4 which was previously installed. If Prepar3d v2.5 doesn't install it by default then I would guess it's pretty safe to uninstall it if Simconnect for FSP Acc/SP2 is still installed. Just a thought...

I`m actually pretty sure it gets installed during the Prepa3D 2.5 installation, at least in my case. However, I`d like to know if the ESP Simconnect client package is extracted to C:\ProgramData\Package cache folder during the installation process (show hidden files and folders option needs to be ticked in the Windows Explorer)? Could someone please have a quick look at that folder, as I always delete the contents of the Package Cache folder as soon as P3D is installed.

 

Thanks in advance.

 

Regards,

Matej 

Hi,

 

I'll add my 2 cents,

 

I also have ESP Simconnect installed on my system. I never specifically requested that it be installed, however, it could have been done when I installed v2.4 or v2.5. I also have all 3 FSX versions of Simconnect installed as well.

 

Bill Clark

Thanks Rob, I installed that redist one yesterday to try to solve some issues, I'll be sure to check that I don't need it.

Does anyone know of a way I can reinstall the ESP Simconnect without having to completely reinstall P3D? Uninstalling it has caused problems with EZDock and the GSX Addon Manager.

I didn't have time to read through this whole thread just this second.  But I've mentioned that all the work that LM did on simconnect functions in 2.5 may be because they may be aware that it's a snake choking off performance the way it was written into ESP code.  I don't know this for fact.  But I do think that the more they can make a completely separate module out of simconnect functionality in P3D the better.  There may be objects instantiated just because simconnect is present that arent' used that just don't need to be.  Your observations may confirm that.

I'm don't actually code these days as much as I do architecture.  I hope that LM has a strong architecture lead, with almost feudal power.  Architecture is really not something to be done by committee, although all architecture and code must be defended logically.  But an architect needs to be an architect, and coders shouldn't need to be thinking about architecture.  Specifically, and architect needs to be immune from the egos swings of the coders.  Remember the story about the big rocks, the pebbles and the jar?   Big rocks first!

One addon that does use the native P3d  version of SimConnect is FSUIPC (from its log file):

59062 Running in "Lockheed Martin® Prepar3D® v2", Version: 2.5.12943.0 (SimConnect: 2.5.0.0)

Ok, took the time to read now.  A long time ago I looked at this simconnect mess because of a 6025 error I was getting.  IRC if a simconnect version module is loaded in to sxs folder it will load, even without a listing in the registry, but the registry listing must be removed in order to remove it from the sxs folder without receiving an error.  simconnect is a MESS.  It's using 20 year old methods, is sloppy as hell, like it was thrown together as a quick patch, and should be redone to use inheritance for legacy methods.  I don't know if LM has license to change it.   The best bet is to use the most current version until there is a problem after installing something that needs legacy.  There are only 4 AFAIK.  I still don't have FSX on my system, now I'm even more hesitant to introduce it.

Rob, once again really grateful for your great work towards our passions, like a bloodhound smelling out things like this.

 

One addon that does use the native P3d  version of SimConnect is FSUIPC (from its log file):

59062 Running in "Lockheed Martin® Prepar3D® v2", Version: 2.5.12943.0 (SimConnect: 2.5.0.0)

Pete probably knows more about this topic than anybody else.  We should find ways to make him talk!

I was thinking the same thing. He'll probably get back this weekend from his vacation, read this thread and have a good laugh at all the speculation. I can almost imagine the content of his post.

 

 

native P3d  version of SimConnect is FSUIPC

 

But I think Pete also uses the application memory offset hence the need to most of the time (not all the time) recompile and deploy for each P3D version change ... so Pete is static linking the managed SimConnect dll?  (meaning he would need to deploy the DLL with FSUPIC).

 

 

 

I don't know if LM has license to change it.

 

I believe they do, in fact almost certain they do as that's how the managed SimConnect was born ... correct me if I'm wrong but I don't think there is a managed SimConnect for FSX any version?

 

Biggest problem is changing SimConnect in an intrusive way WILL cause a 3rd party developer revolt ... almost certain of it.  But I thought the entire managed SimConnect idea was put in place to "help" 3rd party to do away with using Legacy SimConnect client?

 

Cheers, Rob.

I feel so lost when I don't have code to look at/debug.

But I think Pete also uses the application memory offset hence the need to most of the time (not all the time) recompile and deploy for each P3D version change ... so Pete is static linking the managed SimConnect dll?  (meaning he would need to deploy the DLL with FSUPIC).

 

 

You'll have to ask Pete that. He wrote his own SimConnect wrapper DLL with help from LM, at least that what the comment field on the DLL says.