Jump to content
The simFlight Network Forums

TatoBean

Members
  • Posts

    5
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location
    Chicago, IL

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

TatoBean's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Sorry for the delayed response. Reinstall didn't exactly go smoothly as my anti-virus FREAKED out, life and work got in the way, then my real airplane broke, got stuck in Virginia, I've just had a string of bad luck lately. However! The reinstall worked! All controllers are recognized, the computer is faster (imagine that) it likes my complex sceneries again. I think you were right Pete, just lots of really messed up stuff over the years that needed to be cleaned out. (Sounds like my attic) Thanks for the help!
  2. So I've been working on backing up my files preparing for the reinstall. I think I've got everything I need to put on the external drive to survive this. Is there any advice you'd give to a first timer before they dive into this?
  3. Yes, sorry the uninstalling of the devices. I did delete the CH software. Of the two options you have given me I feel like a complete reinstall of windows is probably the better one as this is a fairly old machine and it would probably fix other problems I don't know I have. But having never done it before I am rather concerned about doing irreparable damage by botching the install.
  4. That was my impression too! Good to know I'm not completely crazy! Nope should just be the 1. I did try using JoyID to fix the problem but it did nothing. Alas I tried the nuclear option and still no luck. My CH yoke, Throttle Quad, and pedals, As well as my Logitech stick all work fine but unfortunately it is now not seeing input from the Pro Throttle. I've included the new .log .ini. and JoyScan files for round 2. Again finding identical GUID's and the .ini file skipping a controller ID number.FSUIPC4.ini Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk? ,,, HIDscanning completed N, x00, x046D, xC215, , -1, -1, 0, {NULL}, {NULL}, {9F156DC0-B2D7-11E1-8001-444553540000}, Y, N N, x00, x068E, x00F1, , -1, -1, 0, {NULL}, {NULL}, {731BC210-4F6D-11EA-8001-444553540000}, Y, N N, x00, x068E, x00F2, , -1, -1, 0, {NULL}, {NULL}, {9F156DC0-B2D7-11E1-8001-444553540000}, Y, N N, x00, x068E, x00FA, , -1, -1, 0, {NULL}, {NULL}, {2BF6EAF0-6D02-11E1-8002-444553540000}, Y, N N, x00, x068E, x00FF, , -1, -1, 0, {NULL}, {NULL}, {2BF6EAF0-6D02-11E1-8003-444553540000}, Y, N ,,, REGscanning completed N, x00, x046D, xC215, Logitech Extreme 3D, -1, 3, 0, {NULL}, {9F156DC0-B2D7-11E1-8001-444553540000}, {9F156DC0-B2D7-11E1-8001-444553540000}, Y, Y N, x00, x068E, x00F1, CH PRO THROTTLE USB, -1, 0, 0, {NULL}, {2BF6EAF0-6D02-11E1-8001-444553540000}, {NULL}, N, Y N, x00, x068E, x00F2, CH PRO PEDALS USB, -1, 3, 0, {NULL}, {9F156DC0-B2D7-11E1-8001-444553540000}, {9F156DC0-B2D7-11E1-8001-444553540000}, Y, Y N, x00, x068E, x00F2, CH PRO PEDALS USB, -1, 0, 0, {NULL}, {2BF6EAF0-6D02-11E1-8001-444553540000}, {NULL}, N, Y N, x00, x068E, x00FA, CH THROTTLE QUADRANT, -1, 1, 0, {NULL}, {2BF6EAF0-6D02-11E1-8002-444553540000}, {2BF6EAF0-6D02-11E1-8002-444553540000}, Y, Y N, x00, x068E, x00FF, CH FLIGHT SIM YOKE USB, -1, 4, 0, {NULL}, {2BF6EAF0-6D02-11E1-8003-444553540000}, {2BF6EAF0-6D02-11E1-8003-444553540000}, Y, Y ,,, User settings imported N, x00, x046D, xC215, Logitech Extreme 3D, -1, 3, 0, {NULL}, {9F156DC0-B2D7-11E1-8001-444553540000}, {9F156DC0-B2D7-11E1-8001-444553540000}, Y, Y N, x00, x068E, x00F1, CH PRO THROTTLE USB, -1, 0, 0, {NULL}, {2BF6EAF0-6D02-11E1-8001-444553540000}, {NULL}, N, Y N, x00, x068E, x00F2, CH PRO PEDALS USB, -1, 3, 0, {NULL}, {9F156DC0-B2D7-11E1-8001-444553540000}, {9F156DC0-B2D7-11E1-8001-444553540000}, Y, Y N, x00, x068E, x00F2, CH PRO PEDALS USB, -1, 0, 0, {NULL}, {2BF6EAF0-6D02-11E1-8001-444553540000}, {NULL}, N, Y N, x00, x068E, x00FA, CH THROTTLE QUADRANT, -1, 1, 0, {NULL}, {2BF6EAF0-6D02-11E1-8002-444553540000}, {2BF6EAF0-6D02-11E1-8002-444553540000}, Y, Y N, x00, x068E, x00FF, CH FLIGHT SIM YOKE USB, -1, 4, 0, {NULL}, {2BF6EAF0-6D02-11E1-8003-444553540000}, {2BF6EAF0-6D02-11E1-8003-444553540000}, Y, Y ,,, Values matched and decided Y, x1E, x046D, xC215, Logitech Extreme 3D, 3, 3, 0, {NULL}, {9F156DC0-B2D7-11E1-8001-444553540000}, {9F156DC0-B2D7-11E1-8001-444553540000}, Y, Y (Y), x19, x068E, x00F1, CH PRO THROTTLE USB, 0, 0, 0, {NULL}, {2BF6EAF0-6D02-11E1-8001-444553540000}, {NULL}, N, Y Y, x1E, x068E, x00F2, CH PRO PEDALS USB, 3, 3, 0, {NULL}, {9F156DC0-B2D7-11E1-8001-444553540000}, {9F156DC0-B2D7-11E1-8001-444553540000}, Y, Y (Y), x19, x068E, x00F2, CH PRO PEDALS USB, 0, 0, 0, {NULL}, {2BF6EAF0-6D02-11E1-8001-444553540000}, {NULL}, N, Y Y, x1E, x068E, x00FA, CH THROTTLE QUADRANT, 1, 1, 0, {NULL}, {2BF6EAF0-6D02-11E1-8002-444553540000}, {2BF6EAF0-6D02-11E1-8002-444553540000}, Y, Y Y, x1E, x068E, x00FF, CH FLIGHT SIM YOKE USB, 4, 4, 0, {NULL}, {2BF6EAF0-6D02-11E1-8003-444553540000}, {2BF6EAF0-6D02-11E1-8003-444553540000}, Y, Y ********* FSUIPC4, Version 4.974 (24th February 2018) by Pete Dowson ********* Windows 7 Home Premium 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1) fsx.exe version = 10.0.62615.0 Running inside FSX Steam Edition on Windows 7 Module base=164A0000 User Name="Andrea Schultz" User Addr="andreanschultz@hotmail.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 0 System time = 04/05/2020 20:23:49 0 FLT path = "C:\Users\Andrea\Documents\Flight Simulator X Files\" 15 ------ Module Version Check ------ 15 acontain.dll: 10.0.62615.0 15 api.dll: 10.0.62615.0 15 controls.dll: 10.0.62615.0 31 fs-traffic.dll: 10.0.62615.0 31 G3D.dll: 10.0.62615.0 31 language.dll: 10.0.62615.0 31 sim1.dll: 10.0.62615.0 31 visualfx.dll: 10.0.62615.0 47 weather.dll: 10.0.62615.0 47 window.dll: 10.0.62615.0 47 ---------------------------------- 109 Trying to connect to SimConnect Steam ... 125 FS path = "C:\Program Files (x86)\Steam\steamapps\common\FSX\" 546 ---------------------- Joystick Device Scan ----------------------- 546 Product= Logitech Extreme 3D 546 Manufacturer= Logitech 546 Vendor=046D, Product=C215 (Version 2.4) 795 GUIDs returned for product: VID_046D&PID_C215: 795 GUID= {9F156DC0-B2D7-11E1-8001-444553540000} 795 Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X1023,Y1023,Z255 811 Product= CH PRO THROTTLE USB 811 Manufacturer= CH Products 827 Vendor=068E, Product=00F1 (Version 0.1) 827 GUIDs returned for product: VID_068E&PID_00F1: 827 GUID= {731BC210-4F6D-11EA-8001-444553540000} 827 Details: Btns=19, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 827 Product= CH PRO PEDALS USB 827 Manufacturer= CH PRODUCTS 827 Vendor=068E, Product=00F2 (Version 0.0) 827 Product= CH THROTTLE QUADRANT 827 Manufacturer= CH PRODUCTS 827 Vendor=068E, Product=00FA (Version 0.0) 827 GUIDs returned for product: VID_068E&PID_00FA: 827 GUID= {2BF6EAF0-6D02-11E1-8002-444553540000} 827 Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U165,V255,X255,Y252,Z255 827 Product= CH FLIGHT SIM YOKE USB 827 Manufacturer= CH PRODUCTS 827 Vendor=068E, Product=00FF (Version 0.0) 827 GUIDs returned for product: VID_068E&PID_00FF: 827 GUID= {2BF6EAF0-6D02-11E1-8003-444553540000} 827 Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X255,Y255,Z255 827 ------------------------------------------------------------------- 858 Device acquired for use: 858 Joystick ID = 3 (Registry okay) 858 3=Logitech Extreme 3D 858 3.GUID={9F156DC0-B2D7-11E1-8001-444553540000} 858 Device acquired for use: 858 Joystick ID = 0 (Registry okay) 858 0=CH PRO THROTTLE USB 858 0.GUID={2BF6EAF0-6D02-11E1-8001-444553540000} 858 Device acquired for use: 858 Joystick ID = 3 (Registry okay) 858 3=CH PRO PEDALS USB 858 3.GUID={9F156DC0-B2D7-11E1-8001-444553540000} 858 Device acquired for use: 858 Joystick ID = 0 (Registry okay) 858 0=CH PRO PEDALS USB 858 0.GUID={2BF6EAF0-6D02-11E1-8001-444553540000} 873 Device acquired for use: 873 Joystick ID = 1 (Registry okay) 873 1=CH THROTTLE QUADRANT 873 1.GUID={2BF6EAF0-6D02-11E1-8002-444553540000} 873 Device acquired for use: 873 Joystick ID = 4 (Registry okay) 873 4=CH FLIGHT SIM YOKE USB 873 4.GUID={2BF6EAF0-6D02-11E1-8003-444553540000} 873 ------------------------------------------------------------------- 889 LogOptions=00000000 00000001 889 ------------------------------------------------------------------- 889 ------ Setting the hooks and direct calls into the simulator ------ 889 --- CONTROLS timer memory location obtained ok 889 --- SIM1 Frictions access gained 889 --- FS Controls Table located ok 889 --- Installed Mouse Macro hooks ok. 889 --- Wind smoothing fix is fully installed 889 --- SimConnect intercept for texts and menus option is off 889 --- All links checked okay 889 ------------------------------------------------------------------- 889 SimConnect_Open succeeded: waiting to check version okay 889 Trying to use SimConnect Steam 889 Opened separate AI Traffic client okay 5117 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 5117 Initialising SimConnect data requests now 5117 FSUIPC Menu entry added 5195 C:\Users\Andrea\Documents\Flight Simulator X Files\Default Flight.FLT 5195 C:\Program Files (x86)\Steam\SteamApps\common\FSX\SimObjects\Airplanes\C172\Cessna172SP.air 29172 Weather Mode now = Theme 36005 User Aircraft ID 1 supplied, now being used 36005 Aircraft loaded: running normally now ... 204018 System time = 04/05/2020 20:27:13, Simulator time = 20:24:18 (01:24Z) 204033 Aircraft="Cessna Skyhawk 172SP" 207466 Starting everything now ... 207528 ASN active function link set 207528 Ready for ActiveSky WX radar with additional data 208776 Advanced Weather Interface Enabled 340113 === Closing session: waiting for DLLStop to be called ... 356337 === DLLStop called ... 356337 === Closing external processes we started ... 357336 === About to kill any Lua plug-ins still running ... 357492 === Closing global Lua thread 358490 === About to kill my timers ... 358693 === Restoring window procs ... 358693 === Unloading libraries ... 358693 === stopping other threads ... 358693 === ... Memory checking ... 358693 === ... Button scanning ... 358786 === ... Axis scanning ... 358880 === Releasing joystick devices ... 358880 === Freeing macro memory 358880 === Removing any offset overrides 358880 === Clearing any displays left 358880 === NOTE: not calling SimConnect_Close ... 358880 === AI slots deleted! 358880 === Freeing button memory ... 358880 === Closing my Windows ... 358880 === Freeing FS libraries ... 359894 === Closing devices ... 359894 === Closing the Log ... Bye Bye! ... 359894 System time = 04/05/2020 20:29:49, Simulator time = 20:24:42 (01:24Z) 359894 *** FSUIPC log file being closed Minimum frame rate was 45.1 fps, Maximum was 76.8 fps Minimum available memory recorded was 3036Mb Average frame rate for running time of 21 secs = 38.0 fps Maximum AI traffic for session was 100 aircraft Memory managed: 12 Allocs, 12 Freed ********* FSUIPC Log file closed ***********
  5. I have searched high and low to find a solution to my problem but have found similar ones but none that list the solution. For some reason FSUIPC is not recognizing inputs from various controllers, which controller has varied depending on what I've tried to change to attempt to fix the problem. Currently it is not recognizing my CH Throttle Quadrant, though in the past it's been the CH Pedals, and CH Pro Throttle. The only constant is that it doesn't seem to like CH products. I have noticed in my INI that it skips a number going from 0. to 2. 3. and though I'm getting data from 4/5 controllers It's only listing 3 in the INI. Also in the joyscan.csv file it is showing multiple controllers with identical GUID's which I thought was not possible. This could be my problem, but I don't know how to fix it. Thanks Tato FSUIPC4.ini FSUIPC4.JoyScan.csv FSUIPC4.log
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.