FSUIPC Button assignment not working for all devices

[pesz]

Hi,

Can someone share the FSX/P3D Saitek plugin, please?
Drivers section seems to be empty.

Fighting with X-56 Stick for 5 hrs now AGAIN. Looks ok when I thick "enable controller" in the P3D's settings, but it doesn't work with FSUIPC without any known reason :( 

Thanks in advance.

[pacebl]

Hi, I think it's completely ridiculous that Saitek doesn't seem to even offer their drivers for download anymore. I happen to still have these files in my downloads folder, but I don't seem to have the "Saitek FSX Plugin" anymore. These are also for the X-55, but the X-56 seems very similar, I hope they work for you.

 

https://www.dropbox.com/s/oejhj6102w87yud/X55_Rhino_7_0_55_13_x64_Drivers.exe?dl=0

 

https://www.dropbox.com/s/4ohgz3bcwqq4pu8/X55_Rhino_7_0_55_13_x64_Software.exe?dl=0

[pesz]

There is a download section on the Logitech website but it is only a driver and a profile pack available for download, no FSX Plugin I'm afraid.

Thanks anyway for your help mate.

[Pete Dowson]

19 minutes ago, pesz said:

Fighting with X-56 Stick for 5 hrs now AGAIN. Looks ok when I thick "enable controller" in the P3D's settings, but it doesn't work with FSUIPC without any known reason :( 

Problems with the X-55 and X-56 series were fixed several FSUIPC releases ago, and certainly in the current versions, 5.112 or 4.971, which are the curren supported versions. What version are you using?

Generally everything works best if there is NO Saitek software running at all.  Best to uninstall it, then uninstall both X-56 units in Windows Device Manager -- including drivers when the option is offered -- then re-boot and let windows sort it out.

Pete

 

[pesz]

32 minutes ago, Pete Dowson said:

Problems with the X-55 and X-56 series were fixed several FSUIPC releases ago, and certainly in the current versions, 5.112 or 4.971, which are the curren supported versions. What version are you using.

Generally everything works best if there is NO Saitek software running at all.  Best to uninstall it, then uninstall both X-56 units in Windows Device Manager -- including drivers when the option is offered -- then re-boot and let windows sort it out.

Pete

 

I didn't use P3D for couple of months. I just realised the only one thing I did not update was FSUIPC. Everything's working well now.

Thanks Pete and sorry for this confusion.

Piotr.

[Albert Szmidt]

On ‎1‎/‎22‎/‎2017 at 8:17 PM, pacebl said:

I might have fixed it. If it is a hardware issue, it magically started working again. If it isn't a hardware issue, installing the FSX Saitek Plugin seems to have fixed it. I also installed the programming software and it seems to be working fine with that + the driver + the plugin installed.

http://www.saitek.com/uk/down/drivers.php The link to the plugin is at the bottom of the page, if anyone else has an X-55, this might fix it.

Where can I get drivers for x56?

[Albert Szmidt]

On ‎8‎/‎18‎/‎2017 at 6:47 PM, Pete Dowson said:

Problems with the X-55 and X-56 series were fixed several FSUIPC releases ago, and certainly in the current versions, 5.112 or 4.971, which are the curren supported versions. What version are you using?

Generally everything works best if there is NO Saitek software running at all.  Best to uninstall it, then uninstall both X-56 units in Windows Device Manager -- including drivers when the option is offered -- then re-boot and let windows sort it out.

Pete

 

I unistalled all saitek software again, i have removed x56 units from windows device manager- but still axis x and y on the stick are not visible for fsuipc5- Please help

[Pete Dowson]

On 10/10/2018 at 8:43 PM, Albert Szmidt said:

I unistalled all saitek software again, i have removed x56 units from windows device manager- but still axis x and y on the stick are not visible for fsuipc5- Please help

When uninstalling in the device manager did you confirm to remove drivers too? That means any Windows drivers, and also removes entried from the Registry. It is that last part which is important, as the Saitek installers seem to often screwe the registry entries up, and uninstalling just the Saitek software doesn't appear to correct them.

Don't forget to re-boot after ininstalling. Re-connect the device just befor re-boothing or soon after.

Pete

 

[kdavis30]

Good morning,

I setup the new Honeycomb Alpha controls exclusively with FSUIPC, but I'm still having a problem.  I tried assigning the left trigger (button pressed with middle finger) for the Parking Brake command in P3d, but for some reason, it has both the parking brake and the regular brakes mapped to that button.  I disabled controllers in P3d's settings, so I'd think FSUIPC would have full control of the joystick.  If this thread is too old, I can certainly create a new topic.  Any help you can provide is appreciated. 

Regards,

Kevin Davis

[John Dowson]

Hi Kevin,

could you please attach your FSUIPC .ini file together with your .log file and I'll take a look.

Cheers,

John

[kdavis30]

21 hours ago, John Dowson said:

Hi John, 

Attached are copies of the FSUIPC.ini & .log files.  

INI: 

[General]
UpdatedByVersion=5152
History=1T7K4KE39M4OMKN7BB4P6
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
TrafficStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
ComReadLoopTime=20
ControlsListBuild=30293
ProvideAIdata=Yes
ProvideAIairports=Yes
Console=No
InitDelayDevicesToo=No
PMDG737offsets=Auto
PMDG747offsets=Auto
PMDG777offsets=Auto
Annotate=Yes
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
RestoreSimcWindows=No
FixMachSpeedBug=No
AutoScanDevices=Yes
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
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=Yes
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
TextFileMaxRead=4095
TextFileNumbers=Yes
TextFilePhonetics=Yes
OptionsDialogOffset=-42, 232
FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.5.12.30293
SimConnectUsed=4.5.0.0

[WideServer]
WideFSenabled=Yes

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

[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight Quadrant
0.GUID={CC7245B0-705A-11EA-8001-444553540000}
1=Alpha Flight Controls
1.GUID={19035B90-752D-11EA-8001-444553540000}

[JoystickCalibration]
RudderBlendLowest=1
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=No
ExcludeMixtureSet=No
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
Throttle1=-16380,-512,512,16380/32
SlopeThrottle1=-4
Throttle2=-16380,-512,512,16380/32
Elevator=-16380,-512,512,16380
SlopeThrottle2=-4
Spoilers=-16380,16380/16
SlopeSpoilers=-4
Aileron=-16380,-512,512,16380

[Axes]
PollInterval=10
RangeRepeatRate=10
0=0X,256,F,65820,0,0,0    -{ TO SIM: THROTTLE1_SET }-
1=0Y,256,F,65820,65767,65773,0    -{ TO SIM: THROTTLE1_SET, PROP_PITCH_SET, MIXTURE_SET }-
2=0Z,256,F,65773,0,0,0    -{ TO SIM: MIXTURE_SET }-
3=1X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
4=1Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
5=1Z,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
6=1U,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
7=1V,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
8=1P,0,F,66416,0,0,0    -{ TO SIM: PAN_VIEW }-

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=P1,13,C65861,0     -{AUTO_THROTTLE_TO_GA}-
2=R1,0,C65752,0     -{PARKING_BRAKES}-
3=P1,34,C66416,0     -{PAN_VIEW}-
4=P1,7,C65908,0     -{PANEL_3}-
7=P1,6,K192,8     -{Key press: '@key}-
8=U1,6,K192,8     -{Key press: '@key}-
9=U1,7,C65908,0     -{PANEL_3}-

[AutoSave]
Next=6
Interval=60
Files=10
SaveOnGround=Yes
AutoSaveEnabled=Yes
1=Mon 094626
2=Mon 094725
3=Mon 094825
4=Mon 094924
5=Mon 095024
6=Mon 094128
7=Mon 094228
8=Mon 094327
9=Mon 094427
10=Mon 094526

[GPSout]
GPSoutEnabled=No
Port=COM1
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=

[GPSout2]
GPSoutEnabled=No
Port=<none set>
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=

[Sounds]
Path=C:\Program Files\Lockheed Martin\Prepar3D v4\Sound\
Device1=Primary Sound Driver
Device2=Headset Earphone (Corsair VOID RGB Wireless Gaming Headset)
Device3=LG ULTRAWIDE (NVIDIA High Definition Audio)
Device4=Headset Earphone (2- Corsair VOID RGB Wireless Gaming Headset)
Device5=PXL2230MW (NVIDIA High Definition Audio)
Device6=Headset Earphone (4- Corsair VOID RGB Wireless Gaming Headset)

[Profile.737NGX]
1=Boeing 737-8D6NGX Air Algerie (OC)

[Buttons.737NGX]
0=P1,13,C65861,0     -{AUTO_THROTTLE_TO_GA}-

[Window.SimConnectWindow]
Undocked=1021, 519, 656, 293
 

Log: 

********* FSUIPC5, Version 5.152 (24th July 2019) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FFEC4970000
Windows 10 Home 64 Bit reported as Build 18363, Release ID: 1909 (OS 10.0)
Prepar3D.exe version = 4.5.12.30293
Reading options from "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="Kevin Davis"
User Addr="kevinmdavis2010@gmail.com"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 06/04/2020 08:05:53
        0 FLT path = "C:\Users\yokev\Documents\Prepar3D v4 Files\"
        0 Using DialogMode
        0 FS path = "C:\Program Files\Lockheed Martin\Prepar3D v4\"
       78 ---------------------- Joystick Device Scan -----------------------
      187 Product= Saitek Pro Flight Quadrant
      187    Manufacturer= Saitek
      187    Vendor=06A3, Product=0C2D (Version 2.2)
      187    GUIDs returned for product: VID_06A3&PID_0C2D:
      187       GUID= {CC7245B0-705A-11EA-8001-444553540000}
      187       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      187 Product= Alpha Flight Controls
      187    Manufacturer= Honeycomb Aeronautical
      187    Serial Number= A3BB380309203B00
      187    Vendor=294B, Product=1900 (Version 0.16)
      187    GUIDs returned for product: VID_294B&PID_1900:
      187       GUID= {19035B90-752D-11EA-8001-444553540000}
      187       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0
      187 -------------------------------------------------------------------
      187 Device acquired for use:
      187    Joystick ID = 0 (Registry okay)
      187    0=Saitek Pro Flight Quadrant
      187    0.GUID={CC7245B0-705A-11EA-8001-444553540000}
      187 Device acquired for use:
      187    Joystick ID = 1 (Registry okay)
      187    1=Alpha Flight Controls
      187    1.GUID={19035B90-752D-11EA-8001-444553540000}
      187 -------------------------------------------------------------------
      203 LogOptions=00000000 00000001
      203 -------------------------------------------------------------------
      203 SimConnect_Open succeeded: waiting to check version okay
      203 Opened separate AI Traffic client okay
    21312 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.12.30293 (SimConnect: 4.5.0.0)
    21312 Initialising SimConnect data requests now
    21312 FSUIPC Menu entry added
    21328 ... Using Prepar3D with Professional License
    21344 C:\Users\yokev\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
    21344 C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
  2167875 Weather Mode now = Theme
  2171203 Weather Mode now = Global
  2248094 C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\PMDG 737-800NGXu SSW\B737-800 SSW.air
  2248094 PMDG 737 offsets enabled
  2248125 ### The user object is 'PMDG 737-800NGXu PMDG House Split Scimitar Winglets (N738SW | 2019)'
  2248125 ### Mode is NORMAL
  2248922 ### Mode: PAUSE on
  2256562 Loading Complete ...
  2256578 ### Mode is NORMAL
  2257344 User Aircraft ID 2 supplied, now being used
  2257344 Aircraft loaded: running normally now ...
  2257515 System time = 06/04/2020 08:43:31, Simulator time = 09:18:08 (13:18Z)
  2257515 Aircraft="PMDG 737-800NGXu PMDG House Split Scimitar Winglets (N738SW | 2019)"
  2264672 Weather Mode now = Theme
  2265031 -------------------- Starting everything now ----------------------
  2265078 ASN active function link set
  2265078 Ready for ActiveSky WX radar with additional data
  2266281 Advanced Weather Interface Enabled
  3186125 Requested flightplan loading: "C:\Users\yokev\Documents\Prepar3D v4 Files\CYYZ_CYHU_P2AFPL.pln"
  3186140 Planned flight from CYYZ to CYHU
  3186140 C:\Users\yokev\Documents\Prepar3D v4 Files\CYYZ_CYHU_P2AFPL.pln
  3186140 C:\Users\yokev\Documents\Prepar3D v4 Files\CYYZ_CYHU_P2AFPL.pln
  4862047 ### Mode: FREEZE_ATT on FREEZE_ALT on FREEZE_LATLON on
  5283953 ### Mode is NORMAL
  6301531 ### Mode: PAUSE on
I hope this helps.  

Regards, 

Kevin Davis 

Hi Kevin,

could you please attach your FSUIPC .ini file together with your .log file and I'll take a look.

Cheers,

John

 

[John Dowson]

First, you are using an older unsupported version of FSUIPC - can you please update to the latest release, which is 5.155.

Could you please do this and resend your log file (this will also tell me the state of your controllers in P3D).

You only have parking brakes assigned (to repeat of button 0 on your yoke,  which I presume is the left trigger that you mentioned), and no assignments to differential brakes. You could also try activating  logging for Events (non-axis controls) and Button and key operations (from the FSUIPC logging tab) and activate the parking brake to see what is logged. You could also try logging Axis controls to see if the differential brakes are assigned to an axis somewhere. Try not to move your other axis while logging this. Please post again and attach the generated log file with this info.

Maybe also try with a default aircraft rather than the PMDG 737 NGXu that you are currently using.

Cheers,

John

Edited April 7, 2020 by John Dowson
button on repeat not release

[John Dowson]

Just noticed that your parking break is assigned as a repeat (not a release!) - try changing this to a simple press (so you click once to activate, then again to release) - I corrected my previous post.

 

[John Dowson]

By the way, how are you detecting that the normal/toe brakes are applied? Are you seeing any messages from P3D (or via offsets)? Engaging the parking brake will set and lock the normal brakes. I think you just need to take the "repeat" off of your parking brake assignment.

John

[kdavis30]

Hi John, 

I took "Repeat" off of the parking brake setting, but now the parking brake command doesn't work at all.  I know that the toe breaks are applied because the red indicator on the bottom left of the screen says brakes when I press the trigger.  I hope this makes sense.   

Regards, 

Kevin Davis 

[John Dowson]

Hi Kevin,

could you attach your ini file please.

John