FSUIPC Saitek X56 Issue

[Albert Szmidt]

Still there is no change 😞 FSUIPC cannot see my stick axes

 

[Albert Szmidt]

[General]
Debug=Please
UpdatedByVersion=5140
History=1M6TNSQ1IYOCMZLMM82NY
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
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=Yes
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
ControlsListBuild=25520
Console=No
ConsoleWindow=78,78,1071,597
FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.3.29.25520
SimConnectUsed=4.3.0.0

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

[JoystickCalibration]
RudderBlendLowest=1
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,-512,512,16380
Rudder=-16380,-512,512,16380
Throttle=-16380,16380
Spoilers=-16380,16380
Flaps=0,16380
Reverser=-11263,16380/24

[Axes]
PollInterval=10
RangeRepeatRate=10
0=AP,0,D,35,0,0,0    -{ DIRECT: PanTilt }-
1=1R,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=1U,B,0,0,66992,0    -{ Entering=EYEPOINT_MOVE_VERTICAL }-
4=1U,B,0,0,66992,0    -{ Entering=EYEPOINT_MOVE_VERTICAL }-
5=1V,256
6=1V,B,0,0,66992,0    -{ Entering=EYEPOINT_MOVE_VERTICAL }-
7=1V,B,0,0,66992,0    -{ Entering=EYEPOINT_MOVE_VERTICAL }-
9=1P,B,0,0,66690,0    -{ Entering=VIEW_AXIS_INDICATOR_CYCLE }-
10=BZ,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-
11=BS,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
12=BT,256
13=BT,B,0,0,1007,0    -{ Entering=autobrake set }-
14=BT,B,0,0,1007,0    -{ Entering=autobrake set }-

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=PB,30,C65615,0     -{ELEV_TRIM_UP}-
2=PB,29,C65607,0     -{ELEV_TRIM_DN}-
3=PB,18,C66718,0     -{CABIN_NO_SMOKING_ALERT_SWITCH_TOGGLE}-
4=PB,17,C66719,0     -{CABIN_SEATBELTS_ALERT_SWITCH_TOGGLE}-
5=UB,29,C0,0     -{Custom control: <0>}-
6=R1,4,C66080,0     -{GEAR_DOWN}-
7=U1,4,C66079,0     -{GEAR_UP}-
8=PB,5,C66059,0     -{LANDING_LIGHTS_ON}-
9=PB,6,C66060,0     -{LANDING_LIGHTS_OFF}-
10=PB,7,C66052,0     -{STROBES_ON}-
11=PB,8,C66053,0     -{STROBES_OFF}-
14=P1,1,C65567,0     -{VIEW_MODE}-
15=P1,5,C65752,0     -{PARKING_BRAKES}-
16=PB,27,C66079,0     -{GEAR_UP}-
17=PB,28,C66080,0     -{GEAR_DOWN}-
22=PB,24,C66528,0     -{EYEPOINT_FORWARD}-
23=PB,26,C66529,0     -{EYEPOINT_BACK}-
24=PB,4,C0,0     -{Custom control: <0>}-

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

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=D:\Lockheed Martin\Prepar3D v4\Sound\
Device1=Podstawowy sterownik dźwięku
Device2=Głośniki (Creative T6 Series II USB Audio)
Device3=Cyfrowe urządzenie audio (S/PDIF) (Urządzenie zgodne ze standardem High Definition Audio)
Device4=ROG PG348Q-4 (NVIDIA High Definition Audio)

[Profile.p3d]
1=Boeing 737-86NNGX kulula.com (Flying 101) Winglets
2=Aerosoft A321 professional FINNAIR OH-NEO
3=CRJ700ER HOP! Air France F-GRZH
4=Aerosoft A321 professional BRITISH AIRWAYS G-EUXG

[Axes.p3d]
RangeRepeatRate=10
0=0X,256,D,4,0,0,0    -{ DIRECT: Throttle }-
1=1P,R0
2=1P,B,0,0,66690,0    -{ Entering=VIEW_AXIS_INDICATOR_CYCLE }-
3=2Y,1,D,4,25,0,0    -{ DIRECT: Throttle, Reverser }-
4=2Z,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-
6=2V,B,0,0,65606,0    -{ Entering=VIEW }-

[JoystickCalibration.p3d]
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
RudderBlendLowest=1
Throttle=-16384,16383

[Monitor]
Display=15

[Buttons.p3d]
0=P1,10,C65759,0     -{FLAPS_DECR}-
1=P1,12,C65758,0     -{FLAPS_INCR}-
2=R1,32,C66151,0     -{VIEW_ALWAYS_PAN_UP}-
3=R1,38,C65680,0     -{VIEW_LEFT}-
4=R1,34,C65676,0     -{VIEW_RIGHT}-
5=R1,36,C66152,0     -{VIEW_ALWAYS_PAN_DOWN}-
6=R1,32,C66151,0     -{VIEW_ALWAYS_PAN_UP}-
7=R1,36,C66152,0     -{VIEW_ALWAYS_PAN_DOWN}-
8=R1,38,C65680,0     -{VIEW_LEFT}-
9=R1,34,C65676,0     -{VIEW_RIGHT}-
10=R1,39,C66143,0     -{VIEW_LEFT_UP}-

[Profile.Prepar3d]
1=CS 757-200 Captain Sim House 2018 4
2=Boeing 737-900NGX Boeing Technology Demonstrator
3=CRJ900ER SAS Scandinavian Airlines OY-KFI
4=Airbus A319 EUROWINGS D-AGWZ (Aerosoft A319 IAE Professional)
5=F-22 Raptor - 525th Fighter Squadron
6=CRJ700ER Lufthansa Regional Star Alliance D-ACPT
7=Aerosoft A320 professional EASYJET G-EZTB
8=CRJ900ER AtlasGlobal TC-ETC
9=CRJ900ER Lufthansa CityLine D-ACNM NC

[JoystickCalibration.Prepar3d]
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
RudderBlendLowest=1
Aileron=-16380,-512,512,16380
Elevator=-16380,-512,512,16380
Rudder=-16380,-512,512,16380
Spoilers=-16380,16380
Flaps=0,16380
Reverser=-11263,16380/24
Throttle=-16380,16380

[Axes.Prepar3d]
RangeRepeatRate=10
0=0X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
1=0Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
2=0R,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=1X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
4=1Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
5=1R,256,D,3,0,0,0    -{ DIRECT: Rudder }-
7=1U,B,0,0,66992,0    -{ Entering=EYEPOINT_MOVE_VERTICAL }-
8=1U,B,0,0,66992,0    -{ Entering=EYEPOINT_MOVE_VERTICAL }-
9=1V,256
10=1V,B,0,0,66992,0    -{ Entering=EYEPOINT_MOVE_VERTICAL }-
11=1V,B,0,0,66992,0    -{ Entering=EYEPOINT_MOVE_VERTICAL }-
13=1P,B,0,0,66690,0    -{ Entering=VIEW_AXIS_INDICATOR_CYCLE }-
14=2Y,256,D,4,25,0,0    -{ DIRECT: Throttle, Reverser }-
15=2R,256,D,25,0,0,0    -{ DIRECT: Reverser }-
16=2U,256
17=2U,BR,0,0,65701,0    -{ Entering=VIEW_ZOOM_SET }-
18=2S,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
19=2T,256,D,23,0,0,0    -{ DIRECT: Flaps }-
20=7X,R0,D,10,0,0,0    -{ DIRECT: Throttle2 }-
21=7T,R0,D,9,0,0,0    -{ DIRECT: Throttle1 }-

[Buttons.Prepar3d]
0=P0,32,C66151,0     -{VIEW_ALWAYS_PAN_UP}-
1=R0,36,C66152,0     -{VIEW_ALWAYS_PAN_DOWN}-
2=R0,38,C65681,0     -{VIEW_FORWARD_LEFT}-
3=R0,34,C65675,0     -{VIEW_FORWARD_RIGHT}-
4=R0,0,C65588,0     -{BRAKES}-
5=P0,5,C65752,0     -{PARKING_BRAKES}-
7=P2,5,C66059,0     -{LANDING_LIGHTS_ON}-
8=P2,6,C66060,0     -{LANDING_LIGHTS_OFF}-
9=P2,7,C66052,0     -{STROBES_ON}-
10=P2,8,C66053,0     -{STROBES_OFF}-
12=R0,39,C66144,0     -{VIEW_FORWARD_LEFT_UP}-
13=R0,1,C65567,0     -{VIEW_MODE}-

[Profile.CRJ 900]
1=CRJ900ER US Airways Express N247LR

[Axes.CRJ 900]
RangeRepeatRate=10
0=0P,0,D,35,0,0,0    -{ DIRECT: PanTilt }-
1=1R,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=1U,B,0,0,66992,0    -{ Entering=EYEPOINT_MOVE_VERTICAL }-
4=1U,B,0,0,66992,0    -{ Entering=EYEPOINT_MOVE_VERTICAL }-
5=1V,256
6=1V,B,0,0,66992,0    -{ Entering=EYEPOINT_MOVE_VERTICAL }-
7=1V,B,0,0,66992,0    -{ Entering=EYEPOINT_MOVE_VERTICAL }-
9=1P,B,0,0,66690,0    -{ Entering=VIEW_AXIS_INDICATOR_CYCLE }-
10=2Z,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-
11=2S,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
12=2T,256
13=2T,B,0,0,1007,0    -{ Entering=autobrake set }-
14=2T,B,0,0,1007,0    -{ Entering=autobrake set }-

[JoyNames]
AutoAssignLetters=Yes
A=X56 H.O.T.A.S. Stick
A.GUID={9FF0B3C0-C406-11E8-8008-444553540000}
B=X56 H.O.T.A.S. Throttle
B.GUID={9FDCB690-C406-11E8-8004-444553540000}
0=X56 H.O.T.A.S. Stick
0.GUID={9FF0B3C0-C406-11E8-8008-444553540000}
2=X56 H.O.T.A.S. Throttle
2.GUID={9FDCB690-C406-11E8-8004-444553540000}

[Profile.axc]
1=CRJ700ER Conviasa YV2088
2=CRJ900ER Adria Airways S5-AAK
 

[Pete Dowson]

18 hours ago, Albert Szmidt said:

Hi Pete, Ive changed it manually- by changind no to yes and somerthing probably is wrong 😞

Like what? A is the Stick and B is the Thottle. IDs 0 and 2. You must have had a third device at one time as there are assignmwents to a non-existent device 1.

You have, so far, not bothered to provide the extra logging with the option I requested added to the INI file. 

Also you are still using FSUIPC version 5.14. Please update to the currently supported version. Then do that logging I asked for on Friday, and supply Log, INI and the Joyscan CSV file.

Really your INI file is a bit messy. You have odd Profile names like " p3d" and "Prepar3d" which must be hard to differentiate, as well as "axc" and "CRJ900".  I can't really analyse all of that, so, as a test, try moving that INI file out, or renaming it 9so you don't lose it), then let FSUIPC generate a fresh one.

Pete

 

[Albert Szmidt]

Where can i find the latest version (update mine 5.14.?) On the simmarket.com that one is as the latest one ;/

[Pete Dowson]

2 hours ago, Albert Szmidt said:

On the simmarket.com that one is as the latest one ;/

Sorry, i should have been clearer. The full release is 5.14, but there's an interim update 5.141e, which is available (DLL replacement only) in the Updated Modules thread of the Download Links subforum above. That's where all my software is availalbe. 

Actually I misspoke when I implied 5.14 wasn't supported. it still is at present. But it is best when dealing with problems that both of us are using the same.

Pete

 

[Albert Szmidt]

FSUIPC5.ini

FSUIPC5.JoyScan.csv

[Pete Dowson]

And still no log.  the INI and CSV are no use on their own. I asked you (twice before now) to add two specific lines to the INI  and supply the resulting log.

Pete

 

[John Dowson]

The logging lines have been added to the ini file - you just need to start the sim and supply the log file.

 

[Pete Dowson]

8 minutes ago, John Dowson said:

The logging lines have been added to the ini file

Oh, so they have -- at the start! ;-). I looked at the end, where most folks add them. Apologies.

Pete

 

[Albert Szmidt]

Ok 😉

[Albert Szmidt]

Pete what can I do now? 😞 im completely lost 😞

[Pete Dowson]

1 hour ago, Albert Szmidt said:

Pete what can I do now? 😞 im completely lost 😞

Why lost?  Run P3D4. Then provide THREE files, not TWO:

FSUIPC5.INI
FSUIPC5.LOG
FSUIPC5.Joyscan.csv

You just forgot to supply the log file as requested. The whole point of adding those two lines, which you did, was to get more information in the log, but I cannot use that information unless you supply that log.

Pete

 

[Albert Szmidt]

I sent more (just in case)

[Pete Dowson]

39 minutes ago, Albert Szmidt said:

I sent more (just in case)

I had to delete that post. You included your Registration for others to copy. If SimMarket find that now being distributed for others to use they will invalidate it and you will have to purchase another. it is a violation of the terms of sale!

Please ONLY post the three files I listed!!!

Pete

 

[Albert Szmidt]

Im sorry. posted again

FSUIPC5.ini

FSUIPC5.JoyScan.csv

FSUIPC5.log

[Albert Szmidt]

FSUIPC5.ini

FSUIPC5.JoyScan.csv

FSUIPC5.log

[Pete Dowson]

Posted twice, for good measure?

You seem to have started P3D before connecting the devices. Is that right?  FSUIPC signals that devices were connected after everything was started and so re-scans.

The INI file report that only the Throtte was connected, as you said, but it appears to be listed with the same GUID as the Stick. Did the Throttle respond okay in the Axis Assignments tab? Check now if you don't know.

I need to analyse the log further -- it's a rather complicated sequence because of the re-scanning. but it does look to me like a screwed up Registry for these devices. It's the Registry entries for the two devices.

I am not convinced you uninstalled the devices properly at all. As John said whilst I was away:

Quote

In the meantime, can you confirm that you have disconnected your devices &  uninstalled all saitek devices, drivers and software (from the control panel), then reboot and connect your devices (which should install the standard windows drivers, not the Saitek ones). If not, please do this first.

and I requested again last Friday:

Quote

When you uninstalled the Saitek software, and the devices, did you go to the Windows Device Manager, find the devices, right-click, select uninstall, and then also the option to remove drivers? All that is needed to correct the mess that Saitek installers seem to often perpetrate

but to which you replied, rather confusingly and ambiguously:
 

Quote

I have checked and finally I found some uninstalled drivers (I have uninstalled them by device manager - one of them i didnt tick to uninstall drivers and now im lost by the way to find it, there was like 15 positions? Have ne idea why so many positions of the same device)). After this I got same problem 😞

If you do this properly it should clear out all references to your devices. To be sure it does, first unplug them.

Then, knowing it's the devices themselves which need uninstalling (not explicitly drivers now), you use Device Manager (one of the Control Panel apps). When you select uninstall for a device entry you are also asked whether you want to also uninstall drivers. Just say yes. Confim everything. Re-boot the PC.  THEN

In case there are multiple entries as you suggested Friday, do all that again. Keep doing it and re-booting until there are NO entries for those devices there. ONLY THEN reconnect them

Oh, one other thing, whilst in Device Manager: find all the USB devices and ensure that 'power management' is turned off in the Properties of every one of those which has such a facility.

Now start P3D. Let me know the result then, with those three files again. I'd like to compare the result you then get with what you already supplied.

I honestly think all of this is down purely to the mess some Saitek installs seem to make of the Registry.

Please, if there's anything you don't understand or can't find, do not guess. Ask.

Pete

 

 

[Albert Szmidt]

Thats right, Ill try to do this, will be back soon. Thank You 

[Albert Szmidt]

I'm still trying to find some mess after saitek software, but the problem is that I cannot find anything more at device manager. Any idea where can I find it as well? I already checked windows32 folder, deleted some saitek drivers too from there. Please help me 😞 I had some drivers too at device manager but after that when I uninstalled it still I got same problem, also when I'm connecting my saitek x56 the system cannot find any drivers for this device, excluding information that thisbfevive is installed and ready to use ( but when I'm checking details there is no driver installed).=1

[Pete Dowson]

28 minutes ago, Albert Szmidt said:

I'm still trying to find some mess after saitek software

Sorry, how do you find "mess". I'm not sure what you mean.

29 minutes ago, Albert Szmidt said:

I cannot find anything more at device manager. Any idea where can I find it as well? I already checked windows32 folder, deleted some saitek drivers too from there.

Don't mess deleting files, please. you could make things worse. There's no point in looking in folders. In Device Manager you would normally find Game Controllers like the Saitek devices under the entry "Sound, video and game controllers", but if there's nothing there remotely looking like your devices, they could just be listed under "Human Interface Devices" as "Hid-compliant game controller". 

If you can't find them, I can only think I'll have to edit your Registry for you. (I'll supply a .reg file which removes just the culprit entries).

48 minutes ago, Albert Szmidt said:

Please help me 😞 I had some drivers too at device manager but after that when I uninstalled it still I got same problem, also when I'm connecting my saitek x56 the system cannot find any drivers for this device,

It doesn't need anything but the default Windows Game Controllers driver. If you've deleted something which is a default windows driver you may need to run Windows Repair, or even re-install Windows. In fact, with all the time and messing about we are doing it might be quicker just to reinstall.

But don't do anything at present EXCEPT in the Device Manager as above. Failing that, I'll first just do it by deleting the entries in the Registry.

50 minutes ago, Albert Szmidt said:

excluding information that thisbfevive is installed and ready to use

Sorry, I don't understand this part.

Pete

 

[Albert Szmidt]

Excluding an information that this is installed and ready to use, but when I wanna check details at device manager I can only see saitek bulk and no drivers installed details 

[Pete Dowson]

3 hours ago, Albert Szmidt said:

when I wanna check details at device manager I can only see saitek bulk and no drivers installed details 

Uninstall any device showing as Saitek. If there's no option to remove driver too, don't worry -- I'm pretty sure I did say "if".

Pete

 

[Albert Szmidt]

Hi Pete, there is still the same problem- I did reboot of my windows, again I got same problem as before. Sending all requested files again. 

 

Thank u

Regards

FSUIPC5.ini

FSUIPC5.JoyScan.csv

FSUIPC5.log

[Pete Dowson]

35 minutes ago, Albert Szmidt said:

there is still the same problem- I did reboot of my windows, again I got same problem as before. Sending all requested files again.

These all show everything good for both Stick and Throttle. I can't see anything wrong! The results look as good as any X-56 user's I've seen, and my own X-55 (when I had one here).

Have you tried assigning in the Sim instead? Why are you assigning in FSUIPC in any case?

Pete

 

 

[Albert Szmidt]

Ive tried too now, the sim can see all buttons but cannot see axis X and Y, I dont wanna install any saitek drivers thats why probably 😕