Jump to content
The simFlight Network Forums

wkrp2005

Members
  • Posts

    27
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Colorado

Recent Profile Visitors

844 profile views

wkrp2005's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Did you tweak your dead zones in Windows calibration? I think that's what did it for me. Otherwise, I'm out of ideas.. Sorry.
  2. See my thread a few days back: http://forum.simflight.com/topic/81161-saitek-throttle-issues-again/ First off, remove any Saitek drivers. Then, Try this recalibration fix To recalibrate, first unplug the quadrant. Go to start/run and type regedit. The registry editor will have a list of folders on the left hand side. Go down into the following folders in order. HKEY_LOCAL_MACHINE (CURRENT_USER if on VISTA) System CurrentControlSet Control Media Properties Private Properties Direct Input Inside the Direct Input folder, delete any folder that begins VID_06A3. Once done, close the editor. Plug the quadrnat back in and move all the axes through their full range of movement 4 times. Now go to control panel/game controllers/properties to see if everything is ok on the test screen. Finally, what fixed mine was to do what I did in the last post of my initial thread. It has to do both with the Saitek registry and also the dead zones. Good luck
  3. Thanks for feedback Pete. To close the loop, the axis were not reversed as far as FSX goes. I ended up unplugging the yoke/throttle, rebooted, used CCleaner to remove any spurious registry entries, rebooted, plugged in the yoke/throttle, calibrated via Win7 and I opened up the dead zone in the center and tightened up the dead zone on the outside edges and re-tried to assign/calibrate in FSUIPC and everything is fine now. Fingers crossed of course... Thanks again. Keith
  4. Hi Pete, You help me a few days ago regarding possible duplicate assignments which I got sorted out by disabling controllers in FSX. In the process of trying to sort out a different issue with my GoFlight MCP displays ( I wasn't plugged into a powered USB hub) all of the sudden my Saitek yoke/throttle developed an odd behavior. Namely, at ready for takeoff, once I advance the throttle or move the spoiler lever the reversers come on and the spoilers remain raised. Long story short, I've been around the block several times WRT Saitek registry issues and have removed those. The yoke/throttle use MS default drivers. When I try to calibrate the axes in Win7 it appears the Axes XYZ values are highest with the levers at min and lowest when levers are highest. This seems backwards. Also if I change the USB port and let win7 load a new driver twice now I get what appears to be a Saitek-based driver even though I have loaded their software on this machine. When I try to assign axes in FSUIPC the joystick assignment reads in/out values with a great range from -16K to +16K, however, when I proceed to the axis calibration tab the throttle in/out values show 0. In VC the reversers come on at about half way down lever-wise. But since I can't seem to get to the calibration tab I can't calibrate the reversers to not come on. Its all very confusing to me at the moment. I would like to just clear out the drivers for the yoke/throttle and start over. I have attempted this numerous times now and still get the same result. I've let FSUIPC re-build its *.ini file and no joy. I know the Saitek issues come up regularly and I have trolled many threads and tried many remedies, but both I can't get passed this. Thanks for reading all this. If any recommendations I appreciate it. Keith
  5. Pete, Probably little surprise to you but after disabling controllers and assigning all yoke-stuff via FSUIPC it cleared up the initial problem. The one issue that threw me originally was the hat switch, which I had originally assigned via Buttons not Axis. So, all is hunky dory at the moment. Thank you for your time and continued daily support of all our (learn as we go) issues. Cheers Keith
  6. I had earlier tried to disable all controllers in FSX and go only with FSUIPC and Prosim, but my hat switch did not work fully correctly so I enabled it and the Pan Mode button. If I recall correctly the possible duplicate assignment was still present. I will have to retry this weekend. And yes, the log above is the event log since the button log did not show anything when I tried my MIP switches. At the time I could not recall if you said to enable button logging, event logging, or both. Thanks again Keith
  7. Pete, Upon logging it appears various MIP switches are calling FSX assignments. Question is why. None of these are assigned in FSX and Prosim is not running during the logging. Thanks again for your insight. [Continuation log requested by user] Running inside FSX on Windows 7 Module base=5DBF0000 200367 LogOptions changed, now 60000000 00000001 206576 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE 224703 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE 232020 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE 238291 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE 248431 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE 255077 *** EVENT: Cntrl= 65758 (0x000100de), Param= 0 (0x00000000) FLAPS_INCR 258150 *** EVENT: Cntrl= 65759 (0x000100df), Param= 0 (0x00000000) FLAPS_DECR 261036 *** EVENT: Cntrl= 66658 (0x00010462), Param= 0 (0x00000000) RELEASE_DROPPABLE_OBJECTS 265935 *** EVENT: Cntrl= 65759 (0x000100df), Param= 0 (0x00000000) FLAPS_DECR 279803 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE 288555 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE 326978 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES 327009 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES
  8. Thanks Pete. I will give it a look and report back. Keith
  9. Pete or anyone else, I recently changed from a "desktop sim" to a full up MIP interfaced with two Bodnar cards for switches and a Phidgets LED64 for the LEDs. I use FSX, PS737 and a licensed current FSUIPC. All switches registered fine using joy.cpl in Win7; however during a flight (both FSX default planes and Prosim Flight Model 2.0) I have a couple odd issues occurring. 1) When I put up my landing gear using my OC lever the view changes from VC to and outside spot. 2) When I move the switch in the Displays Source Panel from NORM to CPT PFD, the view changes from VC to outside spot. 3) Changing the A/P A/T FMC alerts panel from Test 1 to Test 2 changes the view from VC to outside spot as well. 4) Changing the Displays Source Panel from NORM to PRI makes the landing go down. There could be others not yet discovered. I don't believe its Prosim since it happens without PS running. I don't think its FSUIPC since I have renamed my fsuipc.ini and had FSUIPC rebuild the ini file and the same occurs. It must be a USB device / switch assignment duplication? If so, how does one find where this occurs and how to fix it? Thanks for any ideas in advance. Keith EDIT: I should also add that the MIP switches are all configured via Prosim and only the hat switch and "view mode" are configured via FSX on my Saitek Yoke and throttle. Most else yokewise configured via FSUIPC.
  10. You should always install FSX on the root drive (e.g., C:\FSX). See if that helps. Look around on Google for proper uninstall procedures. I know you have to uninstall FSX 2 or three times due to the Acceleration and SP modules. After that, follow NickN's Bible to re-install and configure. It works great. http://www.simforums.com/Forums/my-bible-and-new-hardware_topic50239.html Hope this helps until Pete or someone more knowing than I can help. Keith
  11. Thanks Pete. I will see if I can contact Marty directly.
  12. Greetings, I have an odd series of errors that occur when I change from my default 737 in FSX (accel). I use Prosim737 and licensed FSUIPC(current version). When I have PS737 running and attempt to change aircraft, PS737 crashes with a "failure to connect to server error". I've addressed this on the PS737 forum with no positive fix. Poking around various log files I found a possible FSUIPC error in the PS737 log. See below for it's entirety. About half way down is this response from FSUIPC: 1/3/2015 10:14:25 AM * FSUIPC process:Thread was being aborted. at FSUIPC.Win32.SendMessageTimeout(IntPtr windowHandle, UInt32 Msg, IntPtr wParam, IntPtr lParam, SendMessageTimeoutFlags flags, UInt32 timeout, IntPtr& result) at FSUIPC.FSUIPCConnection.Process(String GroupName) at FSUIPC.FSUIPCConnection.Process() at A.c9274a332fc88da07f453970ff7a08376.c79addcd55a6a9c265882411074f47fd5() in File71:line 741 Any possible ideas? If I keep my default aircraft then this error does not occur, but does when I attempt to use another FSX aircraft. So I am trying to figure out if its an FSX problem, PS737 (although I have re-installed with no joy), FSUIPC or something deep/or in between. Thanks for any help. At some point it might be easier to wipe and re-do everything. Keith 1/3/2015 10:13:31 AM * Features:Feature "Instructorstation 2.0" enabled 1/3/2015 10:13:31 AM * Features:Feature "Weather system" enabled 1/3/2015 10:13:31 AM * Features:Feature "Engine model" enabled 1/3/2015 10:13:31 AM * Features:Feature "Integrated Approach Navigation feature" enabled 1/3/2015 10:13:33 AM * Init:Booting system; Version 1.41b8, built 03 Jan 2015 1/3/2015 10:13:33 AM * Init:Loading configuration 1/3/2015 10:13:33 AM * Init:Loading preset positions 1/3/2015 10:13:33 AM * Init:Loading global database 1/3/2015 10:13:33 AM * Init:Loading translations 1/3/2015 10:13:33 AM * Init:Loading navigation database 1/3/2015 10:13:34 AM * Database:Loaded Navigraph database from C:\Users\Pilot\AppData\Roaming\Navdata\nd.mdb 1/3/2015 10:13:35 AM * Init:Creating aircraft 1/3/2015 10:13:35 AM * Init:Init hardware layer 1/3/2015 10:13:35 AM * init:Init c0c9ad584af628d7edd17e0e5cf49d2b3 1/3/2015 10:13:35 AM * init:Init c3f4993ff111abfd3dc76d6a2d585abe7 1/3/2015 10:13:35 AM * init:Init c1c608bec4a5046db92f333e0d0911c66 1/3/2015 10:13:35 AM * Init:Init comportconfigurator 1/3/2015 10:13:35 AM * init:Init c5dd94c917bfd7011c96eb5ae61f7da70 1/3/2015 10:13:35 AM * init:Init c543e0fbb04775164705f1c268cba965c 1/3/2015 10:13:35 AM * Init:Init comportconfigurator 1/3/2015 10:13:35 AM * init:Init c20b275df26e4143a98fe1d0e73e69532 1/3/2015 10:13:35 AM * Init:Init comportconfigurator 1/3/2015 10:13:35 AM * init:Init c856086a9a026eec3159b2231d7da4bb9 1/3/2015 10:13:35 AM * init:Init cd75469433fd749b0dffccb8a749ef2f3 1/3/2015 10:13:35 AM * init:Init ca8930770ba8761d31cbfa72173c0e4d9 1/3/2015 10:13:35 AM * Init:Init comportconfigurator 1/3/2015 10:13:35 AM * init:Init c9fcac8e5169cf41c898d9e4bcb1841fe 1/3/2015 10:13:35 AM * init:Init cd63247687916be1e326891511f961259 1/3/2015 10:13:35 AM * Init:Init comportconfigurator 1/3/2015 10:13:35 AM * init:Init c70bc966d733e903df5dd7d1a2e519b2d 1/3/2015 10:13:35 AM * init:Init cb07e7caa89f5fc9ca22dc27d6076754b 1/3/2015 10:13:35 AM * init:Init c92a973bd437ec19782a89fcb4afa64ef 1/3/2015 10:13:35 AM * init:Init c63d0d62dc002549f3eca494bfbd7bd68 1/3/2015 10:13:35 AM * init:Init c4dd4df086e527e43f56722a78c9d312d 1/3/2015 10:13:35 AM * init:Init cd3fffacfce23035b5dbfbf4d87ae7062 1/3/2015 10:13:35 AM * init:Init c4ae97d38efab8c96c25866efcd197bc3 1/3/2015 10:13:35 AM * init:Init c1030e9f3cf0832cc05bb3136707ab48b 1/3/2015 10:13:35 AM * init:Init c5f5dc1cbf6a75ed38aec19beab196378 1/3/2015 10:13:35 AM * init:Init c329f2d3d2109cfcc0aa986fac2b1abd5 1/3/2015 10:13:35 AM * Init:Init comportconfigurator 1/3/2015 10:13:35 AM * Init:FTDI sourceports 1/3/2015 10:13:35 AM * Init:Driver test FTD2XX.DLL 1/3/2015 10:13:35 AM * Init:Library loaded: 268435456 1/3/2015 10:13:35 AM * Init:Library released 1/3/2015 10:13:35 AM * Init:Driver installed 1/3/2015 10:13:35 AM * Init:Init FTDI done 1/3/2015 10:13:35 AM * Init:Num devices: 0 1/3/2015 10:13:35 AM * Init:getDeviceList 1/3/2015 10:13:35 AM * init:Init ce98b4b3e41b5086a56ba0c01426f37e0 1/3/2015 10:13:35 AM * Init:Init comportconfigurator 1/3/2015 10:13:35 AM * Init:FTDI sourceports 1/3/2015 10:13:35 AM * Init:Driver test FTD2XX.DLL 1/3/2015 10:13:35 AM * Init:Library loaded: 268435456 1/3/2015 10:13:35 AM * Init:Library released 1/3/2015 10:13:35 AM * Init:Driver installed 1/3/2015 10:13:35 AM * Init:Init FTDI done 1/3/2015 10:13:35 AM * Init:Num devices: 0 1/3/2015 10:13:35 AM * Init:getDeviceList 1/3/2015 10:13:35 AM * init:Init c976383fef6e4d3b8028b1bbf22cc2f63 1/3/2015 10:13:35 AM * Init:Init comportconfigurator 1/3/2015 10:13:35 AM * init:Init c26522f505a5d75993e3e56a2fbd52ea8 1/3/2015 10:13:35 AM * init:Init cf9b4163f3308733b3076cbc1c0c43725 1/3/2015 10:13:35 AM * init:Init c2f3714aa4a474e4874fa110c10c69f01 1/3/2015 10:13:35 AM * init:Init c074010885431b21cc7a0effcda9ebf1d 1/3/2015 10:13:35 AM * init:Init SystemDriverConfigurator 1/3/2015 10:13:35 AM * init:Init GateInputProviderConfigurator 1/3/2015 10:13:35 AM * Init:Setting intial state 1/3/2015 10:13:35 AM * Init:Deploying audio 1/3/2015 10:13:35 AM * Init:Deploying SDK 1/3/2015 10:13:35 AM * Init:Starting webserver 1/3/2015 10:13:35 AM * Init:Setting hardware mappings 1/3/2015 10:13:35 AM * IOElement:RefreshAllHardware 1/3/2015 10:13:35 AM * Init:Cleaning up 1/3/2015 10:13:35 AM * Init:Setup module services 1/3/2015 10:13:35 AM * Init:Setting up remoting 1/3/2015 10:13:35 AM * Init:Finish 1/3/2015 10:13:36 AM * IOElement:RefreshAllHardware 1/3/2015 10:14:14 AM * Simconnect:Connecting to SimConnect 1/3/2015 10:14:14 AM * Simconnect:Connected to SimConnect 1/3/2015 10:14:14 AM * IOElement:RefreshAllHardware 1/3/2015 10:14:14 AM * Engine model:Installing data from C:\FSX\SimObjects\Airplanes\B737_800 NO VC\Boeing737-800.AIR 1/3/2015 10:14:14 AM * Engine model:Tables updated successfully. 1/3/2015 10:14:25 AM * FSUIPC process:Thread was being aborted. at FSUIPC.Win32.SendMessageTimeout(IntPtr windowHandle, UInt32 Msg, IntPtr wParam, IntPtr lParam, SendMessageTimeoutFlags flags, UInt32 timeout, IntPtr& result) at FSUIPC.FSUIPCConnection.Process(String GroupName) at FSUIPC.FSUIPCConnection.Process() at A.c9274a332fc88da07f453970ff7a08376.c79addcd55a6a9c265882411074f47fd5() in File71:line 741 1/3/2015 10:14:25 AM * Main:Closed 1/3/2015 10:14:25 AM * Features:Feature "Instructorstation 2.0" enabled 1/3/2015 10:14:25 AM * Features:Feature "Weather system" enabled 1/3/2015 10:14:25 AM * Features:Feature "Engine model" enabled 1/3/2015 10:14:25 AM * Features:Feature "Integrated Approach Navigation feature" enabled 1/3/2015 10:14:26 AM * Init:Booting system; Version 1.41b8, built 03 Jan 2015 1/3/2015 10:14:26 AM * Init:Loading configuration 1/3/2015 10:14:26 AM * Init:Loading preset positions 1/3/2015 10:14:26 AM * Init:Loading global database 1/3/2015 10:14:26 AM * Init:Loading translations 1/3/2015 10:14:26 AM * Init:Loading navigation database 1/3/2015 10:14:27 AM * Database:Loaded Navigraph database from C:\Users\Pilot\AppData\Roaming\Navdata\nd.mdb 1/3/2015 10:14:27 AM * Init:Creating aircraft 1/3/2015 10:14:28 AM * Init:Init hardware layer 1/3/2015 10:14:28 AM * init:Init c0c9ad584af628d7edd17e0e5cf49d2b3 1/3/2015 10:14:28 AM * init:Init c3f4993ff111abfd3dc76d6a2d585abe7 1/3/2015 10:14:28 AM * init:Init c1c608bec4a5046db92f333e0d0911c66 1/3/2015 10:14:28 AM * Init:Init comportconfigurator 1/3/2015 10:14:28 AM * init:Init c5dd94c917bfd7011c96eb5ae61f7da70 1/3/2015 10:14:28 AM * init:Init c543e0fbb04775164705f1c268cba965c 1/3/2015 10:14:28 AM * Init:Init comportconfigurator 1/3/2015 10:14:28 AM * init:Init c20b275df26e4143a98fe1d0e73e69532 1/3/2015 10:14:28 AM * Init:Init comportconfigurator 1/3/2015 10:14:28 AM * init:Init c856086a9a026eec3159b2231d7da4bb9 1/3/2015 10:14:28 AM * init:Init cd75469433fd749b0dffccb8a749ef2f3 1/3/2015 10:14:28 AM * init:Init ca8930770ba8761d31cbfa72173c0e4d9 1/3/2015 10:14:28 AM * Init:Init comportconfigurator 1/3/2015 10:14:28 AM * init:Init c9fcac8e5169cf41c898d9e4bcb1841fe 1/3/2015 10:14:28 AM * init:Init cd63247687916be1e326891511f961259 1/3/2015 10:14:28 AM * Init:Init comportconfigurator 1/3/2015 10:14:28 AM * init:Init c70bc966d733e903df5dd7d1a2e519b2d 1/3/2015 10:14:28 AM * init:Init cb07e7caa89f5fc9ca22dc27d6076754b 1/3/2015 10:14:28 AM * init:Init c92a973bd437ec19782a89fcb4afa64ef 1/3/2015 10:14:28 AM * init:Init c63d0d62dc002549f3eca494bfbd7bd68 1/3/2015 10:14:28 AM * init:Init c4dd4df086e527e43f56722a78c9d312d 1/3/2015 10:14:28 AM * init:Init cd3fffacfce23035b5dbfbf4d87ae7062 1/3/2015 10:14:28 AM * init:Init c4ae97d38efab8c96c25866efcd197bc3 1/3/2015 10:14:28 AM * init:Init c1030e9f3cf0832cc05bb3136707ab48b 1/3/2015 10:14:28 AM * init:Init c5f5dc1cbf6a75ed38aec19beab196378 1/3/2015 10:14:28 AM * init:Init c329f2d3d2109cfcc0aa986fac2b1abd5 1/3/2015 10:14:28 AM * Init:Init comportconfigurator 1/3/2015 10:14:28 AM * Init:FTDI sourceports 1/3/2015 10:14:28 AM * Init:Driver test FTD2XX.DLL 1/3/2015 10:14:28 AM * Init:Library loaded: 96993280 1/3/2015 10:14:28 AM * Init:Library released 1/3/2015 10:14:28 AM * Init:Driver installed 1/3/2015 10:14:28 AM * Init:Init FTDI done 1/3/2015 10:14:28 AM * Init:Num devices: 0 1/3/2015 10:14:28 AM * Init:getDeviceList 1/3/2015 10:14:28 AM * init:Init ce98b4b3e41b5086a56ba0c01426f37e0 1/3/2015 10:14:28 AM * Init:Init comportconfigurator 1/3/2015 10:14:28 AM * Init:FTDI sourceports 1/3/2015 10:14:28 AM * Init:Driver test FTD2XX.DLL 1/3/2015 10:14:28 AM * Init:Library loaded: 96993280 1/3/2015 10:14:28 AM * Init:Library released 1/3/2015 10:14:28 AM * Init:Driver installed 1/3/2015 10:14:28 AM * Init:Init FTDI done 1/3/2015 10:14:28 AM * Init:Num devices: 0 1/3/2015 10:14:28 AM * Init:getDeviceList 1/3/2015 10:14:28 AM * init:Init c976383fef6e4d3b8028b1bbf22cc2f63 1/3/2015 10:14:28 AM * Init:Init comportconfigurator 1/3/2015 10:14:28 AM * init:Init c26522f505a5d75993e3e56a2fbd52ea8 1/3/2015 10:14:28 AM * init:Init cf9b4163f3308733b3076cbc1c0c43725 1/3/2015 10:14:28 AM * init:Init c2f3714aa4a474e4874fa110c10c69f01 1/3/2015 10:14:28 AM * init:Init c074010885431b21cc7a0effcda9ebf1d 1/3/2015 10:14:28 AM * init:Init SystemDriverConfigurator 1/3/2015 10:14:28 AM * init:Init GateInputProviderConfigurator 1/3/2015 10:14:28 AM * Generic driver:Only one usage of each socket address (protocol/network address/port) is normally permitted at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at System.Net.Sockets.TcpListener.Start(Int32 backlog) at System.Net.Sockets.TcpListener.Start() at A.c3ef2952a231eac30152ef79327277a5c..ctor() in File75:line 108 1/3/2015 10:14:28 AM * Init:Setting intial state 1/3/2015 10:14:28 AM * Init:Deploying audio 1/3/2015 10:14:28 AM * Init:Deploying SDK 1/3/2015 10:14:28 AM * Init:Starting webserver 1/3/2015 10:14:28 AM ! Webserver:Cannot initialise webserver: Only one usage of each socket address (protocol/network address/port) is normally permitted 1/3/2015 10:14:28 AM * Init:Setting hardware mappings 1/3/2015 10:14:28 AM * IOElement:RefreshAllHardware 1/3/2015 10:14:28 AM * Init:Cleaning up 1/3/2015 10:14:28 AM * Init:Setup module services 1/3/2015 10:14:28 AM * Init:Setting up remoting 1/3/2015 10:14:28 AM * Init:Finish 1/3/2015 10:14:29 AM * IOElement:RefreshAllHardware 1/3/2015 10:14:30 AM * Engine model:Installing data from C:\FSX\SimObjects\Airplanes\B737_800 NO VC\Boeing737-800.AIR 1/3/2015 10:14:30 AM * Engine model:Tables updated successfully. 1/3/2015 10:14:30 AM * Simconnect:Connecting to SimConnect 1/3/2015 10:14:30 AM * Simconnect:Connected to SimConnect 1/3/2015 10:14:30 AM * IOElement:RefreshAllHardware
  13. Hi Jim, Sorry for the delay. Just checked this site out of the blue... Anyway, yes. I contacted Richard at KimodoSimulations and he was able to fabricate (3D print) me an 8-way HAT, prewired for ~18 GBP. He also customized a backplate to mount (glue) to the yoke handle. I had to modify it slightly since it was a bit too deep but I have it mounted and it checked out fine with the Bodnar BU0386X board. I haven't really used it yet since I am still working on my panels so as to get rid of the desk aspect of my pit. It took a while (6-8 weeks) to finally get the switch mainly because he was/is busy and there were some family related priorities, but he was great t work with. Highly recommend this route. See attached pic Good luck Keith
  14. Just to close the loop.. My USB board was faulty. Replaced with a Bodnar BU0386X and all works fine. Adding an 8-way hat switch to the handle (fabricated/wired from KomodoSimulations). Hopefully will be an easy addition.
  15. I had some similar issues with GoFlight modules.. Doubt if its FSUIPC related. Might try affirming USB device power setting are set to "always on" and do not allow windows to manage power to USB devices. See: http://forum.avsim.net/topic/327768-goflight-hardware-disappearing-in-win7-64/ Might be some clues in this post. Also could be bad USB cable or conflict with another defined axis. If using FSUIPC uncheck axes in FSX config. Good luck Keith
×
×
  • 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.