tananarive Posted May 16, 2017 Report Share Posted May 16, 2017 Hello I have 3 MCP Thrustmaster, an MCP is no longer recognized by FSUIPC, it is recognized by P3D Command. The other two are as well as my GoFlight. Link to comment Share on other sites More sharing options...
Thomas Richter Posted May 16, 2017 Report Share Posted May 16, 2017 Hi, as always a FSUIPC4.log file would help. Just copy and paste the FULL content to your message. Thomas Link to comment Share on other sites More sharing options...
tananarive Posted May 16, 2017 Author Report Share Posted May 16, 2017 ********* FSUIPC4, Version 4.966n (8th May 2017) by Pete Dowson ********* Windows 10 Pro 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0) Prepar3D.exe version = 3.4.22.19868 Reading options from "E:\lockheed Martin\P3D_Externes\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 10 Module base=59B20000 User Name="Michel Bergues" User Addr="berguesmichel@free.fr" FSUIPC4 Key is provided WideFS7 Key is provided 0 System time = 16/05/2017 20:32:34 16 FLT UNC path = "\\CORSAIR\Documents\Prepar3D v3 Files\" 16 ------ Module Version Check ------ 16 acontain.dll: 3.4.22.19868 16 api.dll: 3.4.22.19868 16 controls.dll: 3.4.22.19868 16 fs-traffic.dll: 3.4.22.19868 16 G3D.dll: 3.4.22.19868 16 language.dll: 3.4.22.19868 16 sim1.dll: 3.4.22.19868 16 visualfx.dll: 3.4.22.19868 16 weather.dll: 3.4.22.19868 16 window.dll: 3.4.22.19868 16 ---------------------------------- 16 Trying E:\lockheed Martin\P3D_Externes\Modules\SimConnectP3D3.dll 16 Found it: trying to connect 31 FS UNC path = "\\CORSAIR\Lockheed Martin\P3D_Externes\" 31 ---------------------- Joystick Device Scan ----------------------- 31 Product= Throttle - HOTAS Warthog 31 Manufacturer= Thrustmaster 31 Vendor=044F, Product=0404 (Version 1.0) 1984 GUIDs returned for product: VID_044F&PID_0404: 1984 GUID= {7731A390-81BE-11E6-8011-444553540000} 1984 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R16383,U1023,V0,X1023,Y853,Z16383 1984 Product= BU0836 Interface 1984 Manufacturer= Leo Bodnar 1984 Serial Number= A02087 1984 Vendor=16C0, Product=05B5 (Version 1.25) 1984 GUIDs returned for product: VID_16C0&PID_05B5: 1984 GUID= {AE567780-830B-11E6-8004-444553540000} 1984 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U289,V741,X618,Y0,Z0 1984 GUID= {AE567780-830B-11E6-8003-444553540000} 1984 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X566,Y866,Z796 1984 Product= F16 MFD 1 1984 Manufacturer= Thrustmaster 1984 Vendor=044F, Product=B351 (Version 1.0) 1984 GUIDs returned for product: VID_044F&PID_B351: 1984 GUID= {A94D6380-8337-11E6-8001-444553540000} 1984 Details: Btns=28, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 1984 GUID= {F5BA8490-04B6-11E7-8001-444553540000} 1984 Details: Btns=28, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 1984 GUID= {F5AA1330-8338-11E6-8001-444553540000} 1984 Details: Btns=28, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 2328 Product= F16 MFD 1 2328 Manufacturer= Thrustmaster 2328 Vendor=044F, Product=B351 (Version 1.0) 2328 Product= Joystick - HOTAS Warthog 2328 Manufacturer= Thustmaster 2328 Vendor=044F, Product=0402 (Version 1.0) 2328 GUIDs returned for product: VID_044F&PID_0402: 2328 GUID= {FFF17B30-8310-11E6-8005-444553540000} 2328 Details: Btns=19, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X65535,Y65535,Z0 2328 Product= TQ6 2328 Manufacturer= GoFlight 2328 Serial Number= 00080 7 2328 Vendor=09F3, Product=0200 (Version 2.0) 2328 GUIDs returned for product: VID_09F3&PID_0200: 2328 GUID= {64A44210-8280-11E6-8003-444553540000} 2328 Details: Btns=4, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R227,U225,V221,X222,Y224,Z221 2328 Product= BU0836 Interface 2328 Manufacturer= Leo Bodnar 2344 Serial Number= A05615 2344 Vendor=16C0, Product=05B5 (Version 1.33) 2344 Product= F16 MFD 1 2344 Manufacturer= Thrustmaster 2344 Vendor=044F, Product=B351 (Version 1.0) 2344 ------------------------------------------------------------------- 2375 Device acquired for use: 2375 Joystick ID = 3 (Registry okay) 2375 3=Throttle - HOTAS Warthog 2375 3.GUID={7731A390-81BE-11E6-8011-444553540000} 2375 Device acquired for use: 2375 Joystick ID = 1 (Registry okay) 2375 1=BU0836 Interface 2375 1.GUID={AE567780-830B-11E6-8004-444553540000} 2375 Device acquired for use: 2375 Joystick ID = 2 (Registry okay) 2375 2=BU0836 Interface 2375 2.GUID={AE567780-830B-11E6-8003-444553540000} 2375 Device acquired for use: 2375 Joystick ID = 5 (Registry okay) 2375 5=F16 MFD 1 2375 5.GUID={A94D6380-8337-11E6-8001-444553540000} 2375 Device acquired for use: 2375 Joystick ID = 6 (Registry okay) 2375 6=F16 MFD 1 2375 6.GUID={F5BA8490-04B6-11E7-8001-444553540000} 2375 Device acquired for use: 2375 Joystick ID = 4 (Registry okay) 2375 4=Joystick - HOTAS Warthog 2375 4.GUID={FFF17B30-8310-11E6-8005-444553540000} 2375 Device acquired for use: 2375 Joystick ID = 0 (Registry okay) 2375 0=GoFlight GF-TQ6 Throttle System 2375 0.GUID={64A44210-8280-11E6-8003-444553540000} 2375 ------------------------------------------------------------------- 2422 LogOptions=00000000 00000005 2422 ------------------------------------------------------------------- 2422 ------ Setting the hooks and direct calls into the simulator ------ 2422 --- CONTROLS timer memory location obtained ok 2422 --- SIM1 Frictions access gained 2422 --- FS Controls Table located ok 2422 --- Installed Mouse Macro hooks ok. 2422 --- Wind smoothing fix is installed 2422 --- SimConnect intercept for texts and menus option is off 2422 --- All links okay (except older global weather setting method) 2422 ------------------------------------------------------------------- 2422 SimConnect_Open succeeded: waiting to check version okay 2422 Trying to use SimConnect Prepar3D 2422 Opened separate AI Traffic client okay 3750 WRITE0[6004] 330A, 2 bytes: EC 03 .. 36938 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.22.19868 (SimConnect: 3.4.0.0) 36938 ### Changed Lua thread affinity mask from 14 [x0E] to 4 [x04] 36938 Initialising SimConnect data requests now 36938 FSUIPC Menu entry added 36938 LUA.0: beginning "E:\lockheed Martin\P3D_Externes\Modules\ipcInit.lua" 36953 LUA.1: server: waiting for client connection... 36969 \\CORSAIR\Users\ADMINCORSAIR\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml 36969 \\CORSAIR\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 48156 Weather Mode now = Theme 49656 \\CORSAIR\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\PMDG 777-300ER\B777-300ER.air 49656 \\CORSAIR\Documents\Prepar3D v3 Files\LFLL B773 36L en route.fxml 49672 WRITE0[6004] 330A, 2 bytes: 4C 04 L. 107688 User Aircraft ID 1 supplied, now being used 109875 Aircraft loaded: running normally now ... 109875 System time = 16/05/2017 20:34:24, Simulator time = 14:52:27 (13:52Z) 109891 Aircraft="PMDG 777-300ER PMDG House" 113484 WRITE0[6004] 7B91, 1 bytes: 00 . 113703 Starting everything now ... 113781 ASN active function link set 113781 Ready for ASN WX radar 115813 Using "C:\Program Files (x86)\GoFlight\GFDEV.DLL", version 2.2.7.0 115813 GoFlight GFP8 detected: 2 devices 115813 GoFlight GFT8 detected: 6 devices 115813 GoFlight GFLGT detected: 1 device 115813 GoFlight GF166 detected: 2 devices 115813 GoFlight GFRP48 detected: 3 devices 115813 GoFlight GF46 detected: 1 device 115813 GoFlight GFTQ6 detected: 1 device 115813 GoFlight GFMCPPRO detected: 1 device 115813 GoFlight GFEFIS detected: 2 devices 117172 Advanced Weather Interface Enabled 167047 Sim stopped: average frame rate for last 59 secs = 35.4 fps 167047 Max AI traffic was 0 aircraft 198484 === Closing session: waiting for DLLStop to be called ... 228781 === DLLStop called ... 228781 === Closing external processes we started ... 229781 === About to kill any Lua plug-ins still running ... 229938 Lua threads being terminated: 229938 0 = "E:\lockheed Martin\P3D_Externes\Modules\DynamicFriction.lua" 230094 LUA: "E:\lockheed Martin\P3D_Externes\Modules\DynamicFriction.lua": killed 230094 1 = "E:\lockheed Martin\P3D_Externes\Modules\gitlua.lua" 230500 LUA: "E:\lockheed Martin\P3D_Externes\Modules\gitlua.lua": killed 230500 === Closing global Lua thread 231500 === About to kill my timers ... 231703 === Restoring window procs ... 231703 === Unloading libraries ... 231703 === stopping other threads ... 231703 === ... Memory checking ... 231703 === ... Button scanning ... 232172 === ... Axis scanning ... 232266 === Releasing joystick devices ... 232266 === Freeing macro memory 232266 === Removing any offset overrides 232266 === Closing all WideFS threads 234641 === Clearing any displays left 234641 === Calling SimConnect_Close ... 235250 === SimConnect_Close done! 235250 === AI slots deleted! 235250 === Freeing button memory ... 235250 === Closing my Windows ... 235250 === Freeing FS libraries ... 236250 === Closing devices ... 236250 === Closing the Log ... Bye Bye! ... 236250 System time = 16/05/2017 20:36:30, Simulator time = 14:53:23 (13:53Z) 236250 *** FSUIPC log file being closed Minimum frame rate was 23.3 fps, Maximum was 60.9 fps Minimum available memory recorded was 1416Mb Average frame rate for running time of 61 secs = 35.7 fps Maximum AI traffic for session was 0 aircraft Memory managed: 30 Allocs, 29 Freed ********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
Thomas Richter Posted May 21, 2017 Report Share Posted May 21, 2017 Hi, did you try to connect the missing one on a different USB port, not swapping with the recognised ones? Thomas Link to comment Share on other sites More sharing options...
tananarive Posted May 22, 2017 Author Report Share Posted May 22, 2017 Hello I connected the MCP to another HUB, I plugged in another MCP, handed the first still not recognized by FSUIPC. Link to comment Share on other sites More sharing options...
Pete Dowson Posted May 25, 2017 Report Share Posted May 25, 2017 On 5/22/2017 at 3:20 PM, tananarive said: Hello I connected the MCP to another HUB, I plugged in another MCP, handed the first still not recognized by FSUIPC. MCPs (Main Control Panels) are not normal joystick type devices, because they have displays and dials. The version of FSUIPC you are using produces a Joy Scan results file (type csv) -- please show that too, as requested in the text in the place you got that version of FSUIPC from. A HidScanner log might also be useful. it would show what "type" of device those MCPs identify themselves as. HidScanner is available in the Useful Additional Programs thread in Download Links. Pete Link to comment Share on other sites More sharing options...
tananarive Posted May 30, 2017 Author Report Share Posted May 30, 2017 Hello, The joyscan of my installation. Good?, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk? ,,, HIDscanning completed N, x044F, x0404, , -1, -1, 0, {NULL}, {NULL}, {7731A390-81BE-11E6-8011-444553540000}, Y, N N, x16C0, x05B5, , -1, -1, 0, {NULL}, {NULL}, {AE567780-830B-11E6-8004-444553540000}, Y, N N, x16C0, x05B5, , -1, -1, 0, {NULL}, {NULL}, {AE567780-830B-11E6-8003-444553540000}, Y, N N, x044F, xB351, , -1, -1, 0, {NULL}, {NULL}, {A94D6380-8337-11E6-8001-444553540000}, Y, N N, x044F, xB351, , -1, -1, 0, {NULL}, {NULL}, {F5BA8490-04B6-11E7-8001-444553540000}, Y, N N, x044F, xB351, , -1, -1, 0, {NULL}, {NULL}, {F5AA1330-8338-11E6-8001-444553540000}, Y, N N, x044F, x0402, , -1, -1, 0, {NULL}, {NULL}, {FFF17B30-8310-11E6-8005-444553540000}, Y, N N, x09F3, x0200, , -1, -1, 0, {NULL}, {NULL}, {64A44210-8280-11E6-8003-444553540000}, Y, N ,,, REGscanning completed N, x044F, x0404, Throttle - HOTAS Warthog, -1, 3, 0, {NULL}, {7731A390-81BE-11E6-8011-444553540000}, {7731A390-81BE-11E6-8011-444553540000}, Y, Y N, x16C0, x05B5, BU0836 Interface, -1, 1, 1, {NULL}, {AE567780-830B-11E6-8004-444553540000}, {AE567780-830B-11E6-8004-444553540000}, Y, Y N, x16C0, x05B5, BU0836 Interface, -1, 2, 0, {NULL}, {AE567780-830B-11E6-8003-444553540000}, {AE567780-830B-11E6-8003-444553540000}, Y, Y N, x044F, xB351, F16 MFD 1, -1, 5, 0, {NULL}, {A94D6380-8337-11E6-8001-444553540000}, {A94D6380-8337-11E6-8001-444553540000}, Y, N N, x044F, xB351, F16 MFD 1, -1, 6, 2, {NULL}, {F5BA8490-04B6-11E7-8001-444553540000}, {F5BA8490-04B6-11E7-8001-444553540000}, Y, N N, x044F, xB351, F16 MFD 1, -1, 7, 1, {NULL}, {F5AA1330-8338-11E6-8001-444553540000}, {F5AA1330-8338-11E6-8001-444553540000}, Y, N N, x044F, xB351, F16 MFD 1, -1, 5, 3, {NULL}, {2B613890-26B4-11E7-8001-444553540000}, {NULL}, N, N N, x044F, x0402, Joystick - HOTAS Warthog, -1, 4, 0, {NULL}, {FFF17B30-8310-11E6-8005-444553540000}, {FFF17B30-8310-11E6-8005-444553540000}, Y, Y N, x09F3, x0200, GoFlight GF-TQ6 Throttle System, -1, 0, 0, {NULL}, {64A44210-8280-11E6-8003-444553540000}, {64A44210-8280-11E6-8003-444553540000}, Y, Y ,,, User settings imported N, x044F, x0404, Throttle - HOTAS Warthog, 3, 3, 0, {7731A390-81BE-11E6-8011-444553540000}, {7731A390-81BE-11E6-8011-444553540000}, {7731A390-81BE-11E6-8011-444553540000}, Y, Y N, x16C0, x05B5, BU0836 Interface, 1, 1, 1, {AE567780-830B-11E6-8004-444553540000}, {AE567780-830B-11E6-8004-444553540000}, {AE567780-830B-11E6-8004-444553540000}, Y, Y N, x16C0, x05B5, BU0836 Interface, 2, 2, 0, {AE567780-830B-11E6-8003-444553540000}, {AE567780-830B-11E6-8003-444553540000}, {AE567780-830B-11E6-8003-444553540000}, Y, Y N, x044F, xB351, F16 MFD 1, 5, 5, 0, {A94D6380-8337-11E6-8001-444553540000}, {A94D6380-8337-11E6-8001-444553540000}, {A94D6380-8337-11E6-8001-444553540000}, Y, N N, x044F, xB351, F16 MFD 1, 6, 6, 2, {F5BA8490-04B6-11E7-8001-444553540000}, {F5BA8490-04B6-11E7-8001-444553540000}, {F5BA8490-04B6-11E7-8001-444553540000}, Y, N N, x044F, xB351, F16 MFD 1, -1, 7, 1, {NULL}, {F5AA1330-8338-11E6-8001-444553540000}, {F5AA1330-8338-11E6-8001-444553540000}, Y, N N, x044F, xB351, F16 MFD 1, -1, 5, 3, {NULL}, {2B613890-26B4-11E7-8001-444553540000}, {NULL}, N, N N, x044F, x0402, Joystick - HOTAS Warthog, 4, 4, 0, {FFF17B30-8310-11E6-8005-444553540000}, {FFF17B30-8310-11E6-8005-444553540000}, {FFF17B30-8310-11E6-8005-444553540000}, Y, Y N, x09F3, x0200, GoFlight GF-TQ6 Throttle System, 0, 0, 0, {64A44210-8280-11E6-8003-444553540000}, {64A44210-8280-11E6-8003-444553540000}, {64A44210-8280-11E6-8003-444553540000}, Y, Y ,,, Values matched and decided Y, x044F, x0404, Throttle - HOTAS Warthog, 3, 3, 0, {7731A390-81BE-11E6-8011-444553540000}, {7731A390-81BE-11E6-8011-444553540000}, {7731A390-81BE-11E6-8011-444553540000}, Y, Y Y, x16C0, x05B5, BU0836 Interface, 1, 1, 1, {AE567780-830B-11E6-8004-444553540000}, {AE567780-830B-11E6-8004-444553540000}, {AE567780-830B-11E6-8004-444553540000}, Y, Y Y, x16C0, x05B5, BU0836 Interface, 2, 2, 0, {AE567780-830B-11E6-8003-444553540000}, {AE567780-830B-11E6-8003-444553540000}, {AE567780-830B-11E6-8003-444553540000}, Y, Y (Y), x044F, xB351, F16 MFD 1, 5, 5, 0, {A94D6380-8337-11E6-8001-444553540000}, {A94D6380-8337-11E6-8001-444553540000}, {A94D6380-8337-11E6-8001-444553540000}, Y, N (Y), x044F, xB351, F16 MFD 1, 6, 6, 2, {F5BA8490-04B6-11E7-8001-444553540000}, {F5BA8490-04B6-11E7-8001-444553540000}, {F5BA8490-04B6-11E7-8001-444553540000}, Y, N N, x044F, xB351, F16 MFD 1, -1, 7, 1, {NULL}, {F5AA1330-8338-11E6-8001-444553540000}, {F5AA1330-8338-11E6-8001-444553540000}, Y, N N, x044F, xB351, F16 MFD 1, -1, 5, 3, {NULL}, {2B613890-26B4-11E7-8001-444553540000}, {NULL}, N, N Y, x044F, x0402, Joystick - HOTAS Warthog, 4, 4, 0, {FFF17B30-8310-11E6-8005-444553540000}, {FFF17B30-8310-11E6-8005-444553540000}, {FFF17B30-8310-11E6-8005-444553540000}, Y, Y (Y), x09F3, x0200, GoFlight GF-TQ6 Throttle System, 0, 0, 0, {64A44210-8280-11E6-8003-444553540000}, {64A44210-8280-11E6-8003-444553540000}, {64A44210-8280-11E6-8003-444553540000}, Y, Y Link to comment Share on other sites More sharing options...
Pete Dowson Posted May 30, 2017 Report Share Posted May 30, 2017 7 hours ago, tananarive said: The joyscan of my installation. Okay. The MFD devices return 4 entries each, two of which have good values, though no response to normal Joystick reads. I think those need a driver. Are these your MCPs, or do you really actually mean "MCP" not "MFD"? Because no devices calling themselved Joystick types register. Where's the HidScanner log file? Pete Link to comment Share on other sites More sharing options...
tananarive Posted June 27, 2017 Author Report Share Posted June 27, 2017 Hello, My MFD that no longer works with P3Dv3 works. But it does not work with P3Dv4. Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 27, 2017 Report Share Posted June 27, 2017 Are you assigning in FSUIPC? If so, what versions of FSUIPC are you using in each? The currently supported versions are 4.969 and 5.103. Pete Link to comment Share on other sites More sharing options...
tananarive Posted June 28, 2017 Author Report Share Posted June 28, 2017 Hello, For the version P3DV3 it is the 4.966c For the P3DV4 version it is 5.103, I have it again download and installed. The three Thrustmaster MFDs work in both versions of P3D. Thank you very much. Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 28, 2017 Report Share Posted June 28, 2017 16 minutes ago, tananarive said: For the version P3DV3 it is the 4.966c That is out of date and not supported. Please update to 4.969. 16 minutes ago, tananarive said: For the P3DV4 version it is 5.103, Please do this: Add these two lines to the [General] section of FSUIPC5.INI: Debug=Please LogExtras=x200000 Then run P3D4. Check that your devices are still not seen in FSUIPC then close P3D4. Show me these files, all from the P3D4 Modules folder. You might need to ZIP them to make them small enough if you intend to attach: FSUIPC5.LOG FSUIPC5.INI FSUIPC5.JoyScan.csv Pete Link to comment Share on other sites More sharing options...
tananarive Posted June 28, 2017 Author Report Share Posted June 28, 2017 The three MFDs work in P3DV3 and P3DV4, Joy # 5, Joy # 6, Joy # 7. Thank you 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