• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

ESP Add-on

Messages
516
I think SimConnect clients wont work unless they're compiled with the simconnect.lib in the ESP SDK.

Si
 
Messages
324
Country
us-virginia
Hey Simon,

Actually, that's the other way around :-> SimConnect clients built with the SP2 version of the FSX SDK will also work with ESP v1 (it should actually support all previous versions, but I've only tried it with SP2 SDK built clients).

SimConnect clients built with the ESP SDK will only talk to ESP (FSX isn't foreward compatible with versions that weren't released yet when it was :-> ). I suppose FS11 and/or TS2 might have recognized ESP v1 clients, but that's a moot point now :-<

Tim
 
Messages
203
Country
unitedstates
Adding to what Tim stated, it seems you can always connect to get the version number of the server. Any attempts to use other functionality will give you a server version error in my tests, but you can always get the version number. This allows you to load a different client dll as appropriate for the server if you do dynamic client dll loading (ie, not using the built-in manifests).

Etienne
 
Last edited:
Top