That would be wonderful if this would work! I keep this in mind once I come around testing the “network part” of SimConnect (I first need to get hold of a second Windows installation to actually be able to test this, e.g. a virtual machine of some sort).
Now that raises the question where the SimConnect.cfg is actually expected to be located (for FS 2020): According to the Prepar3D
documentation the configuration “should be placed in the Documents folder, or in the same folder as the client application or library, on the computer the client is running on.”
(yes, I know, I keep referring to SimConnect API documentation of other products - but the MS specific SimConnect API documentation is disconninued and well hidden from web crawlers).
The question is relevant because if the application is supposed to be able to change that configuration (and create it automatically in the first place) then it would not be an ideal fit if that configuration could only be stored in the application’s directory - which would normally be write-protected (for non-admin users).
So does the SimConnect client library (DLL) for FS 2020 also look in some “documents” folder for the SimConnect.cfg? Or only in the same directory where the SimConnect.dll is located itself (which would typically be in a read-only location)?
Anyone has already made some practical steps which such a “network setup”?