![]() By default DLLs are searched for in the “executable path”, so the breaking app should continue working by finding the SimConnect.dll in its own path (again, you find a copy of SimConnect.dll in your FS 2020 installation directory).īut then again, I wouldn’t worry about 1.75 MB of disk space either So if you really wanted to get rid of this “SimConnect Client” package you could uninstall it, figure out which add-on(s) or external applications break and then copy SimConnect.dll into their application directory. SimConnect from the MSFS SDK 1444×320 21.2 KB The bottom line is: that “SimConnect Client” package certainly does not come installed with FS 2020, so uninstalling it would not break FS 2020 itself! In fact, I don’t have that package installed myself: for the Steam edition of FS 2020 that libary is located here:Ĭ:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator That SimConnect.dll even is included in the FS 2020 installation directory itself, so third-party apps could dynamically link against that instance (if they didn’t want to ship their own copy). So Little Navmap certainly would not break if you uninstalled this “SimConnect Client” package. One approach would be that every third party application would ship its own copy of said SimConnect.dll, e.g. So if you would uninstall that “SimConnect Client” package then that (possibly multiple) add-on that installed this package in the first place would break.īut that doesn’t mean that all add-ons would break, as there are certainly multiple ways how an add-on (external application) can link to / find the required SimConnect.dll. It is certainly very likely that some add-on installed this “SimConnect Client” (which in the end is a single SimConnect.dll file, the “client library” with which third party add-ons / external apps can communicate with the Flight Simulator, as also explained in another post here - and possibly some “helper / test” applications which go along with it, as the installed package claims to take 1.75 MB, whereas the actual (as of the latest MSFS SKD) SimConnect.dll is a mere 57 KB in size). I don’t think this answer is 100% correct. Anyway, given that the PC desktop connected to the same router as the Mac is working just fine and not getting the error message, I dunno what i ought to be doing about router ports at this point.Do NOT uninstall this if you ever want a chance at making sure your sim works properly with any other 3rd party program. The PC desktop gave no error message, the Mac gave the message that I mentioned (although followed by the message that sets out the access key and says the configuration can't be reached from the internet, about which I don't care), and the PC laptop is caught up in a "failure to update" loop that I will have to address by uinstalling and reinstalling. I am at work now, but just tested remotely the server settings on the three versions of JRiver that are on computers connected by ethernet to my router (a PC laptop, a PC desktop, and the MacBook Pro). I manage ports on the router rather than on the individual computer, which, I guess, is how it's usually done. I am a bit confused about the port numbering issue. This time, I got the same error message when testing connection on the Mac, but was able to connect and run things headlessly using Gizmo without a problem and despite the error message.
0 Comments
Leave a Reply. |