FUSIPC can't set up my Saitek Controller

Raffaele Radice · February 8, 2015

Hi everyone.

I am trying to setup my Saitek Controller via FSUIPC to fix (I hope) the problem regarding the fact that FSX lost them under Windows 8.1 SO... I think a lot of you knows this....

I have SAITEK X52, Saitek Pro Flight and Rudder.

I have read that it's possible to configure them via FSUIPC but only with the full version. So today I bought it.

I am happy because I know FSUICP.

Nevertheless, I can't setup them even if I have read the guide and watched a video tutorial on youtube https://www.youtube.com/watch?v=TkOg-r_MKwM

In my case, when I enter in the BUTTONS + SWITCHES area I can do nothing even if I press the button on the X52 I wish to set up. I can't thick SELECT FOR FS CONTROL and so on....

What can I do? Is there something I wrong I guess... because everyone is enthusiastic about this interface.

Can anyone help me? I do really appreciate.

Raffaele

Pete Dowson · February 9, 2015

In my case, when I enter in the BUTTONS + SWITCHES area I can do nothing even if I press the button on the X52 I wish to set up. I can't thick SELECT FOR FS CONTROL and so on....

What happens when you press your buttons, then? Sorry, you'll need to describe what you see.

Do you have some Saitek software interfering, maybe? Does FS see your buttons? Does Windows, for that matter?

FSUIPC doesn't do anything special for Saitek. It just reads buttons and axes off any normal joystick or hgame controller type device, using standard Windows facilities. Same as FSX in fact. If FSX "loses" joysticks I expect FSUIPC will too, as they are both trying to use the same Windows interface.

Pete

Raffaele Radice · February 9, 2015

Hi.

Thank you for your reply.

I see what you say....

Answering to your first question I could say: nothing.

When I press any button, nothing happens.... I just can calibrate them via FSUIPC but it is impossible for me to setup the various commands....

FSX sees the buttons and I suppose Windows as well.

I try to add an image to make you better understand.

Regarding the fact that Saitek Controller became unresponsive under W 8.1, a lot of people suggest to remove saitek drivers and install fsuipc and setup them...

Look here: http://www.flightsim.com/vbfs/showthread.php?218458-Saitek-Pro-Flight-Yoke-stops-responding

I believe you know it...

Anyway, I try to fix this wonderful problem.... hope to be able to learn how to setup commands via fsuipc....

Thanks again...

Raffaele

Pete Dowson · February 9, 2015

Answering to your first question I could say: nothing.

When I press any button, nothing happens.... I just can calibrate them via FSUIPC but it is impossible for me to setup the various commands....

You can't calibrate buttons. FSUIPC's calibration is for axis controls and works on the actual controls, not the inputs.

FSX sees the buttons and I suppose Windows as well.

I try to add an image to make you better understand.

No, I don't want an image. What button numbers are they in FSX? FSUIPC only supports buttons 0-31 (numbered 1-32 in FSX).

Regarding the fact that Saitek Controller became unresponsive under W 8.1, a lot of people suggest to remove saitek drivers and install fsuipc and setup them...

Look here: http://www.flightsim...tops-responding

I believe you know it...

I know people SAY that. I've never said it and every time folks say it here I tell them there is no reason I know of which would make it better in FSUIPC than in FSX itself, as both use the same methods. The only advantage FSUIPC has is that it does see disconnections and reconnections of USB devices -- with FSX you normally have to restart it to see a newly added device. FSUIPC sees them when it scans on entry to the relevant option tabs.

Pete

Raffaele Radice · February 9, 2015

You can't calibrate buttons. FSUIPC's calibration is for axis controls and works on the actual controls, not the inputs.

Yes, I knew that. My poor english. I meant I just can calibrate the three Saitek devices not the buttons, sure....

No, I don't want an image. What button numbers are they in FSX? FSUIPC only supports buttons 0-31 (numbered 1-32 in FSX).

I just try with the button number 1. It's the red button just behind the first cloche on the left normally used to apply and release the brake. It's a default button.

I press it via FSUIPC and nothing happens even if I know it works.

I disabled the three devices via FSX and tried to program them via FSUIPC but nothing to do....

I know people SAY that. I've never said it and every time folks say it here I tell them there is no reason I know of which would make it better in FSUIPC than in FSX itself, as both use the same methods. The only advantage FSUIPC has is that it does see disconnections and reconnections of USB devices -- with FSX you normally have to restart it to see a newly added device. FSUIPC sees them when it scans on entry to the relevant option tabs.

I got it....

Pete

Pete Dowson · February 9, 2015

Please don't put your replies inside quotes from me. It makes it very hard to answer back properly!

I just try with the button number 1. It's the red button just behind the first cloche on the left normally used to apply and release the brake. It's a default button.

In FSX assignments do you see it actually recognised as button 1? Have you actually used FSX to assign to any of the butons or just left all to default? Are you sure there's no Saitek program running which is sending stuff to FSX. It does sound like something else is reading the buttons first and interpreting them.

Otherwise it is very strange. Maybe it's the Win8 problem attacking!?

Some special logging might help. Please edit the FSUIPC4.INI file (in the FS Modules folder, adding these lines to the [General] section:

Debug=Please

LogExtras=x200008

Then run FSX, Enable Axis and Button logging in FSUIPC's logging tab, then go and press some of those buttons. Close FSX.

Then I need to see the FSUIPC4.INI and FSUIPC4.LOG files, please. You can paaste ther contents into a message here.Use the <> button above the edit area here to enclose the texts.

Pete

Raffaele Radice · February 9, 2015

Ok Thank you for your support... This is really strange. I do not have any Saitek Program running and also FSX doesn't apply the funciotn assigns to the buttons evenf if it is assigned correctly.... I can't understand now.

Also, I can calibrate them via FSX because it's like the three devices doesn't exist.

Anyway this the log you ask for...

********* FSUIPC4, Version 4.938f by Pete Dowson *********
Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"
Running inside FSX on Windows 8
Module base=568B0000
User Name="Raffaele Radice"
User Addr="radiceraffaele@gmail.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       32 System time = 09/02/2015 22:44:41
       32 FLT path = "C:\Users\Utente\Documents\File di Flight Simulator X\"
       63 Trying to connect to SimConnect Acc/SP2 Oct07 ...
       79 FS path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"
      188 #### Initialising Dlrectinput Axis Scanning ...
      188    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"
      188    Found correct joystick Id 0
      188    ... and a "GUID" value
      188    DirectInput8Create failed, return = 80040154
      188    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_075C\Calibration\0"
      188    Found correct joystick Id 1
      188    ... and a "GUID" value
      188    DirectInput8Create failed, return = 80040154
      188    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0BAC\Calibration\0"
      188    Found correct joystick Id 2
      188    ... and a "GUID" value
      204    DirectInput8Create failed, return = 80040154
      204    joyGetDevCaps for device 3 returned error 165 [000000A5]
      204    joyGetDevCaps for device 4 returned error 165 [000000A5]
      204    joyGetDevCaps for device 5 returned error 165 [000000A5]
      204    joyGetDevCaps for device 6 returned error 165 [000000A5]
      204    joyGetDevCaps for device 7 returned error 165 [000000A5]
      204    joyGetDevCaps for device 8 returned error 165 [000000A5]
      204    joyGetDevCaps for device 9 returned error 165 [000000A5]
      204    joyGetDevCaps for device 10 returned error 165 [000000A5]
      204    joyGetDevCaps for device 11 returned error 165 [000000A5]
      204    joyGetDevCaps for device 12 returned error 165 [000000A5]
      204    joyGetDevCaps for device 13 returned error 165 [000000A5]
      204    joyGetDevCaps for device 14 returned error 165 [000000A5]
      204    joyGetDevCaps for device 15 returned error 165 [000000A5]
      204 #### Completed Dlrectinput Axis Scanning
      204 LogOptions=00000000 02000091
      204 SIM1 Frictions access gained
      204 Wind smoothing fix is fully installed
      204 G3D.DLL fix attempt installed ok
      204 SimConnect_Open succeeded: waiting to check version okay
      204 Trying to use SimConnect Acc/SP2 Oct07
     6000 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)
     6016 Initialising SimConnect data requests now
     6016 FSUIPC Menu entry added
     6032 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
     6032 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT
     6032 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
     6188 Memory in use: 687Mb, Avail=3409Mb
     6188 ###JOY### Event seen, ID=65763 (0x000100E3), Joy=0, value=0 
     6188 Axis calibration: Control=65763, Original=0, Calibrated=0
     6188 ###JOY### Event seen, ID=65762 (0x000100E2), Joy=1, value=0 
     6188 Axis calibration: Control=65762, Original=0, Calibrated=0
     6188 ###JOY### Event seen, ID=65765 (0x000100E5), Joy=3, value=-15558 
     6188 Axis calibration: Control=65765, Original=-15558, Calibrated=-15558
     6188 ###JOY### Event seen, ID=66291 (0x000102F3), Joy=4, value=-16256 
     6188 Axis calibration: Control=66291, Original=-16256, Calibrated=-16256
     6188 ###JOY### Event seen, ID=66292 (0x000102F4), Joy=5, value=-16256 
     6188 Axis calibration: Control=66292, Original=-16256, Calibrated=-16256
     6188 ###JOY### Event seen, ID=65763 (0x000100E3), Joy=0, value=0 
     6188 Axis calibration: Control=65763, Original=0, Calibrated=0
     6188 ###JOY### Event seen, ID=65762 (0x000100E2), Joy=1, value=0 
     6188 Axis calibration: Control=65762, Original=0, Calibrated=0
     6188 ###JOY### Event seen, ID=65765 (0x000100E5), Joy=3, value=-15621 
     6188 Axis calibration: Control=65765, Original=-15621, Calibrated=-15621
    50204 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    51188 System time = 09/02/2015 22:45:32, Simulator time = 12:07:24 (15:07Z)
    51188 Aircraft="Aircreation582SL red"
    62829 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
    71719 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR
    71844 Aircraft="Cessna Skyhawk 172SP Paint1"
    71922 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    72875 Memory in use: 1169Mb, Avail=2927Mb
    74641 Starting everything now ...
    74641 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
    76391 ASN active function link set
    76391 Ready for ASN WX radar
    77391 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
[Log closed by user request, and continued in new file]
   104860 System time = 09/02/2015 22:46:26, Simulator time = 12:07:34 (15:07Z)
   104860 *** FSUIPC log file being closed
Average frame rate for running time of 11 secs = 101.4 fps
G3D fix: Passes 11415, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 4 Allocs, 3 Freed
********* FSUIPC Log file closed ***********

And this is FSUIPC4.ini

[General]
UpdatedByVersion=4938f
History=D0L1L260QE6SADCXT7ZKS
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=No
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=Yes
OOMcheck=Yes
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
LuaRerunDelay=66
Console=No
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
Debug=Please
LogExtras=x200008
FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0
SimConnectUsed=10.0.61259.0
LogAxes=Yes
LogButtonsKeys=Yes


[JoyNames]
AutoAssignLetters=No
2=Saitek Pro Flight Yoke
2.GUID={9E00F2B0-8535-11E3-8009-444553540000}
0=Saitek Pro Flight Rudder Pedals
0.GUID={9E00CBA0-8535-11E3-8007-444553540000}
1=Saitek X52 Flight Controller
1.GUID={9E00CBA0-8535-11E3-8008-444553540000}

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Sound\
Device1=Driver audio principale
Device2=Altoparlanti (ASUS Xonar D2X Audio Device)
Device3=Altoparlanti (ASUS Xonar D2X Converter)
Device4=Altoparlanti (C-Media USB Headphone Set  )
Device5=S/PDIF Pass-through Device (ASUS Xonar D2X Audio Device)
Device6=AT2358MWL-4 (NVIDIA High Definition Audio)
Device7=Realtek Digital Output (Realtek High Definition Audio)

[Axes]
PollInterval=10
RangeRepeatRate=10

[Buttons]
PollInterval=25
ButtonRepeat=20,10

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

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

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

[Profile.Cub]
1=Piper Cub
2=Aircreation582SL red

[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

[Profile.Aerosoft Airbus A320X]
1=Airbus A320 Alitalia EI-DSA
[Profile.Cessna]
1=Cessna Skyhawk 172SP Paint1

Thank you again.

Hope we can find a solution

Raffaele

Pete Dowson · February 9, 2015

Ok Thank you for your support... This is really strange. I do not have any Saitek Program running and also FSX doesn't apply the funciotn assigns to the buttons evenf if it is assigned correctly.... I can't understand now.

Well, I have no idea what is wrong with your system, but the only clues I see are that th three devices Registered in Windows all return the same Error:

188 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"

188 Found correct joystick Id 0

188 ... and a "GUID" value

188 DirectInput8Create failed, return = 80040154

188 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_075C\Calibration\0"

188 Found correct joystick Id 1

188 ... and a "GUID" value

188 DirectInput8Create failed, return = 80040154

188 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0BAC\Calibration\0"

188 Found correct joystick Id 2

188 ... and a "GUID" value

204 DirectInput8Create failed, return = 80040154

The devices are identified because they are registered, as also shown in your FSUIPC4 INI file:

0=Saitek Pro Flight Rudder Pedals

0.GUID={9E00CBA0-8535-11E3-8007-444553540000}

1=Saitek X52 Flight Controller

1.GUID={9E00CBA0-8535-11E3-8008-444553540000}

2=Saitek Pro Flight Yoke

2.GUID={9E00F2B0-8535-11E3-8009-444553540000}

I tried Googling the error number, but didn't really find much of any use. One thing you could try is this "fix" by honestly I can't see how it is relevant:

http://www.microsoft.com/en-us/download/details.aspx?id=3988

Also, I can calibrate them via FSX because it's like the three devices doesn't exist.

When you say "can" do you mean "can't", otherwise that doesn't make sense?

So, it looks like there's something screwed up with the device installation.

Try uninstalling them in the Windows device manager unplug them first). Then re-booting and plugging them in again. If that doesn't work I think something is messed up in your Windows installation.

Pete

Raffaele Radice · February 10, 2015

Thank you Pete.

I see.... Yes I meant *can't calibrate....

This is really strange.... Even because I can fly and basically I do it almost every day.

When FSX lost my joysticks I simply run the procedure "Task Manager" clicking "CTRL+ALT+CANC" or "CTRL+ALT+DEL" in English I suppose, and FSX recognizes again magically the devices.....

I read this procedure googling my issue months ago...

Isn't it strange?

Anyway, I will try a complete re-installation as you suggest... It's a shame.... I would like to program them via FSUIPC.

Raffaele

mgh · February 10, 2015

This may be be relevant to Saitek controllers:

http://forum.simflight.com/topic/76089-directinput8create-failed-return-80040154/

Raffaele Radice · February 10, 2015

This may be be relevant to Saitek controllers:

http://forum.simflight.com/topic/76089-directinput8create-failed-return-80040154/

This is bad...

Raffaele Radice · February 11, 2015

Hi Pete. Hi everyone.

I found the way to connect FSUIPC with my three joysticks.

I erase a file DINPUT8.dll located in the main folder of FSX.

I put it months ago because it was reccomended for avoiding their lost inside FSX.

http://forum.avsim.net/topic/397127-lost-joystick-function-in-fsx/

Anyway I move this file and magically I could program my button, switches, axis and so on.....

WOW.... I will try to program FSUIPC properly studying it even if I know it's a little bit complicated.

I will keep you informed.

Raffaele

Pete Dowson · February 11, 2015

I found the way to connect FSUIPC with my three joysticks.

I erase a file DINPUT8.dll located in the main folder of FSX.

I put it months ago because it was reccomended for avoiding their lost inside FSX.

http://forum.avsim.net/topic/397127-lost-joystick-function-in-fsx/

Anyway I move this file and magically I could program my button, switches, axis and so on.....

Aha! I'll need to remember that for any future problems like this! Thanks for letting me know!

Pete

Sign In

FUSIPC can't set up my Saitek Controller

Recommended Posts

Raffaele Radice

Pete Dowson

Raffaele Radice

Pete Dowson

Raffaele Radice

Pete Dowson

Raffaele Radice

Pete Dowson

Raffaele Radice

mgh

Raffaele Radice

Raffaele Radice

Pete Dowson

Create an account or sign in to comment

Create an account

Sign in

Browse

Activity

Important Information