Jump to content
The simFlight Network Forums

FSX Freezes when assigning Throttle as Direct FSUIPC Calibration


Recommended Posts

Hi All,

I have a problem which has been reported in the past but not sure whether rectiified for my situation.

I have two joysticks attached to my simulator running FSX with Acceleration Pack using a registered version of FSUIPC (Version 4.81). Each joystick has a throttle control. I wanted to define a portion of the range to act as thrust reverse but I want the two throttle axes (one on each joystick) to control both engines simultaneously so I can have a two person set-up rather than having throttle axis 1 controlling the left engine and throttle axis 2 (on joystick 2) controlling the right engine of my B737. I am using the default B737-800 model in FSX.

Originally I simply assigned Axis Z with the controls screen of FSX to "Throttle" without defining in FSUIPC for each joystick's throttle axis. This worked well. The throttle on Joystick 1 would operate both engines when pushed forward and likewise for Joystick 2. No problems. BUT this did NOT allow for a portion of the range to act as Thrust Reverse. So ... I deleted the Axis Z definition for both josticks and decided to use FSUIPC.

In the Axis Assignment tab of FSUIPC I used "Send Direct to FSUIPC Calibration" and then selected "Throttle 1" from the dropdown box. I repeated this for both joysticks. Then in the "Joystick Calibration" tab I went to the 3rd page "Seperate Throttles per Engine" and proceeded to set each of the three zones as -16380, -7000 and 16383 to give a Reverser zone when the throttle range is between -16380 (fully back) and -7000 (approx. one quarter forward). In the throttle 2 section I then ticked the Map 1 ->234 as req (otherwise I found that only one engine was controlled !!!)

What I found then was that when the axis was operated on the joysticks FSX would freeze or hang. I needed to end a non responsive FSX using the task manager. Originally I thought this hanging behaviour was being caused by a hardware fault (video card, faulty memory, faulty joystick etc). To keep things simple and diagnose I unplugged one of the joysticks and tried to repeat a flight. As soon as I operated the throttle within a few seconds of doing so FSX would freeze (hang) once again,

I then unpluggled the joystick and found that the hanging stopped ! Thus I thought my joystick was faulty. Anyhow researching on the internet I found a post on this forum about FSUIPC freezing or hanging FSX when using axis mapped as "Send Direct as FUSIPC Calibration" ... it did mention SimConnect being overwhelmed ? and having to set Poll Interval... apparently later versions of FSUIPC bypassed SimConnect when using Direct to FSUIPC Calibration unless using Map 1 -> to 234 throttles which is what I'm needing to do. So I'm experiencing this hanging issue.

If I use send to FS as Normal axis within FSUIPC then I do not have any issues BUT then I cannot set a "reverser" zone in the Joystick Calibration page for both engines....

Am I doing something wrong ? Is there another method ? Can I somehow overcome the freezing (hanging) problem ?

Thank you all in advance

Cheers,

Luke

Link to comment
Share on other sites

I have a problem which has been reported in the past but not sure whether rectiified for my situation.

I've not see any similar problem reported here before.

using a registered version of FSUIPC (Version 4.81).

First thing to do, always before reporting any sort of problem, is to check that you are up to date -- which you are not. The current main release is 4.827 and there are later updates in the Download Links subforum.

In the Axis Assignment tab of FSUIPC I used "Send Direct to FSUIPC Calibration" and then selected "Throttle 1" from the dropdown box.

Any particular reason for selecting the "direct" option instead of the normal FS controls.

You should also know that you can still leave your throttles assigned in FSX, as generic throttles, and map them to the 4 separate throttles in FSUIPC. Jumping straight from using FS assignments to FSUIPC assignments is never necessary -- the FSUIPC mapping and calibration faciities long preceded to addition of the assignment capabilities, which were added for the more complex cockpit situations or when needing different axis assignments according to aircraft type.

In the case of two separate sets of controls, FSUIPC's "direct" assignment does give one advantage -- FSUIPC can then arbitrate between them, using only the one wth the larrgest deflection. However, with throttles it may sometimes be better just to have an idle zone large enough for the currently unused input to be parked there without any risk of "jitter" interfering with the other one.

I repeated this for both joysticks. Then in the "Joystick Calibration" tab I went to the 3rd page "Seperate Throttles per Engine" and proceeded to set each of the three zones as -16380, -7000 and 16383 to give a Reverser zone when the throttle range is between -16380 (fully back) and -7000 (approx. one quarter forward).

You should always make an idle zone, not just one point, to ensure idle can always be set despite the invariable small aberrations which will occur. You should also calibrate with the max and min settings a little away from the extremes for the same reason. If you follow the numbered steps for calibration in the User Guide you will get better results. That's the whole point of calibration after all.

In the throttle 2 section I then ticked the Map 1 ->234 as req (otherwise I found that only one engine was controlled !!!)

Of course. "Throttle1" means "throttle for engine 1".

What I found then was that when the axis was operated on the joysticks FSX would freeze or hang. I needed to end a non responsive FSX using the task manager. Originally I thought this hanging behaviour was being caused by a hardware fault (video card, faulty memory, faulty joystick etc). To keep things simple and diagnose I unplugged one of the joysticks and tried to repeat a flight. As soon as I operated the throttle within a few seconds of doing so FSX would freeze (hang) once again,

I then unpluggled the joystick and found that the hanging stopped ! Thus I thought my joystick was faulty. Anyhow researching on the internet I found a post on this forum about FSUIPC freezing or hanging FSX when using axis mapped as "Send Direct as FUSIPC Calibration" ... it did mention SimConnect being overwhelmed ? and having to set Poll Interval... apparently later versions of FSUIPC bypassed SimConnect when using Direct to FSUIPC Calibration unless using Map 1 -> to 234 throttles which is what I'm needing to do. So I'm experiencing this hanging issue.

Where do you get this idea from? FSUIPC has never "bypassed simconnect" and cannot do so. All controls are operated through Simconnect. Can you point me to this misleading post, please?

I know of no possible reason for FSX to hang simply from use of any axis assignment or calibration. Something else is going on. I need more information -- please show me the FSUIPC4.INI file (from the FSX Modules folder). You could also try enabling FSUIPC's axis logging (in the Logging tab) so you can see what is going on. If you temporarily switch FSX into Windowed mode and enable the Console Log you will be able to see the results of moving the axis in real time.

However, before doing ANY of this, please update your FSUIPC4. I don't want to see any results with an old version -- use 4.827 or later (run the FSUIPC4 installer and then copy in 4.836 for the latest version).

If I use send to FS as Normal axis within FSUIPC then I do not have any issues BUT then I cannot set a "reverser" zone in the Joystick Calibration page for both engines....

What makes you think that? It doesn't matter how or where you assign axes -- all of the mapping and calibration facilities are available no matter where or how you assign. Assignment is always a separate business.

Regards

Pete

Link to comment
Share on other sites

BTW, further to my last reply, I've just done here EXACTLY what you say you've done there, with FSUIPC 4.836, and it all worked correctly.

Note that the "arbitration" for throttles takes the last one to give the highest value (most forward thrust) and then stays with that until the other is moved to exceed it. This is different from arbitration for aileron, elevator and rudder.

Pete

Link to comment
Share on other sites

Hi Peter,

Apologies for this long post but I wanted to address your questions.

Thank you for your quick reply. I'll take each point you have made separately for clarity. Just addressing your point firstly of where I found a related topic in your forum it was this one:FSX crashes with FSUIPC4 posted Jun 13 2008 04:38 AM.

Within that topic you talk about direct calibration being more efficient and bypassing SimConnect. I have copied three quotes from that message to illustrate my point (directly below). However I do realise you were dealing with a different (although similar problem) in that topic that may not be as relevant to my issue but it does sound like what I'm experiencing.

----------------------------------------------------------

Topic: FSX crashes with FSUIPC4

Started by snomhf, Jun 13 2008 04:38 AM

Posted 16 June 2008 - 08:19 AM

Pete Dowson said:

Okay. That's interesting, but I still don't understand it.

I've always had all my axes (not from CH equipment though) sent

"direct". It is more efficient, if you are calibrating in FSUIPC,

because the other method involves three times as many messages flying

about between FSUIPC and SimConnect -- one lot to send the axis values

to FS, then the same stuff being sent from FS to FSUIPC for calibration,

then back from FSUIPC to FS after calibration.

With "send direct", your axis values are calibrated then sent to FS,

by-passing the circuitous route. One set of transfers, so it should be

simpler, less error prone, and three times more efficient! In theory.

So, now I have to find out what there is about that which could possibly

make a system crash.

Posted 19 June 2008 - 11:14 AM

Pete Dowson said:

Could you possibly enable SimConnect logging (as described in the FSX

Help announcement above), reproduce it, then ZIP up both the SimConnect

log and the FSUIPC log and send it to me, please?

I'm looking for a way to bypass SimConnect completely when assigning

axis "direct to FSUIPC". I've a feeling that my joystick axis scanning

rate may be exceeding SimConnect's "pipe" capacity and the automatic

throttling which should occur is cutting in too late, after corruption.

Once the data is corrupted anything can ensue.

Meanwhile, there is one other thing you can try to see if it has a

beneficial effect: reduce the axis polling frequency (i.e. increase the

interval) so that the load on Simconnect is less.

Posted 20 June 2008 - 12:52 AM

Pete Dowson said:

I've made a version of FSUIPC4 which avoids using SimConnect altogether

when you assign axes in FSUIPC for "direct to FSUIPC calibration". I'm

hoping that this will stop these crash/hang problems, but since i've

never been able to reproduce them I cannot tell.

Okay. I've modified it so that it still uses SimConnect but just for

"mapped" axes (e.g. throttles 2, 3 and 4 when only using one). This

otherwise causes a loop with interception followed by re-transmissions

ad infinitum.

Download this and try it, please:

http://fsuipc.simfli.../FSUIPC4291.zip

------------------------------------------------------------------------------------------

OK Onto my answers to your questions:

1) I have now upgraded to the latest version 4.836 and have tested using that version. The results are the same :-( freezing ...

2) The reason I select the "direct" option instead of Normal FS Controls is that it allows the axis to be detected in real time and I can then set ranges for the throttle more easily BUT most importantly when using two joysticks in my simulator (each with a throttle axis) the arbitration of the throttles (taking highest value is very useful .Perhaps I'm not understanding how to use this page properly ??? Also I always thought that to avoid conflicts with axis, you needed to clear them from the FSX controls menu ... I guess my understanding is also wrong here. Thank you for making me aware.

3) I employed null zones as you suggested and followed the User Guide for Calibration but this did not help solve the problem.

4) When I ticked Map 1 -> 234 as req for Throttle1 I was pretty sure it was required to allow both engines to be controlled (as for my previous FS2004 setup), what I forgot to mention is that without this tick one engine operated with the throttle BUT the freezes stopped occurring !!! so may maybe its related to that ??? As you mentioned in your post in 2008 on SimConnect and bypassing it, it seems SimConnect bypass is not implement for Mapping 1 throttle to 234... please see quote below.

Pete Dowson said:"

I've made a version of FSUIPC4 which avoids using SimConnect altogether

when you assign axes in FSUIPC for "direct to FSUIPC calibration". I'm

hoping that this will stop these crash/hang problems, but since i've

never been able to reproduce them I cannot tell.

Okay. I've modified it so that it still uses SimConnect but just for

"mapped" axes (e.g. throttles 2, 3 and 4 when only using one). This

otherwise causes a loop with interception followed by re-transmissions

ad infinitum.

"

I think what I'm relying on here is that my problem is similar to the one discussed in my referenced topic at the beginning of the post, that somehow something is going on in SimConnect and that it may be getting "garbage data" and causing the freezes. But again disregard if you do not think its relevant. I have no proof...

5) The fsuipc.ini file and subset of output is below:

[General]

UpdatedByVersion=4836

History=C7GUS5QOIYWV06GT1VO94

MouseWheelMove=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

DeleteVehiclesForAES=Yes

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=Yes

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=Yes

EnableMouseLook=No

AxesWrongRange=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

AutoScanDevices=Yes

OOMcheck=Yes

LogAxes=Yes

FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=No

3=CH FIGHTERSTICK USB

3.GUID={B9DCFE80-8400-11E1-8004-444553540000}

[buttons]

ButtonRepeat=20,10

1=P1,6,Cx51006DB5,x00080001

2=P1,4,Cx61006DB5,x00000001

3=R1,2,C65615,0

4=R1,3,C65607,0

5=R1,1,C66152,0

6=P1,7,C65589,0

7=P1,8,C65853,0

8=R1,5,C1001,0

9=U1,5,C1002,0

10=P1,0,C65567,0

11=P3,5,Cx07006DB3,x00000004

12=P3,4,Cx05006DB3,x01

13=U3,4,Cx09006DB3,x01

14=P3,7,Cx0D006DB3,x08

15=U3,5,Cx0B006DB3,x00000004

16=P3,6,Cx05006DB3,x02

17=U3,6,Cx09006DB3,x02

18=P3,1,Cx61006DB5,x00000001

19=P3,0,Cx53006DB5,x00080001

20=R3,3,C1001,0

21=U3,3,C1002,0

22=P3,13,C66279,0

23=P3,15,C66278,0

24=R3,8,C66152,0

25=R3,10,C66151,0

26=P3,11,C65853,0

27=P3,9,C65589,0

28=P3,16,C65567,0

29=R3,12,C65607,0

30=R3,14,C65615,0

31=R1,32,C65567,0

32=R1,36,C66151,0

33=R1,38,C65680,0

34=R1,34,C65676,0

35=R1,39,C65681,0

36=R1,33,C65675,0

37=R1,35,C65677,0

38=R1,37,C65679,0

39=U1,32,C66152,0

40=U1,36,C66151,0

[AutoSave]

Next=2

Interval=180

Files=5

SaveOnGround=Yes

AutoSaveEnabled=Yes

AlsoSave=latest_cond

AlsoInterval=180

1=Fri 222531

2=Fri 220228

3=Fri 220527

4=Fri 221403

5=Fri 222232

[GPSout]

GPSoutEnabled=No

Port=COM3

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[GPSout2]

GPSoutEnabled=No

Port=<none set>

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[WideServer]

WideFSenabled=Yes

AdvertiseService=1

Port=8002

Port2=9002

[sounds]

Path=C:\fsx\Sound\

Device1=Primary Sound Driver

Device2=Digital Audio (S/PDIF) (High Definition Audio Device)

[ClientNames]

1=LUCASLAPPY

2=SIMCOMPUTER

3=FLIGHT1

4=SIMCOMPUTER2

[Axes]

0=1S,256,D,9,0,0,0

1=2X,256,D,7,0,0,0

2=2X,BR,-16384,11776,x05006DB0,x01,x09006DB0,x01

3=2Y,256,D,8,0,0,0

4=2Y,BR,-16384,12544,x05006DB0,x02,x0B006DB0,x00000002

5=2Z,256,D,8,0,0,0

6=2Z,BR,-16253,11008,x05006DB0,x02,x09006DB0,x00

7=3Z,256,D,9,0,0,0

8=4X,256,D,7,0,0,0

9=4X,BR,-16384,9216,x05006DB0,x01,x09006DB0,x01

10=4Y,256,D,8,0,0,0

11=4Y,BR,-16384,9216,x05006DB0,x02,x09006DB0,x02

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=No

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

LeftBrake=-16384,11008/16

RightBrake=-16384,11264/16

Throttle1=-16380,-512,512,16380

MapThr1to234=Yes

Output from axis logging:

********* FSUIPC4, Version 4.836 by Pete Dowson *********

User Name="Luke Ramirez"

User Addr="luker23@hotmail.com"

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside FSX

Module base=61000000

156 System time = 15/06/2012 22:29:53

156 FLT UNC path = "C:\Users\Hansel\Documents\Flight Simulator X Files\"

187 Trying to connect to SimConnect Acc/SP2 Oct07 ...

202 FS UNC path = "C:\fsx\"

1014 Assuming running on Vista or later in compatibility mode!

1029 LogOptions=10000000 00000001

1029 Wind smoothing fix is fully installed

1029 G3D.DLL fix attempt installed ok

1029 SimConnect_Open succeeded: waiting to check version okay

1029 Trying to use SimConnect Acc/SP2 Oct07

5647 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

5647 Initialising SimConnect data requests now

5647 FSUIPC Menu entry added

5756 C:\Users\Hansel\Documents\Flight Simulator X Files\YSCB.FLT

5756 C:\fsx\SimObjects\Airplanes\B737_800\Boeing737-800.AIR

5959 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

5959 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -4004 (0xfffff05c) AXIS_ELEVATOR_SET

5959 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16193 (0xffffc0bf) AXIS_THROTTLE_SET

6411 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3840 (0xfffff100) AXIS_ELEVATOR_SET

6536 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3741 (0xfffff163) AXIS_ELEVATOR_SET

6598 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3769 (0xfffff147) AXIS_ELEVATOR_SET

6661 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3790 (0xfffff132) AXIS_ELEVATOR_SET

6739 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3744 (0xfffff160) AXIS_ELEVATOR_SET

6801 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3771 (0xfffff145) AXIS_ELEVATOR_SET

.......

676841 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3662 (0xfffff1b2) AXIS_ELEVATOR_SET

676919 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3666 (0xfffff1ae) AXIS_ELEVATOR_SET

676982 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 13348 (0x00003424) THROTTLE2_SET

676982 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 13348 (0x00003424) THROTTLE1_SET

676997 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3615 (0xfffff1e1) AXIS_ELEVATOR_SET

677044 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3582 (0xfffff202) AXIS_ELEVATOR_SET

677122 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 2907 (0x00000b5b) THROTTLE2_SET

677122 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 2907 (0x00000b5b) THROTTLE1_SET

677138 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3689 (0xfffff197) AXIS_ELEVATOR_SET

677200 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3684 (0xfffff19c) AXIS_ELEVATOR_SET

677262 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 0 (0x00000000) THROTTLE2_SET

677262 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 0 (0x00000000) THROTTLE1_SET

677294 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3680 (0xfffff1a0) AXIS_ELEVATOR_SET

677356 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3627 (0xfffff1d5) AXIS_ELEVATOR_SET

677403 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3640 (0xfffff1c8) AXIS_ELEVATOR_SET

677481 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3652 (0xfffff1bc) AXIS_ELEVATOR_SET

677543 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3659 (0xfffff1b5) AXIS_ELEVATOR_SET

677621 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3664 (0xfffff1b0) AXIS_ELEVATOR_SET

677684 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3667 (0xfffff1ad) AXIS_ELEVATOR_SET

677762 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3669 (0xfffff1ab) AXIS_ELEVATOR_SET

677808 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3670 (0xfffff1aa) AXIS_ELEVATOR_SET

677886 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3671 (0xfffff1a9) AXIS_ELEVATOR_SET

677949 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3672 (0xfffff1a8) AXIS_ELEVATOR_SET

Then FREEZE ( about a second after I operated the throttle).

Hope this helps Peter.

Cheers,

Luke

Link to comment
Share on other sites

Thank you for your quick reply. I'll take each point you have made separately for clarity. Just addressing your point firstly of where I found a related topic in your forum it was this one:FSX crashes with FSUIPC4 posted Jun 13 2008 04:38 AM.

2008!?

Within that topic you talk about direct calibration being more efficient and bypassing SimConnect.

No, you've read it incorrectly. It doesn't say that. It is not possible to bypass SimConnect successfully. The special test version it describes in one place was never released generally. All control is done through SimConnect. The "circuitous route" which is being bypassed is only the one described -- I've highlighted it here in red:

... the other method involves three times as many messages flying

about between FSUIPC and SimConnect -- one lot to send the axis values

to FS, then the same stuff being sent from FS to FSUIPC for calibration,

then back from FSUIPC to FS after calibration.

The last is still necessary otherwise FS will never see the request at all! The first two are omitted. If you assign in FS instead of FSUIPC you get two sets of messages, the last two.

I think what I'm relying on here is that my problem is similar to the one discussed in my referenced topic at the beginning of the post, that somehow something is going on in SimConnect and that it may be getting "garbage data" and causing the freezes. But again disregard if you do not think its relevant. I have no proof...

It's a pity you didn't provide a link to the 4 year old post you referenced, as I would be interested to see how it resolved. I certainly didn't remember it, nor have ever seen any similar incidents that I recall. If this was a general problem you'd expect to see it a lot.

There is a way to find out what SimConnect is doing, and that is to enable SimConnect logging and see what that log looks like. See the FAQ subforum where there are instructions for getting one of these.

Your INI file looks okay, though this shows you've not calibrated the throttle properly yet:

Throttle1=-16380,-512,512,16380

Those are the default values, certainly not agreeing with your earlier statement

... and proceeded to set each of the three zones as -16380, -7000 and 16383 to give a Reverser zone when the throttle range is between -16380 (fully back) and -7000 (approx. one quarter forward)

The logging shows a much lower and well spaced out set of axis requests. There's no way anything will be overloaded by this level. In fact considering FSUIPC polls the axes at set intervals, there's no way to overload anything no matter how assigned

There's something else going on in your system. I don't know where. You say

Then FREEZE ( about a second after I operated the throttle).

but as you can see, the only throttle operation going on is it being reduced to idle very quickly (the numbers on the left are miliiseconds, so thise complete sequencxe is less than a third of a second):

676982 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 13348 (0x00003424) THROTTLE2_SET

676982 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 13348 (0x00003424) THROTTLE1_SET

677122 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 2907 (0x00000b5b) THROTTLE2_SET

677122 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 2907 (0x00000b5b) THROTTLE1_SET

677262 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 0 (0x00000000) THROTTLE2_SET

677262 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 0 (0x00000000) THROTTLE1_SET

What else do you have installed in your FSX system? There must be something wrong somewhere, because your use of these facilities is very common and quite basic. It isn't complicated -- the mapping simply causes two controls to be sent instead of one, as you can see. For a 4 engined plave it would send 4. These aren't large loads for SimConnect -- you should see what happens with add-on aircraft like the PMDG or LevelD ones!

I'm not sure how to advise you to proceed. If you do have other add-ons try a process of elimination in case one of them is interacting here. And, as you say, you don't have a problem with other ways of assigning, so why not use those? You can do everything you are currenty doing with standard assignment to FS controls and also with assignment in FSX itself. In fact the more common way is to assign to generic throttle ("Throttle" for direct FSUIPC, "Axis throttle set" for FSUIPC assignment to FS control, or the one main throttle in FSX) then map it to the 4 separate throttles on page 1 of the FSUIPC calibrations. That's the way actually recommended in the FSUIPC User Guide.

Regards

Pete

Link to comment
Share on other sites

Hi Pete,

Thank you once again for your speedy response.

The quotes that came from the post in 2008 are in the forum and if searched for by the exact name (or even using "FSX freezes") you should be able to find it. Apologies for not posting a link I'm not too sure how to do that in this forum.

I too am stumped by this behaviour that I'm experiencing. I do have some Orbx scenery installed and some fly tampa but the only other thing that I can think of is Squawkbox 4 ( but not as a module within FSX) but I did have to install the SDK in order to make use of certain features to allow me to simConnect from my client (running SB4) to FSX... Maybe that's done it?

Anyhow I'm really tired of trying to troubleshoot as I've only had my system for a short period of time and still haven't enjoyed one single flight in my flightdeck.... This is a minor issue after all and I don't want to risk anything else "breaking"

Come to think of it I also use FS2PHIDGETS to control some of my hardware connected to my FSX PC but that was not operational when I was performing these tests.

Anyhow I am happy that I should be able to achieve what I intend to do using normal axis as you are recommending. The major reason I wanted to use direct to FSUIPC was to avoid any conflicts between my two joysticks.

Finally, I had calibrated the joystick I was using for testing this problem when I assigned axis was direct to FSUIPC. The default values you observed in my FSUIPC ini file was the result of me reseting everything again and just using the default values after pressing SET in the calibration page...as I performed the tests about 10-15 times so I was a bit tired by the end.

Incidentally Peter I'm really struggling to set the calibration of the throttle axis when using send to FS as normal axis. Reason is that when I try to calibrate I cannot see the in/out values when I move the throttle axis in the calibration page so I just press SET and accept the defaults, I've tried moving the axis and pressing set again but that just sets the value to ZERO for whatever range I'm trying to set. Your Docs does state that with sending to FS as normal axis the in/out values will not show real time so I'm aware of that but then how do I go about defining the ranges?

I will study the documentation again carefully. I probably have not interpreted it correctly.

So I will start using normal axis again and get back to flying :) hopefully I can work out how to assign reverse thrust to each axis of my joystick throttles. Then I'll be very happy once again. If not well I'll just have to wait until I upgrade my current system and carefully reinstall everything again and see if whatever is interfering with the axis mapping gets resolved.

But in the meantime I may continue to try to isolate the problem perhaps I could do some testing with my other joystick or try different aircraft types etc as my only small worry is that something is still not quite right and this may lead to nasty surprises further down the track (I hope not)

Once again many thanks for taking the time in trying to help me

Cheers

Luke

Link to comment
Share on other sites

Incidentally Peter I'm really struggling to set the calibration of the throttle axis when using send to FS as normal axis. Reason is that when I try to calibrate I cannot see the in/out values when I move the throttle axis in the calibration page

Wow! There's something really wrong if the values don't change.

This is assigning to "axis throttle set", then, on page 1 in FSUIPC calibration, checking to Map option, and then calibrating in the 4 throttles page?

If you are doing that and seeing no changes then you have some really serious problem somewhere. Please enable axis logging again and see if your joystick is actually doing anything.

So I will start using normal axis again and get back to flying :) hopefully I can work out how to assign reverse thrust to each axis of my joystick throttles.

Why not follow the instructions in the User Guide? You know the saying, "if all else fails, follow the instructions" or similar?

I assume your partner (the one using the other joystick) doesn't know any more?

Regards

Pete

Link to comment
Share on other sites

Hi Peter,

Yes that is correct I was not seeing values after assigning throttle set and the using the map to 4 throttles feature and calibrating in the 4 throttle page. So ... what I have done:

Re-read the manual paying attention to the step by step instructions. I then unplugged that joystick and plugged in another one (to eliminate possibiity of joystick malfunction).

I started FSX and tried a flight. At this stage FSX had recognised the joystick and all axis were working except of course this did not give me thrust reverse. These were all defined in FSX outside of FSUIPC.

I then reset the flight and went to the FSX Controls and deleted the Throttle axis. Then I went into FSUIPC and on the Axis Assignment tab I scanned for the throttle axis. It was detected (movement of the axis in the Axis Assignment tab cause the numbers to change from -16000 to +16000 approx.) and then I assigned "Send to FS as Normal Axis" then I selected "axis throttle set" as the function. I exited back to FSX and tried a flight. The axis worked. I did not calibrate through FSUIPC yet ...

I then went back in FSUIPC and the Axis Assignment Tab to make sure everything was still as assigned (to be sure). Then I went to the Joystick Calibration Tab (Page 1 Main Flight Controls) then I move the throttle up and down and could see the IN/OUT values in the throttle area moving properly. Now I hit set for both min and max and exited back to FSX to test.

Testing in FSX revealed that the throttle axis was still working AND when throttle fully back (negative value approx -16000) thrust reverse engaged. This was very promising !!!

So I now went back to the Joystick Calibration page in FSUIPC and then clicked map to 4 throttles near the bottom of Page 1 and then I went to Page 3 (Seperate throttles per engine). I did this so I could set an IDLE zone for the thrust reverse...here is where it went BAD. I pressed set (Next to Throttle 1 (direct) and the values that came up were the defaults with -512,512 for the centre values. Moving the throttle axis did NOT cause a change to the IN/OUT values in real time :-(

I went back to first page in the Joystick Calibration tab (Main Flight Controls) and unchecked the Map to 4 throtlles. I then move the throttle axis again and the IN/OUT values didn't change anymore there either .... hmmmm. I pressed set but no luck values would not change...just stayed at zero. So I went back to the Axis Assignment page. Deleted the Assignment and re-assigned as before.

Went back to the Joystick Calibration tab again (Page 1 - Main Controls) and I hit set. The default values appeared but the IN/OUT still remained zero. I exited back to FSX for a flight as I was very frustrated...The throttle worked but as before without an idle zone defined... at this stage I gave up. Incidently the IN/OUT values on the first page of the Joystick Calibration page worked well throughout for aileron and elevator axis. It is only the THROTTLE axis that had problems.

Finally I plugged in the original joystick I thought might have been faulty (I now had 2 joysticks pluggled in). It exhibited the same behaviour for the throttle axis (didn't calibrate properly)...in addition the aileron axis stopped working well in the first joystick I had plugged in..very difficult to turn so to rectify I unassigned that axis in FSX and re-assigned through FSUIPC and both joysticks worked well (except the throttle calibration problems mentioned above) interestingly enough the elevator axis for both joysticks remained defined in FSX and both worked properly unlike the aileron axis of which one I had to define through FSUIPC to avoid the conflict with turning the aircraft. No conflict however occurred for the elevator axis.

So there you have it Peter, another round of trouble shooting with very weird/strange abnormal behaviour. Although I cannot calibrate the throttle properly with FSUIPC, it seems to work even though it is frustrating that I cannot set a wide Idle zone...at least I can fly and have reversers....and the aileron and elevator axis both work well :-)

I guess it would be possible for me to modify the values for the Idle zone on the throttles in the FSUIPC.ini file instead of using the user interface in FSX ? Correct ? as that may be my last hope short of installing all of FSX and FSUIPC which would take days for me given my flightdeck setup.

Thanks again for your help

Cheers,

Luke

I

Link to comment
Share on other sites

I then went back in FSUIPC and the Axis Assignment Tab to make sure everything was still as assigned (to be sure). Then I went to the Joystick Calibration Tab (Page 1 Main Flight Controls) then I move the throttle up and down and could see the IN/OUT values in the throttle area moving properly. Now I hit set for both min and max and exited back to FSX to test.

Testing in FSX revealed that the throttle axis was still working AND when throttle fully back (negative value approx -16000) thrust reverse engaged. This was very promising !!!

No, on the contrary, it is not actually possible to get reverse thrust using the page 1 generic assignment. This is because it is still sending the Axis_Throttle_Set control, and that control provides no reverse thrust capabilities in FS at all! This is why it has to be mapped to the separate controls -- THROTTLEn_SET are the only ones offering reverse in FS, which is why they are mapped to those controls in the first place.

So there you have it Peter, another round of trouble shooting with very weird/strange abnormal behaviour. Although I cannot calibrate the throttle properly with FSUIPC, it seems to work even though it is frustrating that I cannot set a wide Idle zone...at least I can fly and have reversers....and the aileron and elevator axis both work well :smile:

I'm afraid none of the symptoms you describe make any sense at all to me, and are not and never have been reproducible here on any of my systems. If other folks were getting the results you are getting there'd be a hue and cry, because they simply negate one of the main and mostly used facilities FSUIPC offers.

As I said, it is just not possible in FS to get axis-driven reverse using the normal Axis controls. So I am completely bewildered at what is going on in your system. And because of that I've no idea what to suggest. Perhaps at least enable the Axis Logging again and show me a section of the log where you are achieving reverse thrust with the generc throttle assignment only. I'd also like to see the INI file again please.

Pete

Link to comment
Share on other sites

Hi Peter,

Yes I totally agree that this is not common and most likely something is wrong with my FSX installation, like you say if it was a common occurrence there would be other folk posting about this issue.

I will send the latest FSUIPC.INI file as well as a portion of the logs showing throttle operation on both throttle axis of each joystick if that helps.

Oddly I do have thrust reverse on both throttle axis as reported above. Am I going mad ???? I cannot understand how it can be but I do and it works.

Anyhow I'll provide those files tomorrow but I understand if you cannot help me further as I already greatly appreciate both your patience and time you have spent looking at this puzzling problem.

I just hope that this behaviour is not the result of something I'm doing wrong as I don't want to be wasting your time.

Cheers

Luke

Link to comment
Share on other sites

Hello Peter,

I hope you have had a good weekend. I have produced another axis log within FSUIPC which logs my use of the throttle axis on each of my two joysticks in FSX. I moved the throttle axis on each joystick a few times exercising it from "reverse" to full. I know this cannot be possible but perhaps even though the user interface does not show the IN/OUT values maybe somehow it is still being inputted ??? I have looked at the aircraft in SPOT view when operating the throttle to confirm reverser and I can see on the engine pods the reverser is open and after a little while the aircraft moves backwards.

Each throttle axis exhibits about 40-50% of its range as reverser (perhaps this is a FSUIPC default). So although it mysteriously works...it is a bit annoying that I cannot fine tune it in the calibration page and modify the ranges.

By the way I also repeated this experiment using my old laptop with my no longer used FS2004 and FSUIPC 3.90 (I know old version but I've discontinued using it) so I could definitely eliminate joystick errors. FSUIPC for axis assignment and joystick calibration worked perfectly. I even made sure that the first time I mapped the axis I only used page one to ensure I could not get thrust reverse and as you say I didn't get it. I then went to page 3 (seperate throttles) after mapping in page one and set up the ranges for reverse, idle and max and all work perfectly and IN/OUT values were showing each time I moved the axis. Exactly like you intended it to work ....

So ... what I can say for certain...something is wrong with my FSX with the Joystick Calibration through FSUIPC and using direct to FSUIPC Calibration causes it to freeze, whereas using Direct to FS does not cause it to freeze but calibration is not possible because IN/OUT values only appear "randomly" usually when I've unplugged and re-plugged the joystick but then when I go back into the calibration pages the IN/OUT no longer show...I know this is very confusing.

Could it be perhaps the way Windows 7 32bit (which is what Im using) on my system is reading the USB port and the input from the joystick...perhaps my USB ports are at fault? Just a wild guess. BUT the elevator and aileron axis seem to work ok with FSUIPC...

Anyhow below is my FSUIPC config file followed by a portion of the axis logging log (I have edited it to allow show portions pertaining to the throttle movement as it is otherwise too big to paste into the forum) if you are interested in seeing it in its entirety let me know and I can e-mail it.

Cheers,

Luke

FSUIPC Congiguration File:

[General]

UpdatedByVersion=4836

History=I0A6QYJIUR4J9NDS0UN8G

MouseWheelMove=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

DeleteVehiclesForAES=Yes

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=Yes

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=Yes

EnableMouseLook=No

AxesWrongRange=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

AutoScanDevices=Yes

OOMcheck=Yes

FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=No

0=Logitech Attack 3

0.GUID={A0608B50-7692-11E1-8001-444553540000}

3=CH FIGHTERSTICK USB

3.GUID={B9DCFE80-8400-11E1-8004-444553540000}

[buttons]

ButtonRepeat=20,10

1=P1,6,Cx51006DB5,x00080001

2=P1,4,Cx61006DB5,x00000001

3=R1,2,C65615,0

4=R1,3,C65607,0

5=R1,1,C66152,0

6=P1,7,C65589,0

7=P1,8,C65853,0

8=R1,5,C1001,0

9=U1,5,C1002,0

10=P1,0,C65567,0

11=P3,5,Cx07006DB3,x00000004

12=P3,4,Cx05006DB3,x01

13=U3,4,Cx09006DB3,x01

14=P3,7,Cx0D006DB3,x08

15=U3,5,Cx0B006DB3,x00000004

16=P3,6,Cx05006DB3,x02

17=U3,6,Cx09006DB3,x02

18=P3,1,Cx61006DB5,x00000001

19=P3,0,Cx53006DB5,x00080001

20=R3,3,C1001,0

21=U3,3,C1002,0

22=P3,13,C66279,0

23=P3,15,C66278,0

24=R3,8,C66152,0

25=R3,10,C66151,0

26=P3,11,C65853,0

27=P3,9,C65589,0

28=P3,16,C65567,0

29=R3,12,C65607,0

30=R3,14,C65615,0

31=R1,32,C65567,0

32=R1,36,C66151,0

33=R1,38,C65680,0

34=R1,34,C65676,0

35=R1,39,C65681,0

36=R1,33,C65675,0

37=R1,35,C65677,0

38=R1,37,C65679,0

39=U1,32,C66152,0

40=U1,36,C66151,0

[AutoSave]

Next=2

Interval=180

Files=5

SaveOnGround=Yes

AutoSaveEnabled=Yes

AlsoSave=latest_cond

AlsoInterval=180

1=Sun 101100

2=Sat 181441

3=Sun 095409

4=Sun 095708

5=Sun 100800

[GPSout]

GPSoutEnabled=No

Port=COM3

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[GPSout2]

GPSoutEnabled=No

Port=<none set>

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[WideServer]

WideFSenabled=Yes

AdvertiseService=1

Port=8002

Port2=9002

[sounds]

Path=C:\fsx\Sound\

Device1=Primary Sound Driver

Device2=Digital Audio (S/PDIF) (High Definition Audio Device)

[ClientNames]

1=LUCASLAPPY

2=SIMCOMPUTER

3=FLIGHT1

4=SIMCOMPUTER2

[Axes]

0=0X,256,F,65695,0,0,0

1=0Z,256,F,65697,0,0,0

2=1S,256,D,9,0,0,0

3=2X,256,D,7,0,0,0

4=2X,BR,-16384,11776,x05006DB0,x01,x09006DB0,x01

5=2Y,256,D,8,0,0,0

6=2Y,BR,-16384,12544,x05006DB0,x02,x0B006DB0,x00000002

7=2Z,256,D,8,0,0,0

8=2Z,BR,-16253,11008,x05006DB0,x02,x09006DB0,x00

9=3Z,1171,F,65697,0,0,0

10=4X,256,D,7,0,0,0

11=4X,BR,-16384,9216,x05006DB0,x01,x09006DB0,x01

12=4Y,256,D,8,0,0,0

13=4Y,BR,-16384,9216,x05006DB0,x02,x09006DB0,x02

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=No

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

LeftBrake=-16384,11008/16

RightBrake=-16384,11264/16

Throttle=-16193,-16193

Aileron=-16380,-512,512,16380

Elevator=-16380,-512,512,16380

AXIS Logging file (edited portion)

******** FSUIPC4, Version 4.836 by Pete Dowson *********

User Name="Luke Ramirez"

User Addr="luker23@hotmail.com"

FSUIPC4 Key is provided

WideFS7 Key is provided

[Continuation log requested by user]

Running inside FSX on Windows Vista

Module base=0E490000

236623 System time = 17/06/2012 10:08:46, Simulator time = 15:09:06 (08:09Z)

236669 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -1349 (0xfffffabb) AXIS_AILERONS_SET

236669 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -865 (0xfffffc9f) AXIS_AILERONS_SET

236685 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -866 (0xfffffc9e) AXIS_AILERONS_SET

236779 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -867 (0xfffffc9d) AXIS_AILERONS_SET

237059 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -857 (0xfffffca7) AXIS_AILERONS_SET

237075 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -859 (0xfffffca5) AXIS_AILERONS_SET

237075 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -868 (0xfffffc9c) AXIS_AILERONS_SET

237278 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -860 (0xfffffca4) AXIS_AILERONS_SET

237293 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -869 (0xfffffc9b) AXIS_AILERONS_SET

237839 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -878 (0xfffffc92) AXIS_AILERONS_SET

237886 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -869 (0xfffffc9b) AXIS_AILERONS_SET

238292 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -861 (0xfffffca3) AXIS_AILERONS_SET

238307 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -862 (0xfffffca2) AXIS_AILERONS_SET

238307 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -863 (0xfffffca1) AXIS_AILERONS_SET

238323 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -864 (0xfffffca0) AXIS_AILERONS_SET

238339 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -854 (0xfffffcaa) AXIS_AILERONS_SET

238339 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -866 (0xfffffc9e) AXIS_AILERONS_SET

238448 *** AXIS: Cntrl= 65697 (0x000100a1), Param= -13003 (0xffffcd35) THROTTLE_SET

238479 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -867 (0xfffffc9d) AXIS_AILERONS_SET

238541 *** AXIS: Cntrl= 65697 (0x000100a1), Param= -7022 (0xffffe492) THROTTLE_SET

238635 *** AXIS: Cntrl= 65697 (0x000100a1), Param= -3121 (0xfffff3cf) THROTTLE_SET

238666 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -876 (0xfffffc94) AXIS_AILERONS_SET

238697 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -885 (0xfffffc8b) AXIS_AILERONS_SET

238697 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -884 (0xfffffc8c) AXIS_AILERONS_SET

238713 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -883 (0xfffffc8d) AXIS_AILERONS_SET

238729 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -882 (0xfffffc8e) AXIS_AILERONS_SET

238729 *** AXIS: Cntrl= 65697 (0x000100a1), Param= -390 (0xfffffe7a) THROTTLE_SET

238838 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 3200 (0x00000c80) THROTTLE_SET

238916 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 4864 (0x00001300) THROTTLE_SET

239025 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -872 (0xfffffc98) AXIS_AILERONS_SET

239119 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 8192 (0x00002000) THROTTLE_SET

239212 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 10368 (0x00002880) THROTTLE_SET

239306 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 12672 (0x00003180) THROTTLE_SET

239399 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 16383 (0x00003fff) THROTTLE_SET

239509 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -863 (0xfffffca1) AXIS_AILERONS_SET

239524 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -864 (0xfffffca0) AXIS_AILERONS_SET

239540 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -865 (0xfffffc9f) AXIS_AILERONS_SET

239727 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -874 (0xfffffc96) AXIS_AILERONS_SET

.....

257730 *** AXIS: Cntrl= 65697 (0x000100a1), Param= -13653 (0xffffcaab) THROTTLE_SET

257745 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -903 (0xfffffc79) AXIS_AILERONS_SET

257745 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -901 (0xfffffc7b) AXIS_AILERONS_SET

257761 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -899 (0xfffffc7d) AXIS_AILERONS_SET

257776 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -908 (0xfffffc74) AXIS_AILERONS_SET

257792 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -906 (0xfffffc76) AXIS_AILERONS_SET

257808 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -896 (0xfffffc80) AXIS_AILERONS_SET

257823 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -895 (0xfffffc81) AXIS_AILERONS_SET

257823 *** AXIS: Cntrl= 65697 (0x000100a1), Param= -6761 (0xffffe597) THROTTLE_SET

257839 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -894 (0xfffffc82) AXIS_AILERONS_SET

257854 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -912 (0xfffffc70) AXIS_AILERONS_SET

257870 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -910 (0xfffffc72) AXIS_AILERONS_SET

257886 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -908 (0xfffffc74) AXIS_AILERONS_SET

257886 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -906 (0xfffffc76) AXIS_AILERONS_SET

257917 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -915 (0xfffffc6d) AXIS_AILERONS_SET

257917 *** AXIS: Cntrl= 65697 (0x000100a1), Param= -1300 (0xfffffaec) THROTTLE_SET

257917 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -912 (0xfffffc70) AXIS_AILERONS_SET

257948 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -910 (0xfffffc72) AXIS_AILERONS_SET

257948 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -908 (0xfffffc74) AXIS_AILERONS_SET

257964 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -906 (0xfffffc76) AXIS_AILERONS_SET

257979 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -904 (0xfffffc78) AXIS_AILERONS_SET

257995 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -902 (0xfffffc7a) AXIS_AILERONS_SET

258010 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -900 (0xfffffc7c) AXIS_AILERONS_SET

258010 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 512 (0x00000200) THROTTLE_SET

258026 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -898 (0xfffffc7e) AXIS_AILERONS_SET

258042 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -897 (0xfffffc7f) AXIS_AILERONS_SET

258057 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -896 (0xfffffc80) AXIS_AILERONS_SET

258057 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -895 (0xfffffc81) AXIS_AILERONS_SET

258088 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -894 (0xfffffc82) AXIS_AILERONS_SET

258088 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -893 (0xfffffc83) AXIS_AILERONS_SET

258120 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -892 (0xfffffc84) AXIS_AILERONS_SET

258120 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 1792 (0x00000700) THROTTLE_SET

258120 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -891 (0xfffffc85) AXIS_AILERONS_SET

258135 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -889 (0xfffffc87) AXIS_AILERONS_SET

258151 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -888 (0xfffffc88) AXIS_AILERONS_SET

258166 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -887 (0xfffffc89) AXIS_AILERONS_SET

258182 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -886 (0xfffffc8a) AXIS_AILERONS_SET

258198 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -885 (0xfffffc8b) AXIS_AILERONS_SET

258198 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 3328 (0x00000d00) THROTTLE_SET

258198 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -897 (0xfffffc7f) AXIS_AILERONS_SET

258229 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -896 (0xfffffc80) AXIS_AILERONS_SET

258229 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -895 (0xfffffc81) AXIS_AILERONS_SET

258260 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -894 (0xfffffc82) AXIS_AILERONS_SET

258260 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -893 (0xfffffc83) AXIS_AILERONS_SET

258276 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -892 (0xfffffc84) AXIS_AILERONS_SET

258291 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -891 (0xfffffc85) AXIS_AILERONS_SET

258291 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 5376 (0x00001500) THROTTLE_SET

258307 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -889 (0xfffffc87) AXIS_AILERONS_SET

258322 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -877 (0xfffffc93) AXIS_AILERONS_SET

258385 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 6656 (0x00001a00) THROTTLE_SET

258478 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 7936 (0x00001f00) THROTTLE_SET

258572 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 8320 (0x00002080) THROTTLE_SET

258666 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -888 (0xfffffc88) AXIS_AILERONS_SET

258666 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 8576 (0x00002180) THROTTLE_SET

258697 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -887 (0xfffffc89) AXIS_AILERONS_SET

258697 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -886 (0xfffffc8a) AXIS_AILERONS_SET

258712 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -885 (0xfffffc8b) AXIS_AILERONS_SET

258728 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -884 (0xfffffc8c) AXIS_AILERONS_SET

258744 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -872 (0xfffffc98) AXIS_AILERONS_SET

258868 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 9344 (0x00002480) THROTTLE_SET

258946 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -883 (0xfffffc8d) AXIS_AILERONS_SET

258946 *** AXIS: Cntrl= 65697 (0x000100a1), Param= 9728 (0x00002600) THROTTLE_SET

258978 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -882 (0xfffffc8e) AXIS_AILERONS_SET

260210 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -871 (0xfffffc99) AXIS_AILERONS_SET

260382 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -882 (0xfffffc8e) AXIS_AILERONS_SET

260522 Sim stopped: average frame rate for last 24 secs = 77.4 fps

Link to comment
Share on other sites

You have assigned the throttles to "throttle set", not "axis throttle set" as I instructed. I don't think the now defunct "throttle set" can be handled in the way you want. It's of very secialist use within certain add-ons.

You also have an unknown (not connected) axis assigned the Throttle1 direct, as shown in this line:

2=1S,256,D,9,0,0,0

That assignment can easily interfere. Best delete it, as with other assignments to non-existent devices.

You have axis assignments for three devices which aren't listed as connected (devices with joystick nmbers 1, 2 and 4), including two axes on the same unknown device both assigned to the right toe brake:

5=2Y,256,D,8,0,0,0

6=2Y,BR,-16384,12544,x05006DB0,x02,x0B006DB0,x00000002

7=2Z,256,D,8,0,0,0

8=2Z,BR,-16253,11008,x05006DB0,x02,x09006DB0,x00

with a third on a different unknown device:

12=4Y,256,D,8,0,0,0

13=4Y,BR,-16384,9216,x05006DB0,x02,x09006DB0,x02

You only have two assignments to the left brake, though.

Finally, you don't seem to have (yet) gone through the calibration steps on either the ailerons or elevator. These are the defauls:

Aileron=-16380,-512,512,16380

Elevator=-16380,-512,512,16380

I've never known any device which exactly suit the defaults!

Regards

Pete

Link to comment
Share on other sites

Hi Peter,

The unknown devices would be the other joystick in my flightdeck and two sets of rudder pedals. The reason they are not connected Is because I chose to bring the FSX Server PC inside the house to troubleshoot the problems with the freezing (it was too difficult to bring in the other equipment) and too cold to do the troubleshooting in the garage were the flightdeck resides (we are having quite a cold winter here in Australia)

So I decided to use one of the flightdeck joysticks (which I could easily get to) and to test dual control I plugged in a spare joystick I had in the house.

I will rectify the Axis Throttle Set assignment that you pointed out that I have mistakenly assigned to Throttle Set instead.

It may even be best just to delete ALL axis assignments and start all over again to avoid conflicts and further confusion.

What is the best way of accomplishing axis deletion? Should I delete them in the FSUIPC.ini file? Or connect up the offending devices, detect them via scanning for them and then deleting them in the FSUIPC interface ?

Cheers

Luke

Link to comment
Share on other sites

What is the best way of accomplishing axis deletion? Should I delete them in the FSUIPC.ini file?

Easiest way to delete them all is simply to delete the [Axes] section completely.

Or connect up the offending devices, detect them via scanning for them and then deleting them in the FSUIPC interface ?

One problem if you keep unplugging and plugging things in again is the possibility of Windows assignng different ID numbers to them next time. This will not only mess the Axis assignments up but also all the button assignments. It isn't just a matter of always using the same USB sockets, but the order in which you reconnect them (if power is on). With multiple devices you should really consider using the joy letters instead -- you can assign them mnemonically, or just let FSUIPC assign them automatically (A, B, C ...). After that FSUIPC will identify them by their names and GUIDs (that's why thast section in the INI is there).

Regards

Pete

Link to comment
Share on other sites

Hi Peter,

A short update. I deleted my axis assignments as suggested and assigned and calibrated one of the joysticks in FSX using FSUIPC. Both the axis assignment and Calibration worked perfectly.

Thank you !!!

Over the next few days I'll be moving the server back into the flightdeck and re-assigning and calibrating all the rest of the devices and hopefully that will not cause conflicts.

Out of curiosity I tried direct to FSUIPC Calibration to see if the freezing/hanging problem had been solved by clearing the axis and starting over. I completed one flight without a freeze using this setting in FSUIPC. All is looking positive !

I'll be reading the manual again to learn more about using Joystick letters instead of the windows IDs as I regularly turn everything off in the Flightdeck after completing flights so I think I should be using the letters as you suggest.

Final question. Because one of my joysticks is force feedback I'll need to let FSX handle the axis otherwise I'll lose the Force feedback function ( as I understand it) if that's the case is there any problem with one joystick being assigned via FSUIPC and the other via FSX ??? I'm just mindful of causing another conflict. My testing shows this should not be an issue but I thought I'd check with you as well

Cheers

Luke

Link to comment
Share on other sites

... is there any problem with one joystick being assigned via FSUIPC and the other via FSX ?

No, provided the same axes are not assigned in both. Also be aware that FS does have a nasty habit of auto-assigning devices which it thinks are newly attached. This is why most folks who assign in FSUIPC disable controllers in FS. I don't think this problem is so prevalent in FSX as it was in FS9 and before, but just wacth out. If things start playing up, look in the FSX assignments to see if this has happened. It shouldn't unless you unplug and replug-in controllers.

Regards

Pete

Link to comment
Share on other sites

Hi Peter,

I hope you are having a good weekend. Well I moved my FSX server PC back to the flightdeck and attached all joystick devices and rudder pedals to the server. I assigned throttle via direct to FS and assigned axis thottle set and mapped the throttle to 4 engines in the calibaration tab for both joysticks. For joystick 1 I also assgned axis for elevator and aileron though FSUIPC and calibrated. For joystick 2 I left assignment to FSX as it is force feedback and I wanted to retain this functionality. For both sets of rudder pedals and toe brakes I use FCUIPC axis assignment and calibration.

I flew a circuit around the airport and everything was working well and I can confirm the freezes/hangs have GONE thankfully. It is a joy to have things calibrated well as you recommended. Starting over again although a bit painful was worth the final result !

I have posted the final resultant FSUIPC ini for you to have a quick look (if you are able - it is much appreciated) in case you can see any pontential issues.

I have one final question as that is with Joynames section of the ini file. If I leave leave AutoAssignLetters = NO then can I simply place letters from A-Z in front of the joysticks/device name and a matching letter in fron of the GUID entry to make it work ? (Currently only numbers 1 - n are setup) I guess to make it work automatically I can set AutoAssignLetters = YES ? But if I do this when do the letters get assigned ? Is it the next time FSX Starts OR should I do it manually to avoid any issues ?

I guess that is the last thing I need to set up. The letters for the devices. As I'm very worried that when I turn things back on they may get assigned differently especially since I'm using a powered HUB to handle most of the joystick connections and sometimes I do not turn it on as I just want to perform upgrades/maintenance to my FSX server PC rather than go for a flight.

So ... should I be setting the Letters for the devices BEFORE I start FSX again? OR is the risk small and I should just set AutoAssignLetters = YES and start FSX

Thank you for your help and advice through my troublesome time.

Cheers,

Luke

==============================

New FSUIPC.ini

[General]

UpdatedByVersion=4836

History=0RWMIQB4AJCPTSRAJD6RJ

MouseWheelMove=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

DeleteVehiclesForAES=Yes

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=Yes

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=Yes

EnableMouseLook=No

AxesWrongRange=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

AutoScanDevices=Yes

OOMcheck=Yes

FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=No

3=CH FIGHTERSTICK USB

3.GUID={B9DCFE80-8400-11E1-8004-444553540000}

1=Logitech WingMan Force USB

1.GUID={B9DB77E0-8400-11E1-8002-444553540000}

2=CH PRO PEDALS USB

2.GUID={B9DCFE80-8400-11E1-8003-444553540000}

4=Saitek Pro Flight Rudder Pedals

4.GUID={B9DCFE80-8400-11E1-8005-444553540000}

[buttons]

ButtonRepeat=20,10

1=P1,6,Cx51006DB5,x00080001

2=P1,4,Cx61006DB5,x00000001

3=R1,2,C65615,0

4=R1,3,C65607,0

5=R1,1,C66152,0

6=P1,7,C65589,0

7=P1,8,C65853,0

8=R1,5,C1001,0

9=U1,5,C1002,0

10=P1,0,C65567,0

11=P3,5,Cx07006DB3,x00000004

12=P3,4,Cx05006DB3,x01

13=U3,4,Cx09006DB3,x01

14=P3,7,Cx0D006DB3,x08

15=U3,5,Cx0B006DB3,x00000004

16=P3,6,Cx05006DB3,x02

17=U3,6,Cx09006DB3,x02

18=P3,1,Cx61006DB5,x00000001

19=P3,0,Cx53006DB5,x00080001

20=R3,3,C1001,0

21=U3,3,C1002,0

22=P3,13,C66279,0

23=P3,15,C66278,0

24=R3,8,C66152,0

25=R3,10,C66151,0

26=P3,11,C65853,0

27=P3,9,C65589,0

28=P3,16,C65567,0

29=R3,12,C65607,0

30=R3,14,C65615,0

31=R1,32,C65567,0

32=R1,36,C66151,0

33=R1,38,C65680,0

34=R1,34,C65676,0

35=R1,39,C65681,0

36=R1,33,C65675,0

37=R1,35,C65677,0

38=R1,37,C65679,0

39=U1,32,C66152,0

40=U1,36,C66151,0

[AutoSave]

Next=4

Interval=180

Files=5

SaveOnGround=Yes

AutoSaveEnabled=Yes

AlsoSave=latest_cond

AlsoInterval=180

1=Sat 155748

2=Sat 160047

3=Sat 160347

4=Sat 153352

5=Sat 155149

[GPSout]

GPSoutEnabled=No

Port=COM3

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[GPSout2]

GPSoutEnabled=No

Port=<none set>

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[WideServer]

WideFSenabled=Yes

AdvertiseService=1

Port=8002

Port2=9002

[sounds]

Path=C:\fsx\Sound\

Device1=Primary Sound Driver

Device2=Digital Audio (S/PDIF) (High Definition Audio Device)

[ClientNames]

1=LUCASLAPPY

2=SIMCOMPUTER

3=FLIGHT1

4=SIMCOMPUTER2

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=No

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

LeftBrake=-16384,11008/16

RightBrake=-16384,11264/16

Aileron=-16123,-1430,1536,16000/8

Elevator=-15603,-1430,256,15616/8

Throttle1=-16253,-5461,-520,16128

MapThr1to234=Yes

MapThrottle=Yes

Rudder=-16190,-3032,4032,16000/8

[Axes]

0=1S,256,F,65765,0,0,0

1=2X,256,F,66387,0,0,0

2=2X,BR,-16123,15872,x05006DB0,x01,x09006DB0,x01

3=2Y,256,F,66388,0,0,0

4=2Y,BR,-15213,15616,x05006DB0,x02,x09006DB0,x02

5=2Z,256,F,65764,0,0,0

6=3X,256,F,65763,0,0,0

7=3Y,256,F,65762,0,0,0

8=3Z,256,F,65765,0,0,0

9=4X,256,F,66387,0,0,0

10=4X,BR,-15591,15104,x05006DB0,x01,x09006DB0,x01

11=4Y,256,F,66388,0,0,0

12=4Y,BR,-15591,16128,x05006DB0,x02,x09006DB0,x02

13=4R,256,F,65764,0,0,0

Link to comment
Share on other sites

I have posted the final resultant FSUIPC ini for you to have a quick look (if you are able - it is much appreciated) in case you can see any pontential issues.

Looks a lot better, and with properly calibrated axes by the look of it! ;-)

I have one final question as that is with Joynames section of the ini file. If I leave leave AutoAssignLetters = NO then can I simply place letters from A-Z in front of the joysticks/device name and a matching letter in fron of the GUID entry to make it work ? (Currently only numbers 1 - n are setup) I guess to make it work automatically I can set AutoAssignLetters = YES ? But if I do this when do the letters get assigned ? Is it the next time FSX Starts OR should I do it manually to avoid any issues ?

Either will work, but I always recommend toing it manually so you can choose letters which bear some relation to the function. For example, in your case, just add these lines to the [JoyNames] section:

S=CH FIGHTERSTICK USB

S.GUID={B9DCFE80-8400-11E1-8004-444553540000}

W=Logitech WingMan Force USB

W.GUID={B9DB77E0-8400-11E1-8002-444553540000}

P=CH PRO PEDALS USB

P.GUID={B9DCFE80-8400-11E1-8003-444553540000}

R=Saitek Pro Flight Rudder Pedals

R.GUID={B9DCFE80-8400-11E1-8005-444553540000}

Regards

Pete

Link to comment
Share on other sites

Ok Thanks Peter

I have now added the above lines to my [JoyNames] section as advised.

I assume the addition replaces what was there previously (that is, the numbered devices) rather than just adding a second set of devices with letter in front of the Joystick/device names and GUIDs in addition to leaving the originals with numbers in front of them

So my [JoyNames] section only contains what you posted above in boldface. I deleted the numbered joystick/device lines and the numbered GUID lines.

I tried to check the manual for clarity and it did seem to imply this but without actually stating that it replaces the numbers in front of the devices. Logically I think it would.

Hopefully I'm correct. A test flight tomorrow will confirm :)

Thank you again

Cheers

Luke

Link to comment
Share on other sites

I assume the addition replaces what was there previously (that is, the numbered devices) rather than just adding a second set of devices with letter in front of the Joystick/device names and GUIDs in addition to leaving the originals with numbers in front of them

No. The numbers are the IDs assigned by Windows and used internally. FSUIPC cannot address the devices by letters. It uses the [Joynames] section to relate the letters to the numbers.

So my [JoyNames] section only contains what you posted above in boldface. I deleted the numbered joystick/device lines and the numbered GUID lines.

Well, it will re-locate the numbers it needs in the Windows registry, relating them by comparing names and GUIDs, and restore the lines you deleted. It's just less efficient that one time. With the lines already there it knows exactly where to check, else there's a small search involved which it would otherwise only need to if there was no match found at that numerical ID.

I tried to check the manual for clarity and it did seem to imply this but without actually stating that it replaces the numbers in front of the devices. Logically I think it would.

Well, as i just said, it won't matter either way -- FSUIPC will correct the section when it is run.

Regards

Pete

Link to comment
Share on other sites

Hi Peter,

I thought I'd post an update after finally being able to test the flightdeck with the joysticks connected and properly calibrated :) thanks to your help.

The flight started well and the calibration made it a joy to fly with precision. However 10 minutes into the flight the force feedback joystick (Wingman) which is powered, stopped responding...umm weird. I continued to fly on with the other joystick

In the meantime I tried unplugging the failed joystick and re-plugging in without success. The joystick would no longer respond within flight simulator even though it was powered and plugged back in. Although I did expect this behaviour as its what it has exhibited In the past (once un-plugged and re-plugged I have exit FS to get it re-detected even in my FS2004 days)

Then within 10 minutes of landing (about 35mins after takeoff) FSX once again hanged and I experienced a freeze. I will note that the force feedback joystick that failed was not the one I conducted my testing with when I originally removed the FSX server PC to trouble shoot the original freeze/hang issues.

I un-plugged the joystick once again and rebooted the clients and the FSX server and repeated the flight. This time success (without the offending joystick)

So I think that joystick may have caused the problems but I cannot be sure .... I guess what I could do is plug it back in and this time assign through FSUIPC like the working joystick and sacrifice the force feedback functionality and see whether assigning through FSUIPC the problem goes away.

Link to comment
Share on other sites

This is the only way I can think of re-testing otherwise I may just try a different joystick.

Needless to say as you pointed out FSUIPC was never the problem and worked flawlessly.

Thank you for your patience and advice through my testing and problems. I think I'm getting closer to the root of the problem but I'm not quiter ther yet.

Cheers

Luke

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.