Tried this in FSUIPC. When in Axis Assignment, nothing registers when I move either throttle. The GF TQ6 is not assigned in FSX.

 

This sounds like FSUIPC cannot "see" your throttle quadrant.  If you say 'nothing registers' I assume you are trying to assign the axis within FSUIPC per my suggestion.  Make sure your drivers are registered.

 

Tip for consideration:  A very fine program called USBDeview.exe is available that will list every USB device on your system.  In some cases, after unplugging and reinserting USB devices into different ports, Windows 7 can become overloaded with USB assignments.  I have had good luck starting the USBDeview.exe program, then from the EDIT menu SELECT ALL USB devices and after they are all highlighted, click on the FILE menu and choose UNINSTALL SELECTED DEVICES.  You have to wait a while as each USB device is removed from your Windows 7 setup.  Eventually all but your USB external hard disks will disappear from the list of devices.  At that point, your USB keyboard and mouse will NOT work, you will need to restart your PC manually, by either pressing the reset button, or holding the power button down to shut the machine off.  Restart the machine and sign back into windows.

 

You will need to sit there and wait quite a bit as each and every USB device on your system is 'rediscovered' by Windows 7 and re-assigned within the registry.  This will blow out duplicate USB assignments which occur each time you remove a USB device and connect it to a different port (plug) on your system.  If you have an older system, this can take quite a bit of time.  You will hear the USB Discovered sound from Win 7 as each device is located.  Then the drivers for each device are assigned (which also takes time) as Windows 7 checks online for newer drivers for your devices.  Finally after all of this, my advice would be to hit START button and then RESTART, just to be sure everything was found.  If you have bluetooth, the bluetooth devices may not appear until after you restart your system.

 

This is a good thing to do from time to time, especially if you have unplugged things and put them into different USB plugs.  If you're using USB hardware for your flight deck, example VRInsight MCP Combo II controller, you may find it is now on a different port than it was before, and you will need to enter the new port number in LINDA.  Linda's built in checkup tool will tell you if it cannot locate the device, and offer to make changes within FSUIPC to correct the issue.

 

Also, your Bluetooth controller (built into your motherboard) may assign a virtual com port to a new port number as well, programs like GARMIN PILOT need the correct port number to work properly.  

 

As always, it's wise to have a full backup of your system prior to doing anything major to your system.

Yes very good tip.

 

never heard if this program.

 

I personally never change my USB connecors, and have them all labeled.

So if I have to disconnect things (for maintenance or so) I know where they go later!

I had a problem where if I unplugged a USB device and plugged it back in- sometimes it would not be recognized by the system.  I call this USB device assignment confusion.  So I prowled the web and found the USBDeview.exe (USB Device Viewer) program.  It has helped me, with the caveat that sometimes you may need to adjust settings in some programs to take note of the new com port numbers that are assigned for virtual serial ports.  A virtual serial port is a com port number that has been assigned by windows to a USB device.  For example, the VRinsight MCP Combo II unit is a USB device, but it operates within FSX as  a 'virtual' serial port device.  "Linda" (available free here on AVSIM) connects this device to FSX via FSUIPC, by taking note of its virtual serial port COM setting and writing that value into the FSUIPC.ini file.  Linda will handle this task for you, but you may need to help out by determining what com port number has been assigned to the MCP Combo unit, so you can tell Linda the correct Com Port number.  Again, this is a 'virtual' com port, as the device is not connected with a serial connector it is a USB connector, but Windows will assign a virtual Com Port to it, this occurs when you first install the device, part of the driver package from VRinsight installs a virtual com port driver for the MCP.

Good tip Robert, I'll try that after the Bears game.

 

Gnacino;)

Robert, does your fix require that the fsx controllers enabled box be checked to "on"? Talking about the one that is inside the fsx menu, not fsuipc.

 

Sent from Samsung Galaxy Note 2

 

I can still find nothing that works, without destroying the FSUIPC settings for other aircraft.

 

I know PMDG say it's not supported, which is no doubt why they're silent on the subject, but considering how many folk use FSUIPC, it seems crazy!

Robert, does your fix require that the fsx controllers enabled box be checked to "on"? Talking about the one that is inside the fsx menu, not fsuipc. Sent from Samsung Galaxy Note 2

 

NO.  I have all FSX controllers disabled in FSX (by unchecking the tickbox you refer to).  The calibration of the devices is not done in FSX nor in FSUIPC.  They are calibrated from the windows 7 control panel.  Devices and printers.  Click on the controller, example Thrustmaster Hotas Warthog Throttle, or Thrustmaster Hotas Wathog Joystick, right-click and then choose game controller settings.  Then from the flyout menu choose properties.  You see a dialog box with two tabs, TEST and SETTINGS.  Click on settings tab.  You can choose RESTORE TO DEFAULT or CALIBRATE.  I find you can RESTORE TO DEFAULT and be ok in most cases.  Worst case, you can return to this area I'm talking about after a test flight and THEN choose Calibrate. 

 

 

What is the setting you all have the FMC A/T over ride set to? Never, in hold or always?

 

Only in HOLD.

Just took off for another flight and nothing worked again, with throttles through FSUIPC (direct to FSUIPC - no calibration).  Unchecked FSX's 'Enable Controllers' and the throttles still snaps back to idle.  I could again only taxi with A/T Arm switches off and I know my VNAV descent in Hold mode is going to worthless again, as well.  Hopefully PMDG takes a second look at this AT, with FSUIPC involved, and maybe comes up a little something for us.

I have a Saitek Proflight yoke and rudders and have had the same problems as most of you chaps and just put it down to using windows 8. Usually everything is ok but every so often all the settings go haywire.

 

Having seen posts regarding this, I have just recently installed the FSUIPC for FSX hoping the issue would be resolved but everything went from fairly bad to disastrous. Very little worked properly and when I got one issue solved, another that was okay went and broke. I have tried all the options above you have all proposed but none of them worked for me unfortunately.

 

However, what I did do was to go into the Proflight yoke and rudder calibration settings and after a number of goes did finally get it to recognise my controllers. Everything works okay for me now (though this was okay before I installed FSUIPC) and am hoping it will stay that way. I know everyone has different systems so what will work for one may not work for another, but at least it is another thing to try.

 

Just got to sort out my issues with my new 777 now

 

Colin

I have a Saitek Proflight yoke and rudders and have had the same problems as most of you chaps and just put it down to using windows 8. Usually everything is ok but every so often all the settings go haywire.

 

Having seen posts regarding this, I have just recently installed the FSUIPC for FSX hoping the issue would be resolved but everything went from fairly bad to disastrous. Very little worked properly and when I got one issue solved, another that was okay went and broke. I have tried all the options above you have all proposed but none of them worked for me unfortunately.

 

However, what I did do was to go into the Proflight yoke and rudder calibration settings and after a number of goes did finally get it to recognise my controllers. Everything works okay for me now (though this was okay before I installed FSUIPC) and am hoping it will stay that way. I know everyone has different systems so what will work for one may not work for another, but at least it is another thing to try.

 

Just got to sort out my issues with my new 777 now

 

Colin

 

You're a brave soul trying to run flight simulation on Windows 8.  I have read some comments across the web indicating Win 8 may not be the 'best' choice of O/S for FSX.  Glad you (apparently) have solved the issue.  

Robert

 

FSX works perfectly fine on windows 8, it is the older Saitek controllers that I have issues with. Before PMDG came along I was using mostly the 737 and the prop machines without any problems at all. Even installed FSgenesis and Flight1's ultimate terrain without any issues. The biggest problem I had was that the parking brake switch on the yoke kept failing so I needed to go into the settings and add it. No big deal but frustrating.

 

When I read of the latest FSUIPC I thought it would solve my issue with the brakes, but I have spent all weekend trying to fix FSX after installing it, blooming thing. By the way, PMDG 777 installed perfectly and works okay apart from some minor issues which may or may not be windows 8 related, still trying to figure it out.

 

Colin

Hey Robert, I'm trying the USBDeview you mentioned.  I selected all as you mentioned but doesn't seem to be doing anything.

After selecting ALL, they should turn dark blue (indicating they have been selected), then click FILE across the top menu and "UNINSTALL ALL".  There will be quite a long delay as each device is uninstalled from Windows.  It will look like nothing is happening.  Then, after the wait, almost all the selected items will disappear (indicating they are 'uninstalled') but any external hard disk drives will still be connected.  At that point, you would THEN press your restart button (as your keyboard and mouse won't work- they have been uninstalled too) or power cycle your PC (turn it off completely, wait 30 seconds, turn it back on).

 

Upon restart, there again will be a long time passing whereby each USB device is first 'discovered' and then installed, and then Win 7 will check for each device online to see if new drivers are in the Windows Update site for EACH USB device.  This takes TIME.  Don't get in a rush.

 

After this is all done- you should once again restart your system, as a final check to make sure everything got reinstalled.

 

Before running USBDeview.exe, you should also make sure all your USB devices are turned on and connected to your PC, so they can be uninstalled and then reassigned.

I solved it this way: http://forum.avsim.net/topic/419861-any-solution-for-using-fsuipc-calibration-throttle-calibration/?p=2786100

 

Hope it works for someone else!