Jump to content
The simFlight Network Forums

Recommended Posts

Hello,

I've recently updated my Windows 7 Ultimate installation to Windows 10 Pro (using the upgrade functionality).

Since then, I have one major issue with my Saitek X-55 throttle and FSUIPC. The problem is that FSUIPC does not detect axis and button inputs from the throttle unit. This in both FSX and P3D. If I start the sim, open FSUIPC, and go the axis calibration tab, nothing happens when I move one of the axis. Same thing for buttons, on the respective tab.
The X-55 stick works fine though, it's just the throttle. Similarly, the throttle works perfectly if I don't use FSUIPC. It's detected in Windows, the calibration tool works, and it also works if I assign axis through FSX or P3D. As I said, the problem only seems to happen with FSUIPC.

I've tried:

1) reinstalling latest saitek drivers

2) completely uninstalling the X-55, restarting, then reinstalling, restarting again.

3) deleting the [JoyNames] section of the fsuipc.ini file

3) deleting fsuipc.ini file altogether

So far, no luck.
One thing I did notice that struck me as weird, (although I'm not sure) is that fsuipc.ini shows 2 entries for the X-55 rhino stick (the unit that works) and only one for the throttle (the one that doesn't). No idea why it shows 2 entries, and if it should or not.

(I also tried updating fsuipc to v4.951 after copying the below files. No difference)

My usual fsuipc.ini file, containing the options and edits I used successfully before moving to Windows 10:

Quote

[General]
UpdatedByVersion=4949h
History=ZNT39RM9SUUYYPNRKHBWV
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
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=Yes
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
AutoTuneADF=Yes
FSVersionUsed="Lockheed Martin® Prepar3D® v3",3.2.3.2
SimConnectUsed=3.2.0.0

[MacroFiles]
1=PMDG 737NGX

[JoyNames]
AutoAssignLetters=Yes
A=Saitek Pro Flight Combat Rudder Pedals
B=Saitek Pro Flight X-55 Rhino Stick
C=Saitek Pro Flight X-55 Rhino Throttle
D=Saitek Pro Flight Cessna Yoke
E=Logitech Extreme 3D
0=Saitek Pro Flight Combat Rudder Pedals
0.GUID={7785B0D0-F2DD-11E1-8007-444553540000}
1=Saitek Pro Flight X-55 Rhino Stick
1.GUID={63FB62E0-CA3A-11E3-8002-444553540000}
2=Saitek Pro Flight X-55 Rhino Stick
2.GUID={63FB62E0-CA3A-11E3-8001-444553540000}
3=Saitek Pro Flight X-55 Rhino Throttle
3.GUID={63FB62E0-CA3A-11E3-8003-444553540000}
F=Saitek Pro Flight X-55 Rhino Stick

[Axes]
PollInterval=10
RangeRepeatRate=10
5=DZ,256,F,65765,0,0,0
6=DU,256,F,66291,0,0,0
7=DV,256,F,66292,0,0,0
0=CX,256,F,66420,0,0,0
1=CY,256,F,66423,0,0,0
2=CZ,256,F,66291,0,0,0,*-1
3=CR,256,F,66382,0,0,0,*-1
4=CU,256,F,66292,0,0,0

[Buttons]
PollInterval=25
ButtonRepeat=20,10

[AutoSave]
Next=3
Interval=60
Files=5
SaveOnGround=No
AutoSaveEnabled=No
AlsoManage1=PMDG\PMDG 737 NGX\PanelState\*.fxml.0.rte
AlsoManage2=PMDG\PMDG 737 NGX\PanelState\*.fxml.fmc
AlsoManage3=PMDG\PMDG 737 NGX\PanelState\*.fxml.sav
AlsoManage4=D:\Users\Lars\Documents\Prepar3D v3 Files\*.asc
AlsoManage5=D:\Users\Lars\Documents\Prepar3D v3 Files\*.a2a
AlsoManage6=D:\Users\Lars\Documents\Prepar3D v3 Files\*.mj1
AlsoManage7=D:\Users\Lars\Documents\Prepar3D v3 Files\*.mj2
1=Mon 203114
2=Tue 234946
3=Mon 202510
4=Mon 202610
5=Mon 202709

[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=

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=D:\Perpar3Dv3\Sound\
Device1=Primary Sound Driver
Device2=Speakers (2- Realtek High Definition Audio)
Device3=Realtek Digital Output (2- Realtek High Definition Audio)
Device4=Realtek Digital Output(Optical) (2- Realtek High Definition Audio)
Device5=PHL 244E5-C (NVIDIA High Definition Audio)

[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
MapThr12to34=Yes
MapThr12to123=Yes
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
MapThr1to234=Yes
Throttle=-16380,16380

[Profile.Dodosim 206]
1=Dodosim 206 FSX GDDSM H
2=Dodosim 206 FSX GDODO F
3=Dodosim 206 FSX GDODO H
4=Dodosim 206 FSX GDDSM L

[Axes.Dodosim 206]
RangeRepeatRate=10
0=CX,256,F,65765,0,0,0
1=CY,256,F,66423,0,0,0
2=CZ,256,F,66291,0,0,0,*-1
3=CR,256,F,66382,0,0,0,*-1
4=CU,256,F,66292,0,0,0

[Window.LUA display]
Docked=7354, 2823, 3545, 775

[LuaFiles]
1=pa28
2=testfsi
3=Aerosoft_F14AB

[Window.VAFS Message:]
Docked=262, 2823, 3545, 1179

[Profile.Twin Engine Jet (No Props)]
1=Twin Engine Jet (No Props)

[Axes.Twin Engine Jet (No Props)]
RangeRepeatRate=10
0=DZ,256,F,66420,0,0,0
1=DU,256,F,66423,0,0,0
2=DV,256
3=DV,B,-16384,-9288,65778,0
4=DV,B,8256,16383,65774,0

[Profile.PMDG 737 NGX]
1=Boeing 737-800NGX Andras Meridian RTW Winglets (McPhat)
2=PMDG 737-800NGX PMDG House
3=PMDG 737-900NGX PMDG House
4=PMDG P-8A Poseidon
5=PMDG 737-800NGX Scandinavian

[Axes.PMDG 737 NGX]
RangeRepeatRate=10
0=DZ,256,F,66420,0,0,0
1=DU,256,F,66423,0,0,0
2=DV,256
3=DV,B,-16384,-9288,M1:1,0
4=DV,B,8256,16383,M1:2,0
5=DV,B,-16384,-9030,M1:3,0
6=DV,B,8385,16383,M1:4,0

 

The new autogenerated fsuipc.ini file:

Quote

[General]
Console=No
UpdatedByVersion=4949h
History=TX0WLZUGL2SE9QB644XIX
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
AssignJoystickIDs=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=No
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-1
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
FSVersionUsed="Lockheed Martin® Prepar3D® v3",3.2.3.2
SimConnectUsed=3.2.0.0
[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight Combat Rudder Pedals
0.GUID={7785B0D0-F2DD-11E1-8007-444553540000}
1=Saitek Pro Flight X-55 Rhino Stick
1.GUID={63FB62E0-CA3A-11E3-8002-444553540000}
2=Saitek Pro Flight X-55 Rhino Stick
2.GUID={63FB62E0-CA3A-11E3-8001-444553540000}
3=Saitek Pro Flight X-55 Rhino Throttle
3.GUID={63FB62E0-CA3A-11E3-8003-444553540000}
[Axes]
PollInterval=10
RangeRepeatRate=10
[Buttons]
PollInterval=25
ButtonRepeat=20,10
[MacroFiles]
1=PMDG 737NGX
[LuaFiles]
1=Aerosoft_F14AB
2=pa28
3=testfsi
[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No
[GPSout]
GPSoutEnabled=No
[GPSout2]
GPSoutEnabled=No
[WideServer]
WideFSenabled=Yes
[Sounds]
Path=D:\Perpar3Dv3\Sound\
Device1=Primary Sound Driver
Device2=Speakers (Realtek High Definition Audio)
Device3=Realtek Digital Output (Realtek High Definition Audio)
Device4=PHL 244E5-C (NVIDIA High Definition Audio)
Device5=Speakers (Logitech G330 Headset)
Device6=Realtek Digital Output(Optical) (Realtek High Definition Audio)

and the FSUIPC.log file from the last try:

Quote

********* FSUIPC4, Version 4.949h by Pete Dowson *********
Prepar3D.exe version = 3.2.3.16769
Reading options from "D:\Perpar3Dv3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0
Module base=52C40000
User Name="Lars Domen"
User Addr=    //removed for privacy reasons (public forum)
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       31 System time = 17/05/2016 15:06:27
       31 FLT path = "D:\Users\Lars\Documents\Prepar3D v3 Files\"
       31 ------ Module Version Check ------
       31        acontain.dll: 3.2.3.16769
       31             api.dll: 3.2.3.16769
       31        controls.dll: 3.2.3.16769
       31      fs-traffic.dll: 3.2.3.16769
       31             G3D.dll: 3.2.3.16769
       31        language.dll: 3.2.3.16769
       31            sim1.dll: 3.2.3.16769
       31        visualfx.dll: 3.2.3.16769
       31         weather.dll: 3.2.3.16769
       31          window.dll: 3.2.3.16769
       31 ----------------------------------
       31 Trying D:\Perpar3Dv3\Modules\SimConnectP3D2.dll
       47 Found it: trying to connect
       47 FS path = "D:\Perpar3Dv3\"
      453 ---------------------- Joystick Device Scan -----------------------
      453 Product= Saitek Pro Flight Combat Rudder Pedals
      453    Manufacturer= Saitek
      453    Vendor=06A3, Product=0764 (Version 2.1)
      453    Serial Number= Saitek
      453 Product= Saitek Pro Flight X-55 Rhino Stick
      453    Manufacturer= Madcatz
      453    Vendor=0738, Product=2215 (Version 0.86)
      453    Serial Number= G0000187
      453 Product= Saitek Pro Flight X-55 Rhino Throttle
      453    Manufacturer= Madcatz
      453    Vendor=0738, Product=A215 (Version 0.119)
      453    Serial Number= G0000223
      453 -------------------------------------------------------------------
      719 LogOptions=00000000 00000001
      719 -------------------------------------------------------------------
      719 ------ Setting the hooks and direct calls into the simulator ------
      719 --- CONTROLS timer memory location obtained ok
      719 --- SIM1 Frictions access gained
      719 --- FS Controls Table located ok
      719 --- Installed Mouse Macro hooks ok.
      719 --- Wind smoothing fix is installed
      719 --- All links okay (except older global weather setting method)
      719 -------------------------------------------------------------------
      719 SimConnect_Open succeeded: waiting to check version okay
      719 Trying to use SimConnect Prepar3D
    13781 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.2.3.2 (SimConnect: 3.2.0.0)
    13781 Initialising SimConnect data requests now
    13781 FSUIPC Menu entry added
    13812 D:\Users\Lars\Documents\Prepar3D v3 Files\EBOS.fxml
    13812 D:\Perpar3Dv3\SimObjects\Airplanes\Maule_M7_260C\Maule_M7_260C.air
    75187 System time = 17/05/2016 15:07:42, Simulator time = 15:06:40 (13:06Z)
    75375 Aircraft="Maule M7 260C paint3"
   130109 Starting everything now ...
   130203 ASN active function link set
   130203 Ready for ASN WX radar
   131297 Advanced Weather Interface Enabled

 

Any feedback would be very welcome. Would very much like to get this working as it should...

Thank you very much,

Lars
 

Share this post


Link to post
Share on other sites
32 minutes ago, Tyrion said:

Since then, I have one major issue with my Saitek X-55 throttle and FSUIPC. The problem is that FSUIPC does not detect axis and button inputs from the throttle unit. This in both FSX and P3D. If I start the sim, open FSUIPC, and go the axis calibration tab, nothing happens when I move one of the axis. Same thing for buttons, on the respective tab.
The X-55 stick works fine though, it's just the throttle. Similarly, the throttle works perfectly if I don't use FSUIPC. It's detected in Windows, the calibration tool works, and it also works if I assign axis through FSX or P3D. As I said, the problem only seems to happen with FSUIPC.

 

FSUIPC doesn't distinguish between different devices, once identified by ID or name, they are just devices. There's nothing to stop it detecting one and not another.

 

Quote

3) deleting the [JoyNames] section of the fsuipc.ini file

3) deleting fsuipc.ini file altogethe

 
That's rather a shame considering your assignments and the use of Joystick Letters to differentiate devices no matter how they connect.
 
The joysticks seem to be recognised okay. I take it the second INI file is the one after the move to Win10?  Comparing this section with your original, 
 
[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight Combat Rudder Pedals
0.GUID={7785B0D0-F2DD-11E1-8007-444553540000}
1=Saitek Pro Flight X-55 Rhino Stick
1.GUID={63FB62E0-CA3A-11E3-8002-444553540000}
2=Saitek Pro Flight X-55 Rhino Stick
2.GUID={63FB62E0-CA3A-11E3-8001-444553540000}
3=Saitek Pro Flight X-55 Rhino Throttle
3.GUID={63FB62E0-CA3A-11E3-8003-444553540000}

 
the ID assignments and the names/GUIDs are the same, so your orinial letter assignments should have worked okay. I would stick with your saved INI if I were you.
 
Quote

One thing I did notice that struck me as weird, (although I'm not sure) is that fsuipc.ini shows 2 entries for the X-55 rhino stick (the unit that works) and only one for the throttle (the one that doesn't). No idea why it shows 2 entries, and if it should or not.

If you only have one of then, then this shows a registry error, probably caused by the rather flakey and annoying Saitek installers. These seem to cause many problems.

The FSUIPC LOG, show only one stick detected. This scan actually scans the hardware, not just the Registry, but it cannot get the joystick IDs that way.
 
FSUIPC uses the same method of reading these devices as FS and P3D, the only thing difference is its reliance on the Windows-assigned ID numbers, so after restoring your INI I would try moving the throttle around, change its ID using the JoyIDs utility -- see the FAQ thread " Fixing joystick connections not seen by FSUIPC ".  You can probably just change the ID to a spare one then change it back. I think this helps by fixing the Registry entries which Saitek driver installation seems to muck up quite frequently! 
 
Whilst using JoyIDs see if you can also fix the duplicate entry for the Stick.
 
Pete
 
 
 
 
 

Share this post


Link to post
Share on other sites

Alright, now I feel stupid. ;)

Luckily, I was smart enough to make a backup of my 'working' fsuipc.ini file.

I tried the JoyIDs utility before, read the FAQ post...
However, before, I swapped id's just a couple of blank spaces below (which probably had something in them, although not showing, my not connected controllers probably).
This time, I just swapped with the very last id, got a confirmation message (hadn't seen that before!), and now it works...

Still not sure why it shows 2 X-55 sticks. I only have and have ever had a single one. Not too worried about that though, as long as everything works.

Sorry to have bothered you with this Pete. Thought I tried everything. Clearly haven't tried well enough.

Thank you very, very much...

Lars

Share this post


Link to post
Share on other sites
20 minutes ago, Tyrion said:

till not sure why it shows 2 X-55 sticks. I only have and have ever had a single one. Not too worried about that though, as long as everything works.

 

Does JoyIDs show the IDs of two X-55 sticks? If so, then it's probably some spurious registry entry. See if joyIDs lets you remove one -- but take care not to remove the real one! (Not sure if there is such a facility in JoyIDs, mind).

The only only thing you could try to correct that, if you feel inclined, would be to uninstall the stick -- both of them, if showing -- in the Windows Device Manager, including drivers, re-booting and reinstalling (if necessary -- Windows might pick it up anyway).

Pete

 

Share this post


Link to post
Share on other sites

Hey Pete,

Both JoyID and Windows only see the one stick...

The 'ghost' stick is not causing issues at the moment, so I'm just going to leave it be, instead of risking causing further problems.

Thanks again for your help!

Lars

Share this post


Link to post
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...

×
×
  • 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.