VFRHawk Posted November 6, 2015 Report Share Posted November 6, 2015 Hi, Wondering if someone can help. I've just built a new, powerful PC mostly for P3D V3. I have varios Orbx sceneries, and ASN for it. I've installed the latest FSUIPC (4948), but when I go into it in P3D in the button presses section it doesn't recognise any buttons on either by X55 stick or throttle, and in the axis assignment section it only recognises my Saitek rudder pedals. However, all 3 controllers work fine in P3D? Here's the P3D log (edited to take my name etc out): ********* FSUIPC4, Version 4.948 by Pete Dowson ********* Reading options from "E:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 8.0 Module base=172E0000 User Name="" User Addr="" FSUIPC4 Key is provided WideFS7 Key is provided 375 System time = 06/11/2015 16:31:28 375 FLT UNC path = "\\GAMINGRIG\Users\\Documents\Prepar3D v3 Files\" 375 Trying E:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll 390 Found it: trying to connect 390 FS UNC path = "E:\Lockheed Martin\Prepar3D v3\" 515 ---------------------- Joystick Device Scan ----------------------- 515 Product= Saitek Pro Flight X-55 Rhino Throttle 515 Manufacturer= Madcatz 515 Vendor=0738, Product=A215 (Version 0.119) 515 Serial Number= G0000836 531 Product= Saitek Pro Flight X-55 Rhino Stick 531 Manufacturer= Madcatz 531 Vendor=0738, Product=2215 (Version 0.87) 531 Serial Number= G0001495 531 Product= Saitek Pro Flight Rudder Pedals 531 Manufacturer= Saitek 531 Vendor=06A3, Product=0763 (Version 1.1) 531 Serial Number= Saitek 531 ------------------------------------------------------------------- 531 LogOptions=00000000 00000001 531 ------------------------------------------------------------------- 531 ------ Setting the hooks and direct calls into the simulator ------ 531 --- CONTROLS timer memory location obtained ok 547 --- SIM1 Frictions access gained 547 --- FS Controls Table located ok 547 --- Installed Mouse Macro hooks ok. 547 --- Wind smoothing fix is installed 547 --- All links okay (except older global weather setting method) 547 ------------------------------------------------------------------- 547 SimConnect_Open succeeded: waiting to check version okay 547 Trying to use SimConnect Prepar3D 6234 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.0.3.0 (SimConnect: 3.0.0.0) 6234 Initialising SimConnect data requests now 6234 FSUIPC Menu entry added 6250 \\GAMINGRIG\Users\\Documents\Prepar3D v3 Files\AH.flt 6250 \\GAMINGRIG\Users\\Documents\Prepar3D v3 Files\AH.pln 6250 E:\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\beech_baron_58\Beech_Baron_58.air 6250 \\GAMINGRIG\Users\\Documents\Prepar3D v3 Files\AH.pln 39672 System time = 06/11/2015 16:32:08, Simulator time = 16:31:35 (16:31Z) 39672 Aircraft="Beech Baron 58 w G1000" 40687 Starting everything now ... 40750 ASN active function link set 40750 Ready for ASN WX radar 43859 Advanced Weather Interface Enabled 116515 Sim stopped: average frame rate for last 40 secs = 19.9 fps 133953 === NOTE: not calling SimConnect_Close ... 134953 System time = 06/11/2015 16:33:43, Simulator time = 16:32:11 (16:32Z) 134953 *** FSUIPC log file being closed Minimum frame rate was 19.8 fps, Maximum was 20.0 fps Minimum available memory recorded was 1719Mb Average frame rate for running time of 46 secs = 19.9 fps Memory managed: 15 Allocs, 15 Freed ********* FSUIPC Log file closed *********** That shows all 3 controllers, so I'm a bit lost as to why they aren't working? Any help appreciated! Graham Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 9, 2015 Report Share Posted November 9, 2015 I've installed the latest FSUIPC (4948), but when I go into it in P3D in the button presses section it doesn't recognise any buttons on either by X55 stick or throttle, and in the axis assignment section it only recognises my Saitek rudder pedals. However, all 3 controllers work fine in P3D? Here's the P3D log (edited to take my name etc out): There are all sorts of problems with P3D, but I've not heard of this one specifically. Can you show me your FSUIPC4.INI file please? Pete Link to comment Share on other sites More sharing options...
VFRHawk Posted November 13, 2015 Author Report Share Posted November 13, 2015 Sorry for the delay, my internet died earlier in the week. Now it's been resuscitated: ********* FSUIPC4, Version 4.948 by Pete Dowson ********* Reading options from "E:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 8.0 Module base=16700000 User Name="" User Addr="" FSUIPC4 Key is provided WideFS7 Key is provided 234 System time = 10/11/2015 21:54:38 234 FLT UNC path = "\\GAMINGRIG\Users\\Documents\Prepar3D v3 Files\" 234 Trying E:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll 234 Found it: trying to connect 250 FS UNC path = "E:\Lockheed Martin\Prepar3D v3\" 359 ---------------------- Joystick Device Scan ----------------------- 375 Product= Saitek Pro Flight Rudder Pedals 375 Manufacturer= Saitek 375 Vendor=06A3, Product=0763 (Version 1.1) 375 Serial Number= Saitek 375 Product= Saitek Pro Flight X-55 Rhino Throttle 375 Manufacturer= Madcatz 375 Vendor=0738, Product=A215 (Version 0.119) 375 Serial Number= G0000836 375 Product= Saitek Pro Flight X-55 Rhino Stick 375 Manufacturer= Madcatz 375 Vendor=0738, Product=2215 (Version 0.87) 375 Serial Number= G0001495 375 ------------------------------------------------------------------- 391 LogOptions=00000000 00000001 391 ------------------------------------------------------------------- 391 ------ Setting the hooks and direct calls into the simulator ------ 391 --- CONTROLS timer memory location obtained ok 391 --- SIM1 Frictions access gained 391 --- FS Controls Table located ok 391 --- Installed Mouse Macro hooks ok. 391 --- Wind smoothing fix is installed 391 --- All links okay (except older global weather setting method) 391 ------------------------------------------------------------------- 391 SimConnect_Open succeeded: waiting to check version okay 391 Trying to use SimConnect Prepar3D 4687 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.0.3.0 (SimConnect: 3.0.0.0) 4687 Initialising SimConnect data requests now 4687 FSUIPC Menu entry added 4703 \\GAMINGRIG\Users\\Documents\Prepar3D v3 Files\AH.flt 4703 \\GAMINGRIG\Users\\Documents\Prepar3D v3 Files\AH.pln 4703 E:\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\beech_baron_58\Beech_Baron_58.air 4703 \\GAMINGRIG\Users\\Documents\Prepar3D v3 Files\AH.pln 63906 System time = 10/11/2015 21:55:41, Simulator time = 21:54:44 (21:54Z) 63906 Aircraft="Beech Baron 58 w G1000" 64906 Starting everything now ... 64969 ASN active function link set 64969 Ready for ASN WX radar 68266 Advanced Weather Interface Enabled 86609 Sim stopped: average frame rate for last 23 secs = 19.9 fps 198375 Sim stopped: average frame rate for last 72 secs = 19.9 fps 217359 === NOTE: not calling SimConnect_Close ... 218359 System time = 10/11/2015 21:58:16, Simulator time = 21:56:05 (21:56Z) 218359 *** FSUIPC log file being closed Minimum frame rate was 19.3 fps, Maximum was 20.0 fps Minimum available memory recorded was 1532Mb Average frame rate for running time of 107 secs = 19.9 fps Memory managed: 29 Allocs, 29 Freed ********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 7, 2015 Report Share Posted December 7, 2015 Sorry for the delay, my internet died earlier in the week. Now it's been resuscitated: That's the LOG file again. I asked to see the INI file, please. Pete Link to comment Share on other sites More sharing options...
VFRHawk Posted December 16, 2015 Author Report Share Posted December 16, 2015 Apologies, both for the delay and the incorrect info. Here's the .ini file: [General] Console=No UpdatedByVersion=4948e History=5JH2QMHXRPKW42CF85ZKZ 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=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.0.3.0 SimConnectUsed=3.0.0.0 [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight X-55 Rhino Throttle 0.GUID={C94D6E20-8269-11E5-8005-444553540000} 1=Saitek Pro Flight X-55 Rhino Stick 1.GUID={C94D9530-8269-11E5-8007-444553540000} 2=Saitek Pro Flight Rudder Pedals 2.GUID={C94DBC40-8269-11E5-8009-444553540000} [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 [GPSout2] GPSoutEnabled=No [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [sounds] Path=E:\Lockheed Martin\Prepar3D v3\Sound\ Device1=Primary Sound Driver Device2=Headset Earphone (HyperX 7.1 Audio) Device3=Acer X34-8 (NVIDIA High Definition Audio) Device4=Realtek Digital Output (Realtek High Definition Audio) [Window.AirHauler Message] Docked=200, 2457, 3572, 568 Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 17, 2015 Report Share Posted December 17, 2015 I've installed the latest FSUIPC (4948), but when I go into it in P3D in the button presses section it doesn't recognise any buttons on either by X55 stick or throttle, and in the axis assignment section it only recognises my Saitek rudder pedals. However, all 3 controllers work fine in P3D? Okay. From the INI file I see that all three devices ARE recognised by FSUIPC and do have assigned ID numbers (0, 1 and 2):: [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight X-55 Rhino Throttle 0.GUID={C94D6E20-8269-11E5-8005-444553540000} 1=Saitek Pro Flight X-55 Rhino Stick 1.GUID={C94D9530-8269-11E5-8007-444553540000} 2=Saitek Pro Flight Rudder Pedals 2.GUID={C94DBC40-8269-11E5-8009-444553540000} So, let me ask you, where exactly are you looking when you say the button presses and axes aren't recognised? Have you seen the pinned thread at the top of this Forum, entitled "IMPORTANT: FSUIPC calibration of axes in P3D version 3"? If that describes your problem then you can either use the suggested work-around or wait for the imminent P3D version 3.1, in which I think this will be fixed. Pete Link to comment Share on other sites More sharing options...
VFRHawk Posted December 17, 2015 Author Report Share Posted December 17, 2015 OK, I load P3D V3, go into FSUIPC, select the Buttons + Switches tab, and whatever buttons I press on either the stick or throttle, nothing is recognised. The "Press the joystick button you wish to program" section doesn't react at all. I haven't tried programming axes as I do that in P3D itself - I just happened to notice whilst I was exploring FSUIPC after this problem raised it's head that the Axis Assignment tab recognises input from my pedals, but not anything else. All I wanted to do was program 1, 2, 3 and 0 as inputs to a hat switch for use with Pro ATC/X! :) Thanks for your help Graham Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 17, 2015 Report Share Posted December 17, 2015 OK, I load P3D V3, go into FSUIPC, select the Buttons + Switches tab, and whatever buttons I press on either the stick or throttle, nothing is recognised. The "Press the joystick button you wish to program" section doesn't react at all. Hmm very strange. Do you have any other software installed which may be handling the affected devices? For instance a Saitek program? You say the rudder pedals are okay, so I don't understand how it cannot see the others. I'll need more logging. Please edit the FSUIPC4.INI file (in the Modules folder), adding these lines to the [General] section: Debug=Please LogExtras=x200200 Then run FS and try again. Please then show me the Log. Pete Link to comment Share on other sites More sharing options...
VFRHawk Posted December 18, 2015 Author Report Share Posted December 18, 2015 OK, log below after adding those lines. I had the Saitek software installed but it occasionally caused button presses to be sent to windows when I wasn't in a game so I deleted it and ran a ccleaner registry clean afterwards. Other than that, I installed joyID's after reading another thread on here, but as far as I know that doesn't run in the background, and this problem pre-dates that install anyway. Can't think of anything else that could cause the problem? I use the PMDG 737 NGX, Air Hauler, P3D V3, Pro ATC/X and ASN. The issue pre-dates install of the 737 and Pro ATC/X at least though, and happens even when I haven't opened ASN or AH before I launch P3D. ********* FSUIPC4, Version 4.948e by Pete Dowson ********* Prepar3D.exe version = 3.0.10.14945 Reading options from "E:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 8.0 Module base=16D90000 User Name="" User Addr="vfrhawk@hotmail.com" FSUIPC4 Key is provided WideFS7 Key is provided 454 System time = 18/12/2015 16:14:57 454 FLT UNC path = "\\GAMINGRIG\Users\\Documents\Prepar3D v3 Files\" 454 ------ Module Version Check ------ 454 acontain.dll: 3.0.10.14945 454 api.dll: 3.0.10.14945 454 controls.dll: 3.0.10.14945 454 fs-traffic.dll: 3.0.10.14945 454 G3D.dll: 3.0.10.14945 454 sim1.dll: 3.0.10.14945 454 visualfx.dll: 3.0.10.14945 454 weather.dll: 3.0.10.14945 454 window.dll: 3.0.10.14945 454 ---------------------------------- 454 Trying E:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll 500 Found it: trying to connect 500 FS UNC path = "E:\Lockheed Martin\Prepar3D v3\" 579 #### Initialising Dlrectinput Axis Scanning ... 594 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_A215\Calibration\0" 594 Found correct joystick Id 0 594 ... and a "GUID" value 610 ... okay, Acquired device as #0 610 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\Calibration\0" 610 Found correct joystick Id 1 610 ... and a "GUID" value 610 ... okay, Acquired device as #1 610 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0" 610 Found correct joystick Id 2 610 ... and a "GUID" value 610 ... okay, Acquired device as #2 610 ---------------------- Joystick Device Scan ----------------------- 610 Checking: \\?\hid#vid_0951&pid_16a4&mi_03&col01#7&1c94fa2&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Checking: \\?\hid#vid_1b1c&pid_1c0d#6&390dc39e&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Checking: \\?\hid#vid_0738&pid_a215&mi_02#8&2e6068d8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Checking: \\?\hid#vid_e0ff&pid_0002&mi_01&col01#8&b67a4cb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Checking: \\?\hid#vid_0951&pid_16a4&mi_03&col02#7&1c94fa2&1&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Checking: \\?\hid#vid_06a3&pid_0763#6&32b02881&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Product= Saitek Pro Flight Rudder Pedals 610 Manufacturer= Saitek 610 Vendor=06A3, Product=0763 (Version 1.1) 610 Serial Number= Saitek 610 Checking: \\?\hid#vid_e0ff&pid_0002&mi_00#8&1e97c109&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Checking: \\?\hid#vid_e0ff&pid_0002&mi_01&col02#8&b67a4cb&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Checking: \\?\hid#vid_0951&pid_16a4&mi_03&col03#7&1c94fa2&1&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Checking: \\?\hid#vid_0738&pid_2215&mi_02#9&114007b2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Checking: \\?\hid#vid_045e&pid_074b&mi_01#7&34e2812d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Checking: \\?\hid#vid_e0ff&pid_0002&mi_01&col03#8&b67a4cb&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Checking: \\?\hid#vid_0738&pid_a215&mi_00#8&3a741a55&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Product= Saitek Pro Flight X-55 Rhino Throttle 610 Manufacturer= Madcatz 610 Vendor=0738, Product=A215 (Version 0.119) 610 Serial Number= G0000836 610 Checking: \\?\hid#vid_0738&pid_2215&mi_00#9&366e73d2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 Product= Saitek Pro Flight X-55 Rhino Stick 610 Manufacturer= Madcatz 610 Vendor=0738, Product=2215 (Version 0.87) 610 Serial Number= G0001495 610 Checking: \\?\hid#vid_045e&pid_074b&mi_00#7&110b436b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 610 ------------------------------------------------------------------- 610 #### Completed Dlrectinput Axis Scanning 610 ---------- Making INI JoyNames Section ---------- 610 Joy#0: Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_A215\" 610 Joy#0: OEMName = "Saitek Pro Flight X-55 Rhino Throttle" 610 Joy#0: GUID = {C94D6E20-8269-11E5-8005-444553540000} 610 Joy#1: Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_2215\" 610 Joy#1: OEMName = "Saitek Pro Flight X-55 Rhino Stick" 625 Joy#1: GUID = {C94D9530-8269-11E5-8007-444553540000} 625 Joy#2: Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0763\" 625 Joy#2: OEMName = "Saitek Pro Flight Rudder Pedals" 625 Joy#2: GUID = {C94DBC40-8269-11E5-8009-444553540000} 625 ------------------------------------------------- 641 Device at "\\?\hid#vid_0951&pid_16a4&mi_03&col01#7&1c94fa2&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 641 HID: Vendor=0951, Product=16A4 (Version 0.3) 641 Manufacturer= Kingston 672 Product= HyperX 7.1 Audio 672 Serial Number= 00000000 672 Device at "\\?\hid#vid_1b1c&pid_1c0d#6&390dc39e&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 672 HID: Vendor=1B1C, Product=1C0D (Version 0.2) 688 Manufacturer= 688 Product= 688 Serial Number= 688 Device at "\\?\hid#vid_0738&pid_a215&mi_02#8&2e6068d8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 688 HID: Vendor=0738, Product=A215 (Version 0.119) 688 Manufacturer= Madcatz 688 Product= Saitek Pro Flight X-55 Rhino Throttle 688 Serial Number= G0000836 688 Device at "\\?\hid#vid_e0ff&pid_0002&mi_01&col01#8&b67a4cb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 688 HID: Vendor=E0FF, Product=0002 (Version 0.1) 688 Manufacturer= A..... 688 Product= Shogun Bros. Ballista MK-I Mouse 688 Serial Number= Shogun Bros. Ballista MK-I Mouse 688 Device at "\\?\hid#vid_0951&pid_16a4&mi_03&col02#7&1c94fa2&1&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" 688 HID: Vendor=0951, Product=16A4 (Version 0.3) 704 Manufacturer= Kingston 719 Product= HyperX 7.1 Audio 735 Serial Number= 00000000 735 Device at "\\?\hid#vid_06a3&pid_0763#6&32b02881&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 735 HID: Vendor=06A3, Product=0763 (Version 1.1) 735 Manufacturer= Saitek 735 Product= Saitek Pro Flight Rudder Pedals 735 Serial Number= Saitek Pro Flight Rudder Pedals 735 Device at "\\?\hid#vid_0951&pid_16a4&mi_03&col03#7&1c94fa2&1&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" 735 HID: Vendor=0951, Product=16A4 (Version 0.3) 750 Manufacturer= Kingston 766 Product= HyperX 7.1 Audio 782 Serial Number= 00000000 782 Device at "\\?\hid#vid_0738&pid_2215&mi_02#9&114007b2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 782 HID: Vendor=0738, Product=2215 (Version 0.87) 782 Manufacturer= Madcatz 782 Product= Saitek Pro Flight X-55 Rhino Stick 782 Serial Number= G0001495 782 Device at "\\?\hid#vid_045e&pid_074b&mi_01#7&34e2812d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 782 HID: Vendor=045E, Product=074B (Version 2.96) 782 Manufacturer= Microsoft 782 Product= Microsoft® SiderWinderTM X6 Keyboard 782 Serial Number= Microsoft® SiderWinderTM X6 Keyboard 782 Device at "\\?\hid#vid_e0ff&pid_0002&mi_01&col03#8&b67a4cb&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" 782 HID: Vendor=E0FF, Product=0002 (Version 0.1) 782 Manufacturer= A..... 782 Product= Shogun Bros. Ballista MK-I Mouse 782 Serial Number= Shogun Bros. Ballista MK-I Mouse 782 Device at "\\?\hid#vid_0738&pid_a215&mi_00#8&3a741a55&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 782 HID: Vendor=0738, Product=A215 (Version 0.119) 782 Manufacturer= Madcatz 782 Product= Saitek Pro Flight X-55 Rhino Throttle 782 Serial Number= G0000836 782 Device at "\\?\hid#vid_0738&pid_2215&mi_00#9&366e73d2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 782 HID: Vendor=0738, Product=2215 (Version 0.87) 782 Manufacturer= Madcatz 797 Product= Saitek Pro Flight X-55 Rhino Stick 797 Serial Number= 797 LogOptions=00000000 02002011 797 ------------------------------------------------------------------- 797 ------ Setting the hooks and direct calls into the simulator ------ 797 --- CONTROLS timer memory location obtained ok 797 --- SIM1 Frictions access gained 797 --- FS Controls Table located ok 797 --- Installed Mouse Macro hooks ok. 797 --- Wind smoothing fix is installed 797 --- All links okay (except older global weather setting method) 797 ------------------------------------------------------------------- 797 SimConnect_Open succeeded: waiting to check version okay 797 Trying to use SimConnect Prepar3D 4610 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.0.3.0 (SimConnect: 3.0.0.0) 4610 Initialising SimConnect data requests now 4610 FSUIPC Menu entry added 4625 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 4625 \\GAMINGRIG\Users\\Documents\Prepar3D v3 Files\Default.fxml 4625 E:\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\beech_baron_58\Beech_Baron_58.air 4829 Memory in use: 788Mb, Avail=3308Mb 47532 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 48000 System time = 18/12/2015 16:15:44, Simulator time = 16:15:02 (16:15Z) 48000 Aircraft="Beech Baron 58 w G1000" 49016 Starting everything now ... 49047 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 49079 ASN active function link set 49079 Ready for ASN WX radar 50172 Advanced Weather Interface Enabled 56047 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 65063 Memory in use: 2546Mb, Avail=1550Mb 76063 ---------- Making INI JoyNames Section ---------- 76063 Joy#0: Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_A215\" 76063 Joy#0: OEMName = "Saitek Pro Flight X-55 Rhino Throttle" 76063 Joy#0: GUID = {C94D6E20-8269-11E5-8005-444553540000} 76063 Joy#1: Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_2215\" 76063 Joy#1: OEMName = "Saitek Pro Flight X-55 Rhino Stick" 76063 Joy#1: GUID = {C94D9530-8269-11E5-8007-444553540000} 76063 Joy#2: Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0763\" 76063 Joy#2: OEMName = "Saitek Pro Flight Rudder Pedals" 76079 Joy#2: GUID = {C94DBC40-8269-11E5-8009-444553540000} 76079 ------------------------------------------------- 76360 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 82797 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 100750 === NOTE: not calling SimConnect_Close ... 101750 System time = 18/12/2015 16:16:38, Simulator time = 16:15:14 (16:15Z) 101750 *** FSUIPC log file being closed Minimum frame rate was 45.0 fps, Maximum was 50.8 fps Minimum available memory recorded was 1539Mb Average frame rate for running time of 13 secs = 45.8 fps Memory managed: 37 Allocs, 37 Freed ********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 18, 2015 Report Share Posted December 18, 2015 OK, log below after adding those lines. Hmm. It all looks okay as far as you went. all of the correct data about your devices is read and the correct entries recorded ready to detect buttons and axes. However, I notice you closed it down pretty soon after it was all ready to fly. Did you press any buttons or move any axes? One more test, please. Change the LogExtras=x200200 to be LogExtras=x1000 then run the sim. Press each button and move each axis whilst in flight mode, then in FSUIPC Options "Buttons & Switches" for buttons, Axes for axes. Show me the log from that, please. I'm running out of ideas. No one else has ever had a problem like this, where the devices are detected but never supply any data. It's a real puzzle. Pete Link to comment Share on other sites More sharing options...
VFRHawk Posted December 18, 2015 Author Report Share Posted December 18, 2015 That's generated 55k lines in the log file - I taxied, took off and climbed out, all buttons and axis used in flight, and then opened FSUIPC and moved them all in there too. The forum doesn't seem to want to let me paste it into a post - even split into sections, and I can't see an attach file option? Can I PM or email the file to you Pete? Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 18, 2015 Report Share Posted December 18, 2015 That's generated 55k lines in the log file In that case it is definitely seeing the buttons and switches! ZIP it up and send as attachment to petedowson@btconnect.com. Thanks, Pete Link to comment Share on other sites More sharing options...
VFRHawk Posted December 18, 2015 Author Report Share Posted December 18, 2015 Done. It does seem to, it just isn't let program anything to what it detects - as the UI isn't seeing anything! Graham Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 19, 2015 Report Share Posted December 19, 2015 The V axis on the Rudder Pedals is the only input which is ever seen as changing. And most of the time that is flicking between 32768 and zero. All the other inputs are returning zero all the time. These are returns from standard API calls reading the joysticks via normal standard USB requests. Why they aren't working is beyond me, I'm afraid. I can only suggest uninstalling them (via the Device Manager in the Windows control panel -- uninstall including drivers, unplug them, then re-boot the PC and re-connect them. Windows should reload the drivers automatically. I really don't understand how they could be working in P3D, because I'm sure it must have to use the same interface. There are other steps you could try: 1. Ensure the controllers are actually disabled in P3D (not just unassigned) in case that is somehow interfering. 2.. Use JoyIDs to change the ID numbers, eg. from 0,1,2 to 3.4.5. 3. Check the Registry entry is correct and fix if necessary -- see the FAQ subfrum thread "Some Saitek axes only provide partial movement" Pete Link to comment Share on other sites More sharing options...
VFRHawk Posted December 28, 2015 Author Report Share Posted December 28, 2015 "I can only suggest uninstalling them (via the Device Manager in the Windows control panel -- uninstall including drivers, unplug them, then re-boot the PC and re-connect them. " That seems to have done the trick - had to manually download and install the drivers, but now FSUIPC is seeing all the buttons as far as I can tell. Thanks a lot for all your help on this Pete. Graham Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now