by Steve Waite » Wed Sep 27, 2017 2:09 pm
SimConnect matters
At the moment all versions of Ideal Flight utilise the x86 SimConnect interface to the P3D server.
The number of connections to the server is what counts toward taking resources. The number of different SimConnect modules installed has no effect if we have 10 or 100. There are 4 versions that P3D uses and are found in the \redist folder, ESP, RTM, FSX-SP1 and FSX-XPACK. Each is installed from a .msi file that sets up the instructions for the WinSxS system
These SimConnect modules reside in the WinSxS folder, a system that is Deprectated in Windows 10, the side-by-side system, so that any application can attach to them without knowing where the module is located and so that only one copy of each is required.
That means at some stage in the future there will be no SimConnect modules to find, the application will carry the SimConnect interface with it.
All versions of Ideal Flight work either way, and can install their own module.
At present they all continue to require the WinSxS version be present. Why? Since 99% of SimConnect apps require it too, and Ideal Flight is very often the first addon installed on a new system, it made sense to leave be so that the user becomes aware all the simconnect versions should be installed until further notice or many addons might fail until they also provide their own interface module.
P3D stopped installing ESP SimConnect .msi as a default installation routine but make the \redist folder available until the WinSxS system dies. That could be a long time.
software architect at codelegend.com
equipment: i9-9980Xe 64GB 2xRTX2080ti NVLink 2TB M.2 NVMe,
i9-9900X 64GB RTX2080ti 2TB M.2 NVMe, i7-3960X 32GB GTX680 4TB RAID10,
NAS @7TB RAID10 (16TB)