This is a bug in FSX/FSX-SE/P3D that affects a small percentage of users. Apparently, the exact nature of the problem is not well understood, even by Microsoft. As a result, finding a solution is a bit of a hit-and-miss affair. Having said that, most users who have come to me with this problem have eventually got it working. The recommended solution that seems to have the most success is as follows:
- Go to the folder where you installed FS Force. This will usually be C:\Program Files (x86)\FSForce 2.
- Locate the file fsforce.dll (or fsforce_x64.dll if you're running P3Dv4), and make a copy of it, but with a different name. It doesn't matter what name you choose. For the purposes of this example, we'll call it fsforce_diff.dll
- Navigate to the folder that contains the DLL.XML file. If you are running FSX, this will normally be %APPDATA%\Microsoft\FSX. If you are running P3D, the folder will be %APPDATA%\Lockheed Martin\Prepar3D vx. (Note: this is the same folder in which you will find the FSX.CFG file).
- Open this file (ie. DLL.XML) using a simple text editor and locate the section that looks like this:
Code: Select all
<Launch.Addon> <Name>FSForce DLL</Name> <Disabled>false</Disabled> <ManualLoad>false</ManualLoad> <Path>C:\Program Files (x86)\FSForce 2\fsforce.dll</Path> </Launch.Addon>
- Rename the occurrence of "fsforce.dll" (or fsforce_x64.dll) the same as you did in step 2 above. So for our example, the <Path> ... </Path> line would now look like this:
Code: Select all
<Path>C:\Program Files (x86)\FSForce 2\fsforce_diff.dll</Path>
- Save the file and exit the editor, then try starting FSX