Closing FSForce

Discussions and general chat

Moderator: RussDirks

Post Reply
gderreck
Posts: 24
Joined: Thu Dec 01, 2011 5:35 am

Closing FSForce

Post by gderreck » Thu Dec 22, 2011 12:35 pm

Greetings
First of all, Season's Greetings.

I am writing a small program to close FSX and associated programs. I realize that FSForce opens and closes with FSX; but often enough, FSX crashes, freezes and/or the main window gets corrupted and I have to close the program from the task bar.

In these instances, the FSForce icon remains in the notification area. I assume FSForce does not close when FSX is interrupted. This is not the fault of FSForce. Your program sits quietly in the background and creates excellent force feedback. Thank you.

If I use the Kill() method in C#, how will that affect FSForce. Does the program have anything to clean up before closing? I suspect that if FSX does not close properly, it may be immaterial. The idea is that after closing FSX, I'll check to see if other programs, that should exit, have exited. If not, I'll close them. I don't think I can use CloseMainWindow() since the application is residing in the notification area. Your help is appreciated.

Second, I have set up a couple of profiles that do not use elevator trim. In these cases, I set the trim to FSX. I do not have a trim axis set up in FSX. Occasionally, when I open aircraft that are associated with these profiles, I get the elevator trim effect. I have to either open the profile menu item and select the profile (the correct profile always shows); or I have to disable/re-enable FSForce. Is there something I am doing wrong?

Finally, with respect to Prepar3D, I understand that that would require a new license. Full price, or a discount for existing users? Not a quibble. The price is reasonable. Just curious.

FsForce version 2.6.0.3
FSX with Acceleration
Win 7 64 bit SP1
FSUIPC version 4.749f

Thanks again, and the best to you and yours.

Graham

RussDirks
Site Admin
Posts: 696
Joined: Sat Sep 13, 2003 1:18 pm
Location: Chilliwack, Canada

Post by RussDirks » Fri Dec 23, 2011 2:37 am

1. I think CloseMainWindow should work fine. Even though it sits in the tray, FS Force is just a regular program (not a service). However, if that doesn't work, Kill would be your next choice, and no, FS Force doesn't need to clean up anything.

2. I tried to set up my system like yours, but was unable to reproduce the problem. I'm not sure what is going on there with you. Are you using the default trim buttons (3 & 4), or have you changed those?

3. Existing users can upgrade for $19.95.
Russel Dirks
Forum Moderator

gderreck
Posts: 24
Joined: Thu Dec 01, 2011 5:35 am

Closing FSForce

Post by gderreck » Fri Dec 23, 2011 4:55 am

Thanks for the reply. The contents of the cfg file (minus the data for the default profiles...to save space) are below. It still takes up a lot of space, but maybe will be of some help:

[General]
TrimClickAmount=125
TrimIndicator=1
PauseOnTaskSwitch=0
FSXFolder=C:\Microsoft Flight Simulator X\
dwStartDelay=1
TrimWheel=Joystick:1:ZAxis
JoystickTrimUp=Joystick:0:Button:60
JoystickTrimDown=Joystick:0:Button:61

[Profile Assignments]
Airbus A321=Fly By Wire
AirCreation Trike Ultralight=Ultralight
Boeing 737-800=Jet Heavy
Boeing 747-400=Jet Heavy
Beechcraft Baron 58=Medium GA
Beechcraft King Air 350=Twin Turboprop
Bombardier CRJ700=Regional Jet
Cessna C172SP Skyhawk=Light GA
Cessna C208B Grand Caravan=Medium GA
de Havilland Beaver DHC2=Light GA
DG Flugzeugbau DG-808S=Generic
de Havilland Dash 8-100=Twin Turboprop
Douglas DC-3=Medium GA
Extra 300S=Light GA
Boeing F/A-18=Military Fighter
Grumman Goose G21A=Medium GA
Bombardier Learjet 45=Business Jet
Maule Orion=Light GA
Maule Orion on skis=Light GA
McDonnell-Douglas/Boeing MD-83=Jet Medium
Mooney Bravo=Light GA
North American P-51D=Medium GA
Piper Cherokee 180=Light GA
Piper J-3 Cub=Light GA
Bell 206B JetRanger=Helicopter
AgustaWestland EH101=Helicopter
Robinson R22 Beta II=Helicopter
BOEING 747-400 GE=Jet Heavy
Airbus X A320-232 IAE=Fly By Wire
Airbus X A320-214 CFM=Fly By Wire
Airbus X A321-211 CFM=Fly By Wire
Airbus X A321-321 IAE=Fly By Wire
FeelThere/Wilco Airbus Series Vol 2 A330-200 GE=Fly By Wire
FeelThere/Wilco Airbus Series Vol 2 A330 MRTT=Fly By Wire
FeelThere/Wilco Airbus Series Vol 2 A330-200 RR=Fly By Wire
FeelThere/Wilco Airbus Series Vol 2 A330-300 GE=Fly By Wire
FeelThere/Wilco Airbus Series Vol 2 A330-300 RR=Fly By Wire
FeelThere/Wilco Airbus Series Vol 2 A340-300 CFM=Fly By Wire
FeelThere/Wilco Airbus Series Vol 2 A340-600 RR=Fly By Wire
BOEING 747-400F GE=Jet Heavy
Avro Canada CF-105 Arrow Mk. 1=Military Fighter
Avro Canada CF-105 Arrow Mk. 2=Military Fighter


[Profile Assignments - P3D]

[Generic]
ID=Profile

[Jet Heavy]
ID=Profile

[Jet Medium]
ID=Profile

[Regional Jet]
ID=Profile

[Business Jet]
ID=Profile

[Twin Turboprop]
ID=Profile

[Medium GA]
ID=Profile

[Light GA]
ID=Profile

[Military Fighter]
ID=Profile

[Helicopter]
ID=Profile

[Ultralight]
ID=Profile
AileronForcePoints=0,0,19,25,43,47,63,61,93,67,127,67,160,67
ElevatorForcePoints=0,0,19,25,43,47,63,61,93,67,127,67,160,67
ElevatorWeight=5
GroundOps=Run-up vibs
AileronFriction=55
AileronDamping=60
ElevatorFriction=55
ElevatorDamping=60
MechanicalCutoff=80
LandingTransition=-240
LandingHardBase=60
LandingMaxForce=-400
LandingMinForce=30
LandingWingsLevel=5
BrakeStrength=90
BrakeVibrationPeriod=80
BrakeVibrationStrength=17
BrakeVibrationDirection=75
BrakeVibrationStartRamp=50
BrakeVibrationEndRamp=30
GearThumpMagnitude=0
GearThumpPeriod=350
GearBuffetDuration=-1
GearBuffetMinForce=1
GearBuffetForce=5
GearBuffetBasePeriod=140
GearBuffetModulatingPeriod=600
GroundOpsGain=1.7
CorneringMultiplier=0
TrimSystem=FSX
StallBuffetMult=0.8
StallAlphaDelta=5.0
"StickShakerMult=0

[Fly By Wire]
ID=Profile
AileronForcePoints=0,0,0,50,174,50,302,50,437,50,593,50,743,50,859,50
ElevatorForcePoints=0,0,0,50,174,50,302,50,437,50,593,50,743,50,859,50
ElevatorWeight=0
GroundOps=Run-up vibs
AileronFriction=0
AileronDamping=0
ElevatorFriction=0
ElevatorDamping=0
MechanicalCutoff=70
LandingTransition=-420
LandingHardBase=60
LandingMaxForce=-700
LandingMinForce=15
LandingWingsLevel=5
BrakeStrength=0
BrakeVibrationPeriod=80
BrakeVibrationStrength=15
BrakeVibrationDirection=75
BrakeVibrationStartRamp=90
BrakeVibrationEndRamp=70
GearThumpMagnitude=15
GearThumpPeriod=350
GearBuffetDuration=3
GearBuffetMinForce=4
GearBuffetForce=15
GearBuffetBasePeriod=140
GearBuffetModulatingPeriod=600
GroundOpsGain=0.9
UseN1=1
CorneringMultiplier=0
TrimSystem=FSX
StallBuffetMult=0.4
StallAlphaDelta=5.0
"StickShakerMult=0

I should also point out that I'm using a Logitech G940 setup.

As per the getting started instructions, I changed the button assignments to a number that I doubt I'll use. Perhaps I should have used higher numbers? One thing to note. In the default profiles, the Trim property is the last entry. In my custom profiles, as you can see; I added stall and stick shaker entries after the trim entry.

Thanks again.

RussDirks
Site Admin
Posts: 696
Joined: Sat Sep 13, 2003 1:18 pm
Location: Chilliwack, Canada

Post by RussDirks » Sat Dec 24, 2011 3:44 am

Perhaps I should have used higher numbers?
I would try smaller numbers. Take the number of buttons on the joystick, add one, and use that as the first number.
Russel Dirks
Forum Moderator

gderreck
Posts: 24
Joined: Thu Dec 01, 2011 5:35 am

Closing FSForce

Post by gderreck » Wed Jan 04, 2012 8:29 am

Thanks for the heads up. I changed the button assignments to the highest number + 1 as per your instructions. FSForce is still opening the trim wheel gauge in profiles where I have chosen FSX for trim. FSForce trim is also functional in those profiles where I've selected FSX (it's not just the gauge showing). The way I'm currently dealing with it is: go to the menu, select the profile option, the current profile shows for the current aircraft. I click OK to confirm and the trim goes away.

RussDirks
Site Admin
Posts: 696
Joined: Sat Sep 13, 2003 1:18 pm
Location: Chilliwack, Canada

Post by RussDirks » Wed Jan 04, 2012 1:20 pm

Well I did some more testing, this time with the G940, but I am still not able to reproduce the problems you're having ... everything works as it should. Do you normally see the problem at the beginning of a flight, or do you often switch airplanes in the middle of a flight, and see the problem then? I tried both scenarios and never had any problems.

Unless there is some information about your setup or specific procedures that you haven't shared with me, the only thing I can suggest is to continue doing what your doing, ie. confirming the profile when the problem appears.
Russel Dirks
Forum Moderator

gderreck
Posts: 24
Joined: Thu Dec 01, 2011 5:35 am

Post by gderreck » Wed Jan 04, 2012 5:16 pm

Thanks for the reply. No, there is nothing that I can think of. I typically do not change planes mid-flight and yes; the issue crops up when I start the flight. I did do a reinstall and pasted the two custom profiles I have created into the configuration file. I am using the I'm not eager to reinstall everything, so I'll just confirm profiles. If other issues arise, I'll let you know.

Current Setup for Trim Wheel:
TrimWheel=Joystick:1:ZAxis
JoystickTrimUp=Joystick:0:Button:10
JoystickTrimDown=Joystick:0:Button:11

Other Addons:
FSUIPC
EZDok
TrackIR 5 (not really an addon, but now controlled by EZDok in FSX)
FScene TotalPack
Avro Arrow
Airbus X
Wilco Airbus Vol 2 Evolution
PMDG 747
PMDG 737 NGX
REX: not installed at the moment. Waiting for update to reinstall.

Just included these in case on of them might be the issue. Please let me know if there is anything else I can send that might help.

Thanks
Graham

zetasj55

Post by zetasj55 » Wed Oct 23, 2013 12:19 pm

I tried to set up my system like yours, but was unable to reproduce the problem. I'm not sure what is going on there with you. Are you using the default trim buttons (3 & 4), or have you changed those?

Post Reply