07-09-2013 01:25 AM - edited 07-09-2013 01:25 AM
I am running windows 7 and only the directinput mode is working. I tried installing the logitech profiler, but this did not fix my problem. How do I fix this?
07-10-2013 06:28 AM
To help resolve the issue with your Logitech F310 Gamepad, try the following:
Are the buttons responding in the calibration Window?
Do you see any "yellow bangs" or error messages? What's the entry of the F310 when set to XInput?
If a reply adequately addresses your technical issue, please click on the "Accept as Solution" and "Give Kudos" button so this information can benefit other users via search.
10-17-2013 05:50 PM
I bought the F310 today and i've had the same problem.
In directinput everything goes fine when I plug it into my USB port and I can find it in Control Panel ---> Select Devices and Printers.
In xinput mode it makes a "duh-dunk" sound when i put it into my USB port and I can't find it in Control Panel ---> Select Devices.
Does it fail to install? And if so, why only in xinput mode and not both?
I've tried to google xinput driver, but it says it should be already installed for windows 7.
Sorry for interrupting.
12-06-2013 01:22 PM
I have teh same issue. Tried controller on two other Windows 7 machines and it works, but for some reason it won't install the driver on this PC. I've tried installing the xbox360 drivers first but still nothing. I also updated all of my motherboard drivers.
08-17-2014 02:52 PM
The best place to look for your gamepad is Devices and Printers.
When in X-Input mode, it is a Gamepad F310.
When in D-Input mode, it is a Logitech Dual Action.
02-16-2015 09:50 AM
I have a similar but slightly different problem that I think is related to this question.
I have been using the F310 GamePad to play Dragon Age Inquisition with my Windows 8.1 system. Suddenly the game stopped recognizing that the GamePad was even plugged in though the Logitech Profiler recognized it with no problem.
I finally realized that the Profiler needed the GamePad Mode switch in the "D" position for the Profiler to recognize the GamePad and set it up for a particular game.
The game, however, required the GamePad Mode switch to be in the "X" position to recognize the GamePad.
My question is ... WHY!?
It doesn't make sense to me to use a profiler to set up a hardware device for a particular piece of software if that software doesn't then recognize the hardware when it's running!!!