Jump to content
The simFlight Network Forums

Please HELP! Strange Joystick Assignment

ansontz
 Share

Recommended Posts

ansontz Newbie

ansontz

Posted
Posted

Hi all,

I have assigned axes, button and switches for my X55 throttle using FSUIPC with letters (R, S and T), and it worked perfectly. Today it just suddenly doesn't give any response when I move it.

Then I went back to FSUIPC axes assignment page, the throttle was recognised as device #4 when moved but all my previous set settings are lost. Interestingly, there were two throttles recognised and shown in FSUIPC.ini but I have one throttle only.

If you read my FSUIPC.ini below, you should know that I have assigned some axes, buttons and switches for the throttle, like 

2=PT,1,K66,8 	-{Key press: B}-

then this assignment should link to joyname "T" (my throttle) and T represents either {68B2A600-D4E0-11E6-8008-444553540000} or {68B60160-D4E0-11E6-800D-444553540000} (as I mentioned there are two throttle displayed in [joyname] section which I don't know why). but nothing works.

I have disabled windows 10 power suspension option in both device manager and power option under control panel.

Thanks.

Anson 

[General]
UpdatedByVersion=4959
History=HDOY2J65NEY85N99SC5QI
InitDelayDevicesToo=No
Annotate=Yes
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
NewDeleteVehiclesForAES=No
AutoScanDevices=Yes
AssignJoystickIDs=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
WideLuaGlobals=Yes
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
OOMcheck=Yes
OOMcheckInterval=10
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
FSVersionUsed="Lockheed Martin® Prepar3D® v3",3.3.3.3
SimConnectUsed=3.3.0.0

[JoyNames]
AutoAssignLetters=No
R=Mad Catz Pro Flight Rudder Pedals
R.GUID={68A93020-D4E0-11E6-8002-444553540000}
S=Saitek Pro Flight X-55 Rhino Stick
S.GUID={68B56520-D4E0-11E6-800A-444553540000}
T=Saitek Pro Flight X-55 Rhino Throttle
T.GUID={68B2A600-D4E0-11E6-8008-444553540000}
T=Saitek Pro Flight X-55 Rhino Throttle
T.GUID={68B60160-D4E0-11E6-800D-444553540000}
0=Mad Catz Pro Flight Rudder Pedals
0.GUID={68A93020-D4E0-11E6-8002-444553540000}
1=Saitek Pro Flight X-55 Rhino Stick
1.GUID={68B56520-D4E0-11E6-800A-444553540000}
3=Saitek Pro Flight X-55 Rhino Throttle
3.GUID={68B2A600-D4E0-11E6-8008-444553540000}
4=Saitek Pro Flight X-55 Rhino Throttle
4.GUID={68B60160-D4E0-11E6-800D-444553540000}

[Axes]
PollInterval=10
RangeRepeatRate=10

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=HS,3,K80,8 	-{Key press: P}-
2=PT,1,K66,8 	-{Key press: B}-
3=PT,28,C65759,0 	-{FLAPS_DECR}-
4=PT,27,C65758,0 	-{FLAPS_INCR}-
5=PT,5,K112,8 	-{Key press: F1}-
6=RT,6,K113,8 	-{Key press: F2}-
7=PS,6,C66079,0 	-{GEAR_UP}-
8=PS,8,C66080,0 	-{GEAR_DOWN}-
9=PS,5,K190,10 	-{Key press: ctl+.>key}-
10=PT,29,C65607,0 	-{ELEV_TRIM_DN}-
11=PT,30,C65615,0 	-{ELEV_TRIM_UP}-
12=PT,4,K71,11 	-{Key press: ctl+shft+G}-
13=PT,3,K82,11 	-{Key press: ctl+shft+R}-
14=PT,0,K90,11 	-{Key press: ctl+shft+Z}-
15=PS,1,K90,11 	-{Key press: ctl+shft+Z}-
16=PS,2,K90,8 	-{Key press: Z}-

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

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[Traffic Limiter]
TrafficLimit=0
AirportPreference=50
GroundPreference=50
NearerPreference=50

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Sound\
Device1=Primary Sound Driver
Device2=Speakers (2- High Definition Audio Device)
Device3=Speakers (Rapoo Wireless Audio)
Device4=Digital Audio (S/PDIF) (2- High Definition Audio Device)
Device5=C24F390 (High Definition Audio Device)

[Profile.PMDG 777]
1=PMDG 777-367/ER Cathay Pacific 'New Livery' B-KPQ
2=PMDG 777-367ER Cathay Pacific Airways
3=PMDG 777-381ER All Nippon Airways
4=PMDG 777-35EER EVA Air

[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
LeftBrake=-16380,16380/16
RightBrake=-16380,16380/16

[Axes.PMDG 777]
RangeRepeatRate=10
0=RX,256,D,7,0,0,0	-{ DIRECT: LeftBrake }-
1=RY,256,D,8,0,0,0	-{ DIRECT: RightBrake }-
2=RR,256,D,3,0,0,0	-{ DIRECT: Rudder }-
3=SX,256,D,1,0,0,0	-{ DIRECT: Aileron }-
4=SY,256,D,2,0,0,0	-{ DIRECT: Elevator }-
5=SR,256,D,3,0,0,0	-{ DIRECT: Rudder }-
6=TX,256,D,9,0,0,0	-{ DIRECT: Throttle1 }-
7=TY,256,D,10,0,0,0	-{ DIRECT: Throttle2 }-
8=TU,256,D,22,0,0,0	-{ DIRECT: Spoilers }-

 

Pete Dowson Rising Star

Pete Dowson

Posted
Posted
2 hours ago, ansontz said:

this assignment should link to joyname "T" (my throttle) and T represents either {68B2A600-D4E0-11E6-8008-444553540000} or {68B60160-D4E0-11E6-800D-444553540000} (as I mentioned there are two throttle displayed in [joyname] section which I don't know why). but nothing works.

If this occurred after an update to a recent FSUIPC version, then it will be because a bug in the GUID checking has been corrected. In this, your JoyNames section: 

[JoyNames]
AutoAssignLetters=No
R=Mad Catz Pro Flight Rudder Pedals
R.GUID={68A93020-D4E0-11E6-8002-444553540000}
S=Saitek Pro Flight X-55 Rhino Stick
S.GUID={68B56520-D4E0-11E6-800A-444553540000}
T=Saitek Pro Flight X-55 Rhino Throttle
T.GUID={68B2A600-D4E0-11E6-8008-444553540000}
T=Saitek Pro Flight X-55 Rhino Throttle
T.GUID={68B60160-D4E0-11E6-800D-444553540000}
0=Mad Catz Pro Flight Rudder Pedals
0.GUID={68A93020-D4E0-11E6-8002-444553540000}
1=Saitek Pro Flight X-55 Rhino Stick
1.GUID={68B56520-D4E0-11E6-800A-444553540000}
3=Saitek Pro Flight X-55 Rhino Throttle
3.GUID={68B2A600-D4E0-11E6-8008-444553540000}
4=Saitek Pro Flight X-55 Rhino Throttle
4.GUID={68B60160-D4E0-11E6-800D-444553540000}

I don't know how you got two throttles registered with different GUIDs -- update to Windows perhaps? Before I corrected the GUID checking you were just lucky that the right device was selected.

Try changing the second "T" pair to be "U" instead of T. Then see whether you get T or U showing in the Axis assignments tab. If T then delete the U and 4 lines. If U then delete the T and 3 lines and change the two U's to T's.

Pete

 

ansontz Newbie

ansontz

Posted
  • Author
Posted
6 hours ago, Pete Dowson said:

If this occurred after an update to a recent FSUIPC version, then it will be because a bug in the GUID checking has been corrected. In this, your JoyNames section: 


[JoyNames]
AutoAssignLetters=No
R=Mad Catz Pro Flight Rudder Pedals
R.GUID={68A93020-D4E0-11E6-8002-444553540000}
S=Saitek Pro Flight X-55 Rhino Stick
S.GUID={68B56520-D4E0-11E6-800A-444553540000}
T=Saitek Pro Flight X-55 Rhino Throttle
T.GUID={68B2A600-D4E0-11E6-8008-444553540000}
T=Saitek Pro Flight X-55 Rhino Throttle
T.GUID={68B60160-D4E0-11E6-800D-444553540000}
0=Mad Catz Pro Flight Rudder Pedals
0.GUID={68A93020-D4E0-11E6-8002-444553540000}
1=Saitek Pro Flight X-55 Rhino Stick
1.GUID={68B56520-D4E0-11E6-800A-444553540000}
3=Saitek Pro Flight X-55 Rhino Throttle
3.GUID={68B2A600-D4E0-11E6-8008-444553540000}
4=Saitek Pro Flight X-55 Rhino Throttle
4.GUID={68B60160-D4E0-11E6-800D-444553540000}

I don't know how you got two throttles registered with different GUIDs -- update to Windows perhaps? Before I corrected the GUID checking you were just lucky that the right device was selected.

Try changing the second "T" pair to be "U" instead of T. Then see whether you get T or U showing in the Axis assignments tab. If T then delete the U and 4 lines. If U then delete the T and 3 lines and change the two U's to T's.

Pete

 

Will give it a try and report back here.

I have changed the order of my devices by JoyIds. But I think it should not be casuing any issue as all my devices work perfectly after the change until yesterday...

ansontz Newbie

ansontz

Posted
  • Author
Posted
22 hours ago, Pete Dowson said:

If this occurred after an update to a recent FSUIPC version, then it will be because a bug in the GUID checking has been corrected. In this, your JoyNames section: 


[JoyNames]
AutoAssignLetters=No
R=Mad Catz Pro Flight Rudder Pedals
R.GUID={68A93020-D4E0-11E6-8002-444553540000}
S=Saitek Pro Flight X-55 Rhino Stick
S.GUID={68B56520-D4E0-11E6-800A-444553540000}
T=Saitek Pro Flight X-55 Rhino Throttle
T.GUID={68B2A600-D4E0-11E6-8008-444553540000}
T=Saitek Pro Flight X-55 Rhino Throttle
T.GUID={68B60160-D4E0-11E6-800D-444553540000}
0=Mad Catz Pro Flight Rudder Pedals
0.GUID={68A93020-D4E0-11E6-8002-444553540000}
1=Saitek Pro Flight X-55 Rhino Stick
1.GUID={68B56520-D4E0-11E6-800A-444553540000}
3=Saitek Pro Flight X-55 Rhino Throttle
3.GUID={68B2A600-D4E0-11E6-8008-444553540000}
4=Saitek Pro Flight X-55 Rhino Throttle
4.GUID={68B60160-D4E0-11E6-800D-444553540000}

I don't know how you got two throttles registered with different GUIDs -- update to Windows perhaps? Before I corrected the GUID checking you were just lucky that the right device was selected.

Try changing the second "T" pair to be "U" instead of T. Then see whether you get T or U showing in the Axis assignments tab. If T then delete the U and 4 lines. If U then delete the T and 3 lines and change the two U's to T's.

Pete

 

Just tested on it and found that the throttle is detected as "U" after changing the second "T" pair to be "U" instead of T. Then I followed your advice to delete two lines of original "T" as well as all the lines with numbers (1 to 4), and changed the two U's to T's. Finally this is what after my edit: 

[JoyNames]
AutoAssignLetters=No
R=Mad Catz Pro Flight Rudder Pedals
R.GUID={68A93020-D4E0-11E6-8002-444553540000}
S=Saitek Pro Flight X-55 Rhino Stick
S.GUID={68B56520-D4E0-11E6-800A-444553540000}
T=Saitek Pro Flight X-55 Rhino Throttle
T.GUID={68B60160-D4E0-11E6-800D-444553540000}

However when I started the sim and enter FSUIPC page, the throttle was detected as #4 again! Here is what after I closed the sim: 

[JoyNames]
AutoAssignLetters=No
R=Mad Catz Pro Flight Rudder Pedals
R.GUID={68A93020-D4E0-11E6-8002-444553540000}
S=Saitek Pro Flight X-55 Rhino Stick
S.GUID={68B56520-D4E0-11E6-800A-444553540000}
T=Saitek Pro Flight X-55 Rhino Throttle
T.GUID={68B60160-D4E0-11E6-800D-444553540000}
0=Mad Catz Pro Flight Rudder Pedals
0.GUID={68A93020-D4E0-11E6-8002-444553540000}
1=Saitek Pro Flight X-55 Rhino Stick
1.GUID={68B56520-D4E0-11E6-800A-444553540000}
3=Saitek Pro Flight X-55 Rhino Throttle
3.GUID={68B2A600-D4E0-11E6-8008-444553540000}
4=Saitek Pro Flight X-55 Rhino Throttle
4.GUID={68B60160-D4E0-11E6-800D-444553540000}

I suspect that the change of device IDs of my throttle via JoyId makes two GUID entry. When FSUIPC scans joysticks/devices, it detects one throttle as two and makes my "T" not workable...I would be grateful if you could give me some insights into the problem.

ansontz Newbie

ansontz

Posted
  • Author
Posted 
[JoyNames]
AutoAssignLetters=No
R=Mad Catz Pro Flight Rudder Pedals
R.GUID={68A93020-D4E0-11E6-8002-444553540000}
S=Saitek Pro Flight X-55 Rhino Stick
S.GUID={68B56520-D4E0-11E6-800A-444553540000}
T=Saitek Pro Flight X-55 Rhino Throttle
T.GUID={68B60160-D4E0-11E6-800D-444553540000}
0=Mad Catz Pro Flight Rudder Pedals
0.GUID={68A93020-D4E0-11E6-8002-444553540000}
1=Saitek Pro Flight X-55 Rhino Stick
1.GUID={68B56520-D4E0-11E6-800A-444553540000}
4=Saitek Pro Flight X-55 Rhino Throttle
4.GUID={68B60160-D4E0-11E6-800D-444553540000}

I tried this. The throttle was detected as #4 but NOT T. It was so strange because T and 4 have the same GUID...

Pete Dowson Rising Star

Pete Dowson

Posted
Posted
54 minutes ago, ansontz said:

I tried this. The throttle was detected as #4 but NOT T. It was so strange because T and 4 have the same GUID...

Yes That makes no sense at all.

Two more things to try:

1. Remove both T lines, and change AutoAssignLetters back to "Yes". Runthe sim, and it will probably assign letter A and that should show as A in the assignments tab. If so, change both A's to T's and see if that fixes it.

If not:

2. Go to the Windows Device Manager, in the Control Panel, and sselecting the throttle and fully uninstalling it there. Both of them if it lists two. Then re-boot the system.

Failing that I think it'll be a matter of searching the registry for any mention of "Rhino Throttle" and deleting the entries for it.

Pete

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • 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.