Wow, I'm really impressed -- reported the bug last night and this morning it was fixed AND released!
Documentation: View it online
Forums: Enter here.
If you are experiencing problems using FS Force, you may be asked by technical support to provide a copy of your SimConnect log file to help diagnose the problem. This log file is not produced by default. Follow these steps to configure your system to produce a SimConnect log file.
Create a text file using a simple text editor like Notepad, and name it SimConnect.ini. Place it in the special flight simulator sub-folder beneath your Documents folder. Depending on which flight sim version you are using, this sub-folder will either be called Flight Simulator X Files, Flight Simulator X - Steam Edition Files, or Prepar3D v3 Files. (If you already have a file by that name in the sub-folder, open it in your editor instead of creating a new one).
Edit the file so it contains the text shown below. The file= line can be customized to point to any folder that is convenient for you.
Save the file, and then start FSX. Use a watch or a stop-watch, and count the number of seconds that elapse from the time you start FSX.
Start a flight and do whatever you need to do to reproduce the errors you are experiencing. As soon as the error has occurred, take note of the number of elapsed seconds, and then shut down FSX
Send the resulting SimConnect.log file to the support email address above, along with your report of when the error occurred.
Once the issue has been resolved and
you no longer need logging enabled, you can either delete the SimConnect.ini
file, or place a semi-colon (;) at the beginning of the file= line to
Just a quick note of thanks for this amazing little piece of software. The thing works, and how!! I have a MS FF2 that was a spastic, limp, lump of plastic until now. The customer support is incredible - my wife deleted my activation code, and it was re-sent within minutes of my requesting a duplicate. Amazing. Software that works, first time ... good customer support...
FS Force can also be configured to produce it's own log file. Follow these steps :
Locate the file FSForce.cfg. Under WinXP, this file can be found under "C:\Documents & Settings\All Users\Application Data\FS Force". Under Vista, it can be found under "C:\ProgramData\FS Force".
Open this file using any text editor. Under the [General] section add "Errorlevel=1". (Setting it to 0 turns logging off.). The log file is saved in the same folder as FSForce.cfg.
This is a small utility program you can download to test the force feedback capabilities of your joystick. If FS Force doesn't seem to be working properly, you can use this utility to test your joystick, which can be helpful in determining if the problem is with FS Force, your system, or your joystick.
Download : ForceTest.exe (108 KB)
Translate this page