FS FORCE

Merry Xmas and Happy New Year,

I am sorry to keep nagging you about the trim gauge. I seems to be very inconsistent. I looked in several aircraft, and there was an entry for FS Force. Here is the entry for the A2A C172:

[Window Titles]
Window17=FSForce Trim Gauge

[Window17]
Position=8
Size_mm=61,23
Window_size=0.08
Visible=1
Zorder=100
Ident=15203
Background_color=0,0,0
gauge00=FSForce!TrimGauge,0,0


And the Dodosim 206:

[WindowTitles]

Window09=FSForce Trim Gauge

[Window09]
Position=8
Size_mm=61,23
Window_size=0.08
Visible=1
Zorder=100
Ident=15203
Background_color=0,0,0
gauge00=FSForce!TrimGauge,0,0

If these entries are correct, then I don't know what to do. If not, perhaps you could post a copy of exactly what entries I should see in the panel.cfg file. I am using the latest version of your software in P3D 2.4.

Thanks,
Graham

Your panel.cfg settings are fine. The problem is that Nvidia DSR, Windows and P3D are not playing well together. I base my conclusion on the fact that the trim gauge (and I would assume, other parts of the P3D display) are showing up behind the taskbar.

You can either just accept it the way it is, or disable the DSR feature.

Thanks for the reply,

I uninstalled and reinstalled FS-Force. No trim gauge showing for Default C172 (imported from FSX), A2A C172 or Dodosim. I should point out that on the first reinstall, I could not test the forces. I had to run the install routine again; and was able to test the forces. Here is a copy of the FS-Force log file:

---------------------------------------------------------------------------
Profile Manager [2014-12-30 22:16:05]
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Profile Manager [2014-12-30 22:18:37]
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Profile Manager [2014-12-30 22:25:09]
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Profile Manager [2014-12-30 22:28:20]
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Profile Manager [2014-12-30 22:39:59]
---------------------------------------------------------------------------
---------------------------------------------------------------------------
FSForce.exe SimConnect Client : Acceleration [2014-12-30 22:44:23]
---------------------------------------------------------------------------
UTC : 2014-12-31 05:44:23
---------------------------------------------------------------------------
FSForce.dll SimConnect Client : Acceleration [2014-12-30 22:44:29]
---------------------------------------------------------------------------
UTC : 2014-12-31 05:44:29
Application name : Lockheed Martin® Prepar3D® v2

Application version : 2.4.11570.0

SimConnect Version : 2.4.0.0

Interface Version : 13
SimConnect Exception (EXE) :
Exception : ERROR
Offending Parameter : 4294967295
Send Packet ID : 36
SimConnect Exception (EXE) :
Exception : ERROR
Offending Parameter : 4294967295
Send Packet ID : 37
SimConnect Exception (EXE) :
Exception : UNRECOGNIZED_ID
Offending Parameter : 1
Send Packet ID : 52
SimConnect Exception (EXE) :
Exception : UNRECOGNIZED_ID
Offending Parameter : 1
Send Packet ID : 53
FS Force closing.
---------------------------------------------------------------------------
FSForce.exe SimConnect Client : Acceleration [2014-12-30 22:52:52]
---------------------------------------------------------------------------
UTC : 2014-12-31 05:52:52
Application name : Lockheed Martin® Prepar3D® v2

Application version : 2.4.11570.0

SimConnect Version : 2.4.0.0

Interface Version : 13
SimConnect Exception (EXE) :
Exception : ERROR
Offending Parameter : 4294967295
Send Packet ID : 36
SimConnect Exception (EXE) :
Exception : ERROR
Offending Parameter : 4294967295
Send Packet ID : 37
SimConnect Exception (EXE) :
Exception : UNRECOGNIZED_ID
Offending Parameter : 1
Send Packet ID : 52
SimConnect Exception (EXE) :
Exception : UNRECOGNIZED_ID
Offending Parameter : 1
Send Packet ID : 53
Error in routine CorneringEffect.Init :
E_NOTIMPL : The function called is not supported at this time
FS Force closing.
---------------------------------------------------------------------------
FSForce.exe SimConnect Client : Acceleration [2014-12-30 23:06:27]
---------------------------------------------------------------------------
UTC : 2014-12-31 06:06:27
---------------------------------------------------------------------------
FSForce.dll SimConnect Client : Acceleration [2014-12-30 23:06:35]
---------------------------------------------------------------------------
UTC : 2014-12-31 06:06:35
Application name : Lockheed Martin® Prepar3D® v2

Application version : 2.4.11570.0

SimConnect Version : 2.4.0.0

Interface Version : 13
SimConnect Exception (EXE) :
Exception : ERROR
Offending Parameter : 4294967295
Send Packet ID : 36
SimConnect Exception (EXE) :
Exception : ERROR
Offending Parameter : 4294967295
Send Packet ID : 37
SimConnect Exception (EXE) :
Exception : UNRECOGNIZED_ID
Offending Parameter : 1
Send Packet ID : 52
SimConnect Exception (EXE) :
Exception : UNRECOGNIZED_ID
Offending Parameter : 1
Send Packet ID : 53
Error in routine AirEffect.Load[1] :
E_NOTIMPL : The function called is not supported at this time
FS Force closing.

P3D was running at 1920x1080x32 which is native resolution for my monitor. Trim gauge was not hiding behind anything. I only use the gauge to determine when trim is neutral in aircraft where there is no visible way of determining the state visually (helicopters).

EDIT: The trim gauge showed up again. I think I am beating this to death. Please just consider the topic closed. I am wasting your time and whatever credibility I still possess.

Happy New Year

Happy New Year to Russ and Everyone,

As you are no doubt painfully aware, I have been thrashing around, quite unsuccessfully, with the software inconsistency issue. I have been hovering around a solution and of course, much of it has to do with my own "duh" moment.

I noticed that if I removed all joystick assignments from the config file, that when I pressed buttons 3 and 4 on the joystick (MS Sidewinder), a little blue gauge popped up that said FSX and beside that were the trim levels -100 to 100. I also noticed that these buttons were not assigned to trim elevators either in P3D 2.4 or FSUIPC or LINDA. Eureka! I also noticed that nothing else was bringing up the trim gauge. Not the trim wheel, or any other combination of buttons. So I...

-installed proper Saitek drivers for the trim wheel and all other connected hardware items.
-assigned the trim gauge X axis to FSForce.
-restarted P3D and opened a Cessna to view the movement of the trim gauge.
-Well...trim gauge spins, blue gauge shows up registering values. Very good!
-then deleted all assignments for elevator trim from the trim wheel; except the trim wheel in FSForce config.
-returned to the aircraft and spun the trim wheel. Trim wheel moves and little blue box in the bottom right hand corner. Oh my!
-did a flight and the trim was never so smooth! Had to reinitialize FSForce after taking off...small potatoes.

What an idiot How long have I been using your software...4 years or so? I never thought for a moment that FS Force took total control of trim, up to and including the physical action of trimming the elevator. I thought is was an augmentation. It's a full implementation! I've been beating your software up with competing assignments.

I would like to point out that that FSForce was OK with native resolution and DSR set at 4k levels. I restarted P3D 3 times and everything worked as expected. I would only add that when there was no joystick assignment in the config and buttons 3 and 4 on the joystick were trimming the aircraft; the gauge had 'FSX' as well as trim values. When the trim wheel was assigned to the aircraft, there were trim values in the gauge, but no 'FSX'.

I wanted to send an email, 'cause I felt like such a schlamozel I decided to post to give you the performance info with DSR and just in case anyone else was not aware of the issues I faced. Doubtful.

Thanks loads for the great software,
Graham