USB device Issue with Launchbox v10.14 using Logitech F710 wireless USB controller when enabling Controllers

[Rod Wilkins]

Hi folks, to start, I’m using Windows 10 1909 64-bit, Launchbox 10.14, Logitech G110 Gaming Keyboard and Logitech F710 USB wireless gamepad.

This is the most peculiar problem I’ve ever encountered, and I’m not sure even the likelihood of someone reproducing it to fix, but thought I would log it just the same.

I’m using a Logitech F710 wireless USB gamepad (connected with X-Input setting) and using the corresponding Xbox 360/Xbox One driver provided by Windows 10.

Now usually things seem to be OK… however every now and then (seems random - like several times a minute or occasionally every couple hours, no real pattern), all of my USB devices suddenly reset (it’s like the symptom of a USB controller power failure). And then the keyboard input becomes stuck on the last key in the keyboard buffer. So for example if I was typing ‘open’ then on the last letter the keyboard is stuck entering ‘nnnnnnnnnnnnnnnnnnnnnnnnnnnn’ and doesn’t respond until I disconnect it and reconnect it.

My first suspicion was that my USB gamepad or keyboard were the problem (or heaven help me my motherboard USB controller was dying). So I tried different USB ports, different keyboard and mouse, even bought a different USB controller card to connect them to. I tried disconnecting all USB devices (including my gamepad) leaving just my keyboard connected.. but the problem persisted.

I was literally pulling my hair out on this issue… until it occurred to me I only really noticed this problem while editing games in Launchbox. So I went in and disabled the controller support in Launchbox.. and Voila the problem disappeared!!!

I’m really baffled why this happens and open to suggestion on any logs I might be able to provide or workarounds I could try to get around this problem… Luckily I’m more concerned with controller support in BigBox but I would still like to get this working for testing things in LB with my gamepad through that interface without always having to open BB.

So there’s no actual ‘error’ message to report, just the strange behavior I mentioned above…

[Christian]

Not sure it would cause the symptoms you are seeing but I am curious. Do you have the power saving options turned on or off for the USB ports you are plugging into? Windows has a setting that lets it shut off the USB ports if the computer is under heavy power draw (like when we full bore the CPU after editing a game) and I am curious if the OS is temporarily shutting down and turning back on the USB port and making this situation worse. The setting reads in the OS similar to “Allow turning off this device to save power”, could you verify if that is checked or unchecked?

[Rod Wilkins]

Thanks for the reply - yes actually I thought of this as a possible suspect too (and checked this as well), I turn off USB power saving as a general rule of thumb when I install the OS, as I never want it to turn off my USB devices anyway.. But I double checked to make sure it was still off and it was.

[Christian]

Thanks for the response. Will have to dig in the code and see if I can find anything else that may be causing this issue then.

[Christian]

Not real sure it will help, but worth the mention. Have you checked that you have up to date drivers specifically for your devices? Wouldn’t even ask since most of the time I use plug-n-play drivers as well but I know with the Logitech stuff I’ve owned in the past they tend to do a LOT of driver updates on their stuff so curious if maybe that would have any impact on this.

[Rod Wilkins]

Thanks, but I tried checking this as well, Logitech has a generic Win7 driver which I’ve tried but when I switch to XInput mode it ‘switches’ to use the Microsoft one anyway on its own (changes how its reported in device manager on its own). I even tried forcing a different version of the Xbox 360 driver (vista, win 7) to see if it helped but it didn't.

[Christian]

Yeah I looked briefly for a driver and couldn’t find one. Just some “Connect Utility” but couldn’t find out what the heck that utility even did. When I get a chance will look and see if I can replicate and look at the code. I have the wired variant of the controller, curious if I can replicate the behavior with that.