Stick uses throttle assignments, throttle uses stick assignments

[vesalius]

Hello,

 

Going to keep it brief and simple.

 

I just did a clean of Windows 10 and Prepar3d v3.

I installed simconnect from the Prepar3D v3 redist folder (to have A2A stuff working)

I deleted all joystick axis and buttons assignments from P3D.

I downloaded, installed and registered FSUIPC.

I restored the fsuipc.ini version from my "pre-restaging" Prepar3d v3 with all its configs and settings like I want.

 

Now, my throttle is being treated as if it was the stick and the stick as if it was the throttle.

 

I had this also during my last reinstall over a year back, and managed to solve it back then. Unfortunatelly for me, I did not document this :(

I believe it had something to do with the [JoyNames] sections (swapping names and/or GUID's) but this time with no luck.

 

Anyone know this situation?

[Axes]
PollInterval=10
RangeRepeatRate=10
0=0X,256,F,65763,0,0,0
1=0Y,256,F,65762,0,0,0
2=0R,256,F,65764,0,0,0
3=1X,256,F,66420,66426,0,0
4=1Y,256,F,66423,66429,0,0
5=1Z,256,F,66818,65764,0,0
6=1R,256,F,66291,0,0,0
7=1U,256,F,65706,0,0,0
8=1V,256,F,66292,0,0,0

[Buttons]
PollInterval=25
ButtonRepeat=20,10
2=R0,12,C65615,0
3=R0,10,C65607,0
4=R0,13,C66276,0
5=R0,11,C66277,0
6=P0,1,C66731,0
7=P0,3,C65564,0
8=U0,12,C65615,0
9=U0,10,C65607,0
10=U0,13,C66276,0
11=U0,11,C66277,0
28=R0,0,C65588,0
29=U0,0,C65588,0
30=P1,10,C66080,0
31=P1,9,C66079,0
32=P1,8,C65758,0
33=P0,14,C66079,0
35=P0,16,C66080,0
37=P1,3,C65588,0
38=R1,27,C65598,0
39=U1,27,C65600,0
40=R1,28,C65602,0
41=U1,28,C66634,0
42=P1,30,C65615,0
43=P1,29,C65607,0
44=P1,7,C65759,0
46=R1,6,C66059,0
47=R1,5,C66060,0
48=P1,0,C65791,0
49=P0,4,C65567,0
50=P0,5,C66167,0
51=P1,18,C66052,0
52=P1,17,C66053,0
54=U1,5,C66240,0
55=U1,6,C66240,0
56=P1,16,C66239,0
57=P1,15,C66239,0

[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
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
Aileron=-16380,-512,512,16380
Elevator=-16380,-13,512,16380
SlopeElevator=5
Rudder=-16380,0,512,16380
SlopeRudder=15
SteeringTiller=-16380,-512,512,16380
SlopeSteeringTiller=11

[Profile.Bell407]
1=Bell 407 N14HX
2=Bell 407 N175P
3=Bell 407 N407MJ
4=Bell 407 N108MF
5=Bell 407 G-BLCK
6=Bell 407 VH-ICK
7=Bell 407 N8NR
8=Bell 407 N315RR
9=Bell 407 Dark

[Axes.Bell407]
RangeRepeatRate=10
0=0X,256,F,65763,0,0,0
1=0Y,256,F,65762,0,0,0
2=1X,256,F,66420,66426,0,0
3=1Y,256,F,66423,66429,0,0
4=1Z,256,F,65764,0,0,0
5=1R,256,F,66291,0,0,0
6=1U,256,F,65706,0,0,0
7=1V,256,F,66292,0,0,0

[Profile.Airbus]
1=Airbus A319 Brussels Airlines STAR ALLIANCE OO-SSC

[JoystickCalibration.Airbus]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
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
Aileron=-16380,-512,46,16380
SlopeAileron=2
Elevator=-16380,-13,512,16380
SlopeElevator=2
Rudder=-16380,0,512,16380
SlopeRudder=15
SteeringTiller=-16380,-512,512,16380
SlopeSteeringTiller=11

[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight X-55 Rhino Throttle
0.GUID={30691CB0-9A59-11E5-8001-444553540000}
1=Saitek Pro Flight X-55 Rhino Stick
1.GUID={30691CB0-9A59-11E5-8003-444553540000}

[General]
UpdatedByVersion=4948
History=XNKJNQL08TSW4YALWNH2W
InitDelayDevicesToo=No
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
DeleteVehiclesForAES=Yes
AutoScanDevices=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=No
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=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=No
OOMcheck=Yes
OOMcheckInterval=10
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
AssignJoystickIDs=Yes
FSVersionUsed="Lockheed Martin® Prepar3D® v3",3.0.3.0
SimConnectUsed=3.0.0.0

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=F:\Prepar3D v3\Sound\
Device1=Primary Sound Driver
Device2=Speakers (2- Logitech USB Headset)
Device3=Speakers (Realtek High Definition Audio)

Kind Regards,

Vital Vanbeginne

[Pete Dowson]

I restored the fsuipc.ini version from my "pre-restaging" Prepar3d v3 with all its configs and settings like I want.

 

Now, my throttle is being treated as if it was the stick and the stick as if it was the throttle.

 

I had this also during my last reinstall over a year back, and managed to solve it back then. Unfortunatelly for me, I did not document this :(

I believe it had something to do with the [JoyNames] sections (swapping names and/or GUID's) but this time with no luck.

 

You aren't using Joy Letters, so FSUIPc is treating joystick #0 as #0 and #1 as #1. it has no choice. The joystick IDs are assigned by Windows at boot time and are liable to change if you reinstall Windows or unplug devices and plug them in again.

 

To get around this first edit this section:

 

[JoyNames]

AutoAssignLetters=No

0=Saitek Pro Flight X-55 Rhino Throttle

0.GUID={30691CB0-9A59-11E5-8001-444553540000}

1=Saitek Pro Flight X-55 Rhino Stick

1.GUID={30691CB0-9A59-11E5-8003-444553540000}

 

adding these extra 4 lines:

 

S=Saitek Pro Flight X-55 Rhino Throttle

S.GUID={30691CB0-9A59-11E5-8001-444553540000}

T=Saitek Pro Flight X-55 Rhino Stick

T.GUID={30691CB0-9A59-11E5-8003-444553540000}

 

I've chosen "S" for stick and "T" for throttle but assigned the other way around. I know they are wrong at the moment, but bear with me.

 

Now run FS. FSUIPC should now replace all assignments for 0 and 1 to assignments for S and T.

 

Close FS. Then edit those 4 lines to swap the S and T. i.e.

 

T=Saitek Pro Flight X-55 Rhino Throttle

T.GUID={30691CB0-9A59-11E5-8001-444553540000}

S=Saitek Pro Flight X-55 Rhino Stick

S.GUID={30691CB0-9A59-11E5-8003-444553540000}

 

Next time you run FS it should all be as you intended, and will stay okay over further reinstalls or unpluggings.

 

Pete

[hydbyr]

I am having a similar problem - I think!  In FSX, no matter how I work on assigning buttons/axes to a Thrustmaster Warthog throttle and joystick w/ CH pedals, the left and right brakes on the pedals actuate the elevator axis and the aileron axis in addition to their assignments as brakes (for all aircraft - this makes it tough to fly!!).  In addition, the trim functions cannot be assigned to what is normally the POV hat.  The trim functions used to work as trim in FSX especially with TrackIR working.  Is there a way to see what controller assignments are in force using FSUIPC?  Would they show up in FSX.cfg?  Prior to the re-install, I erased FSX.cfg and re-ran FSX - still no luck. 

 

I have uninstalled and re-installed FSX gold with a clean re-install. The controls used to work just fine in FSX.  In fact, they work as they always have in DCSWorld.  The clean install should have started a new FSX.cfg - I think. 

[Pete Dowson]

In FSX, no matter how I work on assigning buttons/axes to a Thrustmaster Warthog throttle and joystick w/ CH pedals, the left and right brakes on the pedals actuate the elevator axis and the aileron axis in addition to their assignments as brakes (for all aircraft - this makes it tough to fly!!).

 

You must NOT have controllers enabled in FS if you are assigning in FSUIPC. You evidently have dual conflicting assignments. Either assign in FSUIPC or in FS, not both.

 

 

In addition, the trim functions cannot be assigned to what is normally the POV hat.

 

In FSUIPC a POV hat can be treated as a set of 4 or 8 buttons (according to the device) and you can assign two of those to the elevator trim up and down controls in the drop-down assignments list.

 

Is there a way to see what controller assignments are in force using FSUIPC?

 

Those assigned in FSUIPC will show in the axes tab (or buttons & switches for buttons) when you move/press them. FSUIPC cannot show you what you've assigned in FS -- use FSUIPC or FS, not both!

 

Would they show up in FSX.cfg?  Prior to the re-install, I erased FSX.cfg and re-ran FSX - still no luck. 

 

 

FS assignments are NOT stored in the FSX.CFG file. Just go into FS options/ controls and make sure controllers are disabled.

 

Pete