[SOLVED]FSX:SE latest update killed my FS Force

jschall2 · Post by **jschall2** » Wed Aug 05, 2015 8:17 pm

I have been using FS Force forever, and most recently it was working fine on FSX:SE with Windows 10 RTM (update 10240).

But last weekend Dovetail Games released an update, apparently to improve the way FSX:SE deals with Windows 10 and DirectX 12.

Now, when I run FSX:SE I get the following pop-ups over the splash screen:

"Flight Simulator is attempting to start "FS Force" (Version 2.8.0.5, Config Entry Number 1). Do you want to run this program?

C:\Program Files(x86)\FS Force 2\FSForce.exe

Yes\No"

If I say "Yes", this error pops up:

"Flight Simulator has detected a problem with a third-party software program (add-on):

Name: Unknown
Version: 2.6.2.4
Company: Dirks Software
File: C\Program Files(x86)\FSForce 2\FSForce.dll

Do you want to run this software (not recommended)?

Yes\No"

If I say "No", FSX:SE starts normally, but with no FS Force.

If I say "Yes", the popup disappears, but FSX:SE just hangs at the splash screen.

I hate running FSX without FS Force!

Any suggestions for getting FS Force to run with the latest update of FSX:SE and Windows 10?

Below is an extract from logfile.txt:

---------------------------------------------------------------------------
Profile Manager [2015-08-04 12:07:37]
---------------------------------------------------------------------------
Launching activation helper
-----------------------------------------------------------
Activation Helper - DirectActivation [2015-08-04 12:09:01]
Application Version : 2.8.0.5
Download Version : 3
-----------------------------------------------------------
UTC : 2015-08-04 16:09:01
Version check:
<html>

<<FSF_RET>>act_ver>>3>>
OHL4YNC7jKLuiEhPaRBRU0AinUQzt1TY
x+cbfAxF5NC5mWVlr9feXay4s3cvFrRb
B9f9AVq7Uzb6WsOnO92zfw==
RQfXJkVtfQeKrXrwhIlNsXiBDhatD2gaRXS6DfyEk2oZUXVdkYxd5TjFZrTjPwLe
spt0WWdFGSy3kEj5pmzpDNy9VhNqP8PIVzzoocWekYzfW4XrWQY1z8+O4CnxTDoXcTjzB1jVPzYGeEeGPcJGHfqV5l1yTpXb
b7M/0sisID945pkvMLg9KN0NQfSWmraQxSZE3uxynVk=
4FTFyyISnhqhoBcgdO4l3CJrh8Oc28iR
Activation Attempt:
<html>

<<FSF_RET>>OK>>FSX>>2>>
2015-08-04 12:09:04 PM : 6peG9Zs4Bs1sSWbrz8sHZg==
2015-08-04 12:09:04 : PM received FSF_ACT_COMPLETE
---------------------------------------------------------------------------
FSForce.exe SimConnect Client : Acceleration [2015-08-04 12:10:32]
---------------------------------------------------------------------------
UTC : 2015-08-04 16:10:32
---------------------------------------------------------------------------
FSForce.exe SimConnect Client : Acceleration [2015-08-04 12:18:42]
---------------------------------------------------------------------------
UTC : 2015-08-04 16:18:42
Application name : Microsoft Flight Simulator X

Application version : 10.0.62613.0

SimConnect Version : 10.0.62613.0

Interface Version : 4
FS Force closing.
---------------------------------------------------------------------------
Profile Manager [2015-08-04 12:23:39]
---------------------------------------------------------------------------
---------------------------------------------------------------------------
FSForce.exe SimConnect Client : Acceleration [2015-08-04 12:26:27]
---------------------------------------------------------------------------
UTC : 2015-08-04 16:26:27
---------------------------------------------------------------------------
FSForce.exe SimConnect Client : Acceleration [2015-08-05 08:54:17]
---------------------------------------------------------------------------
UTC : 2015-08-05 12:54:17
Application name : Microsoft Flight Simulator X

Application version : 10.0.62613.0

SimConnect Version : 10.0.62613.0

Interface Version : 4
FS Force closing.
---------------------------------------------------------------------------
FSForce.exe SimConnect Client : Acceleration [2015-08-05 09:03:16]
---------------------------------------------------------------------------
UTC : 2015-08-05 13:03:16

Post by **RussDirks** » Thu Aug 06, 2015 2:07 am

This is a bug in FSX / FSX-SE 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.

A Google search on the first sentence of the error message will show that it affects a number of different FS Add-ons.

Following is a knowledge base article I've put together on the problem. (Note: try the LAST suggestion FIRST. I think it has the best chance of success):

Quote from Pete Dowson: "This is the well known SimConnect "trust" bug, a timing clash between SimConnect's accesses into the Windows module trust verification system and other activities in SimConnect"
See this forum thread for more info : http://forum.simflight.com/topic/68382- ... -installed
MS tried fixing the bug ... they never got it, but they made changes in the various updates to improve the error rate, so make sure FSX is fully updated to SP2/Acceleration
It's just a matter of keep trying to load FSX / FS Force. Once you can get past the error message, even just once, you won't have the problem again.
Try changing things: addon load order, disabling other add-ons
Go into Profile Manager and change the DLL from "Auto-Launch" to "Prompt". Change the EXE to "Don't Launch". Then try starting FSX.
Try disabling anti-virus : turn off real time protection, then try starting FSX.
One user solved the problem by a complete re-install of FSX.
One user solved the problem by renaming the DLL : First, rename fsforce.dll to something else (ie. fsforce_xxx.dll, doesn't matter ... anything, as long as it is different). Second, open up the file DLL.XML (it's in the same folder as FSX.CFG) and edit the entry for fsforce.dll so that it points to the newly renamed file from step 1. See here for a more detailed set of instructions.

jschall2 · Post by **jschall2** » Thu Aug 06, 2015 4:03 am

RussDirks wrote: [*]One user solved the problem by renaming the DLL : First, rename fsforce.dll to something else (ie. fsforce_xxx.dll, doesn't matter ... anything, as long as it is different). Second, open up the file DLL.XML (it's in the same folder as FSX.CFG) and edit the entry for fsforce.dll so that it points to the newly renamed file from step 1.[/list]

That worked!

Thank you for the quick reply, Russell.

jschall2 · Post by **jschall2** » Fri Aug 07, 2015 6:03 am

And then I had to do the same thing for my Prepar3D installation...

FS FORCE

[SOLVED]FSX:SE latest update killed my FS Force

[SOLVED]FSX:SE latest update killed my FS Force

Re: FSX:SE latest update killed my FS Force

Re: FSX:SE latest update killed my FS Force

Re: [SOLVED]FSX:SE latest update killed my FS Force