RobiorClyde

I don't believe this is the case because the controls work in DCS.

Yes, my keyboard and my mouse are plugged into the other ports of my computer.

Thanks however I've checked DIView and there are inputs coming from the port my HOTAS is connected to Also sorry, ''in pre-flight'' means that I was preparing for a flight and when I taxi out to the runway or even just sitting at the apron, my keyboard fails as well as my HOTAS. I knew it stopped working because when I made inputs with my HOTAS, the control stick or throttle would not correspond and when I hold space in an attempt to move my camera around, it would not move the camera. I even tried using the number pad to look around but even that wouldn't work. It was completely unusable.

I've checked in on the control panel to see if the option was selected, it wasn't. I've tried switching ports but it still didn't seem to fix it, I've also tried to use the device manager to remove the USB controller and did a reboot but still no luck :c However may I ask, how can you see if the USB port you're using is unpowered? Also, I reckon the problem I'm experiencing is only in FSX because my HOTAS and my keyboard still work in other games like DCS. Perhaps it is?

Hi, I've been a happy user of FSX:SE for a while now and I use a TM T flight HOTAS. However suddenly came across an issue where when I'm in pre-flight, my HOTAS and keyboard decide to stop working after a few minutes. I've looked over old forums regarding my same annoying issue but all of them had no answers. I've tried stuff like verifying file integrity in Steam, running SCF, doing a fresh reinstall and even things as simple as pressing Control+K but all of them didn't solve the problem. I do notice one thing, my keyboard has a Caps Lock light and usually when I press Caps lock (outside of FSX) my Caps Lock light stays on until I press it again. In FSX the Caps Lock light turns on when I press if but it turns off when I let go of the Caps lock key. I would be more than grateful if anyone can help me find an answer to this seemingly unfixable issue.