Thomas Greer Posted October 24, 2015 Report Posted October 24, 2015 Hi Pete. I have recently upgraded to P3D v3, and so installed your FSUIPC 4.946. Up until this morning, everything worked fine until I opened up P3D and nothing was happening. So I checked the assignments and they had all gone. I tried to reassign the axis' but was unable to because nothing was happening even though i was moving my joystick. (saitek x52 pro and rudders). Regards Thomas.
Pete Dowson Posted October 24, 2015 Report Posted October 24, 2015 I have recently upgraded to P3D v3, and so installed your FSUIPC 4.946. You should be using 4.947c, the current supported version, or even 4.947d. Please see the Download Links subforum. Up until this morning, everything worked fine until I opened up P3D and nothing was happening. So I checked the assignments and they had all gone. I tried to reassign the axis' but was unable to because nothing was happening even though i was moving my joystick. (saitek x52 pro and rudders). FSUIPC does not "lose" assignments. They are all recorded in your FSUIPC settings (the FSUIPC4.INI file in the Modules folder. If the joystick isn't being sen by FSUIPC then it probably isn't being seen by P3D or Windows either. Did you check? I'm not aware of anything causing a sudden stop in a joystick -- there are many reasons for it to stop working whilst not in use, but it should "come to life" when used enough. When you say "assignments" do you really mean axis and button assignments in FSUIPC itself, or just calibration? Pete
Thomas Greer Posted October 28, 2015 Author Report Posted October 28, 2015 Installed 4.947d and issues not resolved. Would a teamviewer session be beneficial?
Pete Dowson Posted October 28, 2015 Report Posted October 28, 2015 Installed 4.947d and issues not resolved. Would a teamviewer session be beneficial? No, sorry, that is not an option for me. It would help move forward if you answered the questions arising in my first reply -- for a start, did you check whether P3D or Windows could see your joystick, or did it die completely for everything? And again, when you say "assignments" do you really mean axis and button assignments in FSUIPC itself, or just calibration? Until you can explain what it is you find is wrong I cannot really help. Pete
Thomas Greer Posted October 28, 2015 Author Report Posted October 28, 2015 P3D and windows can both see my devices. I am trying to assign an axis in the axis assignment page.
Pete Dowson Posted October 28, 2015 Report Posted October 28, 2015 P3D and windows can both see my devices. I am trying to assign an axis in the axis assignment page. Okay. That is clearer. It sounds like there's no ID assigned to the device. In that case please do three things: 1. Show me the FSUIPC4.LOG file from the FS Modules folder. 2. Show me the FSUIPC4.INI file from the same place 3. See if using the JoyIDs program to assign and ID will help -- see the FAQ subforum thread Fixing joystick connections not seen by fsuipc Pete
Thomas Greer Posted October 29, 2015 Author Report Posted October 29, 2015 Will do. I am not in the house today, but I will do it tonight.
Thomas Greer Posted October 29, 2015 Author Report Posted October 29, 2015 Will do. I am not in the house today, but I will do it tonight.
Thomas Greer Posted October 29, 2015 Author Report Posted October 29, 2015 Log file; ********* FSUIPC4, Version 4.947c by Pete Dowson ********* Reading options from "J:\P3D\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 8.0 Module base=5D090000 User Name="Thomas Greer" User Addr="greerthomas@me.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 16 System time = 28/10/2015 18:52:49 16 FLT path = "C:\Users\user\Documents\Prepar3D v3 Files\" 16 Trying J:\P3D\Modules\SimConnectP3D2.dll 16 Found it: trying to connect 31 FS path = "J:\P3D\" 187 ---------------------- Joystick Device Scan ----------------------- 187 Product= HP Wireless Keyboard Kit 187 Manufacturer= Hewlett Packard 187 Vendor=0461, Product=4E25 (Version 1.50) 187 Serial Number= Hewlett Packard 187 Product= Saitek Pro Flight Rudder Pedals 187 Manufacturer= Saitek 187 Vendor=06A3, Product=0763 (Version 1.1) 187 Serial Number= Saitek 187 Using existing joystick id: 0 187 Product= Saitek Pro Flight Yoke 187 Manufacturer= Saitek 187 Vendor=06A3, Product=0BAC (Version 3.4) 187 Serial Number= Saitek 187 Using existing joystick id: 1 187 ------------------------------------------------------------------- 203 LogOptions=00000000 00000001 203 ------------------------------------------------------------------- 203 ------ Setting the hooks and direct calls into the simulator ------ 203 --- CONTROLS timer memory location obtained ok 203 --- SIM1 Frictions access gained 203 --- FS Controls Table located ok 203 --- Installed Mouse Macro hooks ok. 203 --- Wind smoothing fix is installed 203 --- All links checked okay 203 ------------------------------------------------------------------- 203 SimConnect_Open succeeded: waiting to check version okay 203 Trying to use SimConnect Prepar3D 34359 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.0.3.0 (SimConnect: 3.0.0.0) 34359 Initialising SimConnect data requests now 34359 FSUIPC Menu entry added 34375 C:\Users\user\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml 34375 J:\P3D\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 100172 J:\P3D\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air 119000 System time = 28/10/2015 18:54:48, Simulator time = 08:00:01 (13:00Z) 119000 Aircraft="Boeing 737-86NNGX Smart Express" 125078 Starting everything now ... 125125 ASN active function link set 125125 Ready for ASN WX radar 126234 Advanced Weather Interface Enabled 325219 Sim stopped: average frame rate for last 207 secs = 48.1 fps 349766 === NOTE: not calling SimConnect_Close ... 350766 System time = 28/10/2015 18:58:40, Simulator time = 08:03:26 (13:03Z) 350766 *** FSUIPC log file being closed Minimum frame rate was 34.4 fps, Maximum was 73.3 fps Minimum available memory recorded was 2019Mb Average frame rate for running time of 207 secs = 48.1 fps Memory managed: 100 Allocs, 100 Freed ********* FSUIPC Log file closed ***********
Thomas Greer Posted October 29, 2015 Author Report Posted October 29, 2015 Ini file; [General] UpdatedByVersion=4947c History=ZAPUFC75JFQKRHVNZQK5A 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 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 FSVersionUsed="Lockheed Martin® Prepar3D® v3",3.0.3.0 SimConnectUsed=3.0.0.0 [JoyNames] AutoAssignLetters=No 0=HP Wireless Keyboard Kit 0.GUID={1D581E50-7763-11E5-8002-444553540000} 1=HP Wireless Keyboard Kit 1.GUID={1D5670A0-7763-11E5-8001-444553540000} 2=HP Wireless Keyboard Kit 2.GUID={1D581E50-7763-11E5-8003-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 [sounds] Path=J:\P3D\Sound\ Device1=Primary Sound Driver Device2=Speakers / Headphones (IDT High Definition Audio CODEC) Device3=Digital Output (S/PDIF) (IDT High Definition Audio CODEC) Device4=Speakers (3- Raptor HS40)
Pete Dowson Posted October 29, 2015 Report Posted October 29, 2015 Okay. did you yet try the third thing, using JoyIDs to assign your joystick IDs? Something very strange has happened. Here's the device scan in FSUIPC's log: 187 Product= HP Wireless Keyboard Kit 187 Manufacturer= Hewlett Packard 187 Vendor=0461, Product=4E25 (Version 1.50) 187 Serial Number= Hewlett Packard 187 Product= Saitek Pro Flight Rudder Pedals 187 Manufacturer= Saitek 187 Vendor=06A3, Product=0763 (Version 1.1) 187 Serial Number= Saitek 187 Using existing joystick id: 0 187 Product= Saitek Pro Flight Yoke 187 Manufacturer= Saitek 187 Vendor=06A3, Product=0BAC (Version 3.4) 187 Serial Number= Saitek 187 Using existing joystick id: 1 So, your Rudder pedals should be joystick #0 and your Yoke should be #1. But the FSUIPC.INI file shows these assignments to the IDs: 0=HP Wireless Keyboard Kit 0.GUID={1D581E50-7763-11E5-8002-444553540000} 1=HP Wireless Keyboard Kit 1.GUID={1D5670A0-7763-11E5-8001-444553540000} 2=HP Wireless Keyboard Kit 2.GUID={1D581E50-7763-11E5-8003-444553540000} In other words, three different installations of a "wireless keyboard kit", as devices 0, 1 and 2. I canot imagine how a wireless keyboard can even be listed as a "joystick" type device, as it appears to be, let along get three different entries for itself. I assume you don't have three of them on the same, FS, PC? Please can you try running HidScanner for me --: HidScanner and show me the log from that. That may help me see the reason for the above. Then try getting proper IDs assigned to your pedals and yoke, using JoyIDs (as linked in that "fixing joysticks" thread I gave you a link to earlier. I really want to nail this sort of problem, because it should be possible for FSUIPC to handle all this automatically. It's just that I need to find out what is going wrong in cases like yours, which seem very rare. BTW, did you delete your FSUIPC4.INI at some stage, because there are no assignments to any device in the file you pasted here. At the start of the thread you said: Up until this morning, everything worked fine until I opened up P3D and nothing was happening so I assume from that you had actualy made some assignments in FSUIPC, yet there's no sign of any now. FSUIPC4 NEVER deletes them. The INI file you've posted looks like a complete default file, no personalised settings whatsoever. Pete
Thomas Greer Posted October 29, 2015 Author Report Posted October 29, 2015 Im unable too because when I try to assign an axis, i an unable too because FSUIPC is not setting it up. When i move my joystick to assign the axis, nothing happens.
Pete Dowson Posted October 29, 2015 Report Posted October 29, 2015 Im unable too because when I try to assign an axis, i an unable too because FSUIPC is not setting it up. When i move my joystick to assign the axis, nothing happens. I know, and the reasons are shown in the files you posted. But I am not asking you to assign anything at present. Please read my suggestions again. I'm sorry I keep having to repeat myself every time, you do not seem to read my messages! :sad: FIRST (to repeat) Please can you try running HidScanner for me --: HidScanner and show me the log from that. That may help me see the reason for the above. SECOND (to repeat also): Then try getting proper IDs assigned to your pedals and yoke, using JoyIDs (as linked in that "fixing joysticks" thread I gave you a link to earlier. Also, you did not bother to answer my last question, so I repeat that too: Did you delete your FSUIPC4.INI at some stage, because there are no assignments to any device in the file you pasted here. We won't get anywhere if you keep ignoring me. I'm trying to help and I desperately want to solve this issue. But I need you to help, please! Pete
Thomas Greer Posted October 29, 2015 Author Report Posted October 29, 2015 From HidScanner; ********* HidScanner, Version 2.00 by Pete Dowson ********* Device at "\\?\hid#vid_0461&pid_4e25&mi_01&col04#8&b8180dc&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0461, Product=4E25 (Version 1.50) Manufacturer= Hewlett Packard Product= HP Wireless Keyboard Kit Serial Number= HP Wireless Keyboard Kit Usage Page: FFBC Input Report Byte Length: 2 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 0 Number of InputData Indices: 255 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#saitekkeyboard#2&1e0e23ca&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=06A3, Product=5041 (Version 0.1) Manufacturer= HPduct=5041 (Version 0.1) Product= HPr= HPduct=5041 (Version 0.1) Serial Number= HPuct=5041 (Version 0.1) Device is a keyboard Usage Page: 1 Input Report Byte Length: 9 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 2 Number of InputValue Caps: 0 Number of InputData Indices: 110 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#saitekmouse#2&7354a6f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=06A3, Product=5021 (Version 0.1) Manufacturer= HPduct=5021 (Version 0.1) Product= HPr= HPduct=5021 (Version 0.1) Serial Number= HPuct=5021 (Version 0.1) Device is a mouse Usage Page: 1 Input Report Byte Length: 5 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 3 Number of InputData Indices: 8 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 5 at indices 0 -> 4 Value Wh at index 5, range -127 -> 127, using 8 bits Value Y at index 6, range -127 -> 127, using 8 bits Value X at index 7, range -127 -> 127, using 8 bits ************************************************************************** Device at "\\?\hid#vid_1b1c&pid_0a06&mi_03#8&1656656c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1B1C, Product=0A06 (Version 1.0) Manufacturer= Corsair Product= Raptor HS40 Serial Number= Raptor HS40 Usage Page: C Input Report Byte Length: 5 Output Report Byte Length: 5 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 6 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 1 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x00 at index 6, range 0 -> 255, using 8 bits ************************************************************************** Device at "\\?\hid#vid_0461&pid_4e25&mi_01&col01#8&b8180dc&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0461, Product=4E25 (Version 1.50) Manufacturer= Hewlett Packard Product= HP Wireless Keyboard Kit Serial Number= HP Wireless Keyboard Kit Usage Page: C Input Report Byte Length: 3 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 0 Number of InputData Indices: 573 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_0461&pid_4e25&mi_02#8&1855bce6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0461, Product=4E25 (Version 1.50) Manufacturer= Hewlett Packard Product= HP Wireless Keyboard Kit Serial Number= HP Wireless Keyboard Kit Device is a mouse Usage Page: 1 Input Report Byte Length: 6 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 3 Number of InputData Indices: 6 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 3 at indices 0 -> 2 Value Y at index 3, range -2047 -> 2047, using 12 bits Value X at index 4, range -2047 -> 2047, using 12 bits Value Wh at index 5, range -127 -> 127, using 8 bits ************************************************************************** Device at "\\?\hid#vid_0461&pid_4e25&mi_01&col02#8&b8180dc&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0461, Product=4E25 (Version 1.50) Manufacturer= Hewlett Packard Product= HP Wireless Keyboard Kit Serial Number= HP Wireless Keyboard Kit Usage Page: 1 Input Report Byte Length: 2 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 0 Number of InputData Indices: 3 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_06a3&pid_0763#7&fa88d7b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=06A3, Product=0763 (Version 1.1) Manufacturer= Saitek Product= Saitek Pro Flight Rudder Pedals Serial Number= Saitek Pro Flight Rudder Pedals Usage Page: 1 Input Report Byte Length: 4 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 0 Number of InputValue Caps: 3 Number of InputData Indices: 3 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value Y at index 0, range 0 -> 127, using 7 bits Value X at index 1, range 0 -> 127, using 7 bits Value R/RZ at index 2, range 0 -> 511, using 9 bits ************************************************************************** Device at "\\?\hid#vid_0461&pid_4e25&mi_00#8&2f58be9e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0461, Product=4E25 (Version 1.50) Manufacturer= Hewlett Packard Product= HP Wireless Keyboard Kit Serial Number= HP Wireless Keyboard Kit Device is a keyboard Usage Page: 1 Input Report Byte Length: 9 Output Report Byte Length: 2 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 2 Number of InputValue Caps: 0 Number of InputData Indices: 264 Number of Output Button Caps: 1 Number of Output Value Caps: 0 Number of Output Data Indices: 3 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_06a3&pid_0bac#8&2cdfde68&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=06A3, Product=0BAC (Version 3.4) Manufacturer= Saitek Product= Saitek Pro Flight Yoke Serial Number= Saitek Pro Flight Yoke Usage Page: 1 Input Report Byte Length: 10 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 6 Number of InputData Indices: 29 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 23 at indices 6 -> 28 Value Y at index 0, range 0 -> 1023, using 10 bits Value X at index 1, range 0 -> 1023, using 10 bits Value V/RY at index 2, range 0 -> 255, using 8 bits Value U/RX at index 3, range 0 -> 255, using 8 bits Value Z at index 4, range 0 -> 255, using 8 bits Value POV at index 5, range 1 -> 8, using 4 bits ************************************************************************** Device at "\\?\hid#vid_0461&pid_4e25&mi_01&col03#8&b8180dc&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0461, Product=4E25 (Version 1.50) Manufacturer= Hewlett Packard Product= HP Wireless Keyboard Kit Serial Number= HP Wireless Keyboard Kit Usage Page: FF01 Input Report Byte Length: 3 Output Report Byte Length: 0 Feature Report Byte Length: 9 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 0 Number of InputData Indices: 4096 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 1 Number of Feature Data Indices: 1 ************************************************************************** Device at "\\?\hid#saitekhotkeys#2&15d37534&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=06A3, Product=5081 (Version 0.1) Manufacturer= ^ Product= ^ Serial Number= ^ Usage Page: C Input Report Byte Length: 3 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 0 Number of InputData Indices: 669 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Ill try the JoyIDs in the morning as it is late over here. Thanks
Pete Dowson Posted October 30, 2015 Report Posted October 30, 2015 From HidScanner; Thanks. That's very useful. It's going to take me a bit of figuring out though. Your registry for HID type devices appears to be in a real mess. You have 6 entries for that HP Wireless Keyboard kit, including one as a keyboard, one as a mouse, and one as a joystick. Plus three others of completely indeterminate use. There are also corrupt entries for what it says are: a Saitek Mouse, a Saitek Keyboard and Saitek Hotkeys. The only good looking ones appear to be a Corsair Raptor HS40, whatever that is, and your Saitek pedals and yoke. However, that said, FSUIPC should have got just three devices -- the HP Wireless keyboard in its odd joystick guise -- this entry: Device at "\\?\hid#vid_0461&pid_4e25&mi_01&col02#8&b8180dc&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0461, Product=4E25 (Version 1.50) Manufacturer= Hewlett Packard Product= HP Wireless Keyboard Kit Serial Number= HP Wireless Keyboard Kit Usage Page: 1 though this entry also shows that it is a useless joystick as it has no axes or buttons. Plus the Saitek pedals and yoke, which do actually have good entries. The puzzle I have to resolve is how FSUIPC did manage correctly to derive the three devices, but got them all labelled as HP Wireless Keyboard kits: 0=HP Wireless Keyboard Kit 0.GUID={1D581E50-7763-11E5-8002-444553540000} 1=HP Wireless Keyboard Kit 1.GUID={1D5670A0-7763-11E5-8001-444553540000} 2=HP Wireless Keyboard Kit 2.GUID={1D581E50-7763-11E5-8003-444553540000} This is even odder when you consider that the Log identified them all correctly: 187 Product= HP Wireless Keyboard Kit 187 Manufacturer= Hewlett Packard 187 Vendor=0461, Product=4E25 (Version 1.50) 187 Serial Number= Hewlett Packard 187 Product= Saitek Pro Flight Rudder Pedals 187 Manufacturer= Saitek 187 Vendor=06A3, Product=0763 (Version 1.1) 187 Serial Number= Saitek 187 Using existing joystick id: 0 187 Product= Saitek Pro Flight Yoke 187 Manufacturer= Saitek 187 Vendor=06A3, Product=0BAC (Version 3.4) 187 Serial Number= Saitek 187 Using existing joystick id: 1 I'm afraid I'm out all day tomorrow (Friday), but I'll be seriously investigating this over the weekend. I hope that, should I add more logging to find out what is going on you'll be able to do more tests for me and show me more logs? I am very anxious to get this fixed as it might affect others too. Otherwise I'd be advising you to get your system tidied up by uninstalling as many of those devices, in the Device Manager (only) as possible, and re-booting. in order ot get the Registry tidied up a bit. But I'd rather you didn't do that yet so you can help me resolve the problems. Thanks, Pete
Thomas Greer Posted October 30, 2015 Author Report Posted October 30, 2015 Thanks very much Pete!! I know my friend is having the same sort of problems. Sure, I will try to co operate as much as I can.
Pete Dowson Posted October 30, 2015 Report Posted October 30, 2015 I woke up eary this morning thinking about this problem! :sad: So I got to work adding more logging. Thanks very much Pete!! I know my friend is having the same sort of problems. Sure, I will try to co operate as much as I can. I could do with seeing the INI, LOG and HidScanner results from his system too, then, please. It is puzzling me. The more clues I can get the better at present. But first, please download and copy into the Modules folder this test version; FSUIPC4947g_TEST.zip Before running FS, edit the FSUIPC4.INI file, adding these two lines to the [General] section: Debug=Please LogExtras=x200000 Then load FS. Don't let it run very long. Then show me the LOG and INI fies please. If your friend could do the same it would be useful too, thanks. Also please don't forget to run the JoyIDs program, see what that shows and see if you can fix the Joystick IDs there. Remember that JoyIDs numbers them 1-16 whereas FSUIPC uses the Windows internal IDs which are 0-15. Otherwise they correspond. Thanks. I'm off now. I may be back early enough this evening to take another look today. Pete
Thomas Greer Posted October 30, 2015 Author Report Posted October 30, 2015 I will do all that when I get home this evening after school. Thanks Pete. Thomas.
Thomas Greer Posted October 30, 2015 Author Report Posted October 30, 2015 First load and here is the log. ********* FSUIPC4, Version 4.947g by Pete Dowson ********* Reading options from "J:\P3D\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 8.0 Module base=56A10000 User Name="Thomas Greer" User Addr="greerthomas@me.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 47 System time = 30/10/2015 19:27:29 47 FLT path = "C:\Users\user\Documents\Prepar3D v3 Files\" 47 Trying J:\P3D\Modules\SimConnectP3D2.dll 172 Found it: trying to connect 219 FS path = "J:\P3D\" 359 #### Initialising Dlrectinput Axis Scanning ... 406 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0461&PID_4E25\Calibration\0" 406 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0461&PID_4E25\Calibration\1" 406 Found correct joystick Id 0 406 ... and a "GUID" value 469 ... okay, Acquired device as #0 469 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0461&PID_4E25\Calibration\0" 469 Found correct joystick Id 1 469 ... and a "GUID" value 469 ... okay, Acquired device as #1 484 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0461&PID_4E25\Calibration\0" 484 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0461&PID_4E25\Calibration\1" 484 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0461&PID_4E25\Calibration\2" 484 Found correct joystick Id 2 484 ... and a "GUID" value 484 ... okay, Acquired device as #2 547 ---------------------- Joystick Device Scan ----------------------- 547 Checking: \\?\hid#vid_0461&pid_4e25&mi_01&col04#8&b8180dc&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030} 547 Checking: \\?\hid#saitekkeyboard#2&1e0e23ca&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 547 Checking: \\?\hid#saitekmouse#2&7354a6f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 547 Checking: \\?\hid#vid_1b1c&pid_0a06&mi_03#8&1656656c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 547 Checking: \\?\hid#vid_0461&pid_4e25&mi_01&col01#8&b8180dc&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 547 Checking: \\?\hid#vid_0461&pid_4e25&mi_02#8&1855bce6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 547 Checking: \\?\hid#vid_0461&pid_4e25&mi_01&col02#8&b8180dc&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 547 Checking: \\?\hid#vid_06a3&pid_0763#7&fa88d7b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 547 Product= Saitek Pro Flight Rudder Pedals 547 Manufacturer= Saitek 547 Vendor=06A3, Product=0763 (Version 1.1) 547 Serial Number= Saitek 547 Ignoring device 3: not required DeviceInstance: 'vid_06a3&pid_0763' 547 Checking: \\?\hid#vid_0461&pid_4e25&mi_00#8&2f58be9e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 547 Checking: \\?\hid#vid_06a3&pid_0bac#8&2cdfde68&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 547 Product= Saitek Pro Flight Yoke 547 Manufacturer= Saitek 547 Vendor=06A3, Product=0BAC (Version 3.4) 547 Serial Number= Saitek 547 Ignoring device 4: not required DeviceInstance: 'vid_06a3&pid_0bac' 547 Checking: \\?\hid#vid_0461&pid_4e25&mi_01&col03#8&b8180dc&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 547 Product= HP Wireless Keyboard Kit 547 Manufacturer= Hewlett Packard 547 Vendor=0461, Product=4E25 (Version 1.50) 547 Serial Number= Hewlett Packard 547 Checking: \\?\hid#saitekhotkeys#2&15d37534&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 547 ------------------------------------------------------------------- 547 #### Completed Dlrectinput Axis Scanning 563 LogOptions=00000000 02000011 563 ------------------------------------------------------------------- 563 ------ Setting the hooks and direct calls into the simulator ------ 563 --- CONTROLS timer memory location obtained ok 563 --- SIM1 Frictions access gained 563 --- FS Controls Table located ok 563 --- Installed Mouse Macro hooks ok. 563 --- Wind smoothing fix is installed 563 --- All links okay (except older global weather setting method) 563 ------------------------------------------------------------------- 578 SimConnect_Open succeeded: waiting to check version okay 578 Trying to use SimConnect Prepar3D 77938 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.0.3.0 (SimConnect: 3.0.0.0) 77938 Initialising SimConnect data requests now 77938 FSUIPC Menu entry added 78063 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 78063 C:\Users\user\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml 78063 J:\P3D\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 79281 Deactivated for PID=9796, "chrome.exe" 82641 Memory in use: 796Mb, Avail=3300Mb
Thomas Greer Posted October 30, 2015 Author Report Posted October 30, 2015 And the ini file, [General] Debug=Please LogExtras=x200000 UpdatedByVersion=4947g History=3I07SLGGWOWAEC5ZB2WH3 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 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 FSVersionUsed="Lockheed Martin® Prepar3D® v3",3.0.3.0 SimConnectUsed=3.0.0.0 [JoyNames] AutoAssignLetters=No 0=HP Wireless Keyboard Kit 0.GUID={1D581E50-7763-11E5-8002-444553540000} 1=HP Wireless Keyboard Kit 1.GUID={1D5670A0-7763-11E5-8001-444553540000} 2=HP Wireless Keyboard Kit 2.GUID={1D581E50-7763-11E5-8003-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 [sounds] Path=J:\P3D\Sound\ Device1=Primary Sound Driver Device2=Speakers / Headphones (IDT High Definition Audio CODEC) Device3=Digital Output (S/PDIF) (IDT High Definition Audio CODEC) Device4=Speakers (3- Raptor HS40)
Pete Dowson Posted October 30, 2015 Report Posted October 30, 2015 Thank you. Sorry for the delay -- I was later getting back than I had hoped! The information in the logs/INI files is very useful, but I'm afraid it still doesn't tell me what is going wrong in your Registry. I did see one error I made, but correcting it wouldn't fix this entirely. At least I don't think so. However, I've also added some more logging. Could you download this version and try it in exactly the same way as the last test, please -- same INI entries as before and show me the same files. Download link: FSUIPC4947h_TEST.zip Then, could you also please run that JoyIDs program for me and tell me what that shows? If it is what I think it is, you MAY be able to fix it with JoyIDs, but if not I think it will need doing some uninstalling to clear the rubbish from the registry. By "uninstalling" I don't mean any real programs, just telling Windows' Device Manager to remove entries. But we'll need to discuss that after the tests above. Please also see if you can get similar logs/INI's from your friend with the same problem. I must get to the bottom of this. Pete
Thomas Greer Posted October 31, 2015 Author Report Posted October 31, 2015 Roger. Im away to rugby just now, will get it done when I get back. I have asked my friend already but he hasnt got back to me yet.
Thomas Greer Posted October 31, 2015 Author Report Posted October 31, 2015 I tried JoyID and nothing changed. Trying the new fsuipc now.
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