AH3 killed the throttle

[Dobs]

Hi folks!

I appreciate the responses. I don't want to win an argument, I want this game to work. These answers focus on what HTC can't ever be responsible for, which is how USB ports are assigned by Windows. AH3 IS responsible for how it reads them and nothing is said on that? I have fixed this by a method that doesn't make any sense. I left AH3 running over night and rebooted the next day. Now it sees the controllers. Do we have an explanation? Windows did no updates.

Skuzzy I hear what you are saying about Window updates but quite honestly, I don't know how anyone would keep their computer safe without using it. What you seem to be saying is you don't know what update will change the settings so? I can't see any way you can do it without it but I'd love to hear from you how to maintain the computer without Windows updates. Or how you identify that it changed something without telling you. It doesn't seem practical to NEVER update the computer. Please let me know because if it will fix this issue I'll do it.

The other issue that is not answered is how every single mapping is wiped out by AH3 in both AH2 and AH3. That IS something that is handled by the program. How does it accomplish wiping EVERY SINGLE MAPPING? How do I recover this? I have plenty of back ups, why don't they take effect? I still have AH2. If I can make them work there, can I transfer them to AH3 without killing and restarting the program?

Thanks!

TheRapier....I feel your pain. A few years back I switched from twisty to full set of controls. I spent hours programming them and then one day...they had switched IDs.  Button presses on Throttle were doing  Joystick programming and vice versa.....I was like WTF!   So I fixed them again...and next reboot...they had switched back.  I was lucky in that I had copied my settings over in both instances, and I just replaced my files.  After doing some reading, Windows and USB ID were the culprit.  I unplugged them, rebooted.  Shut down, plugged them back in, rebooted, checked the USB IDs. Shut down, rebooted...they stayed the same. Put the correct files in place and moved on.  I've been lucky it hasn't repeated.  I've moved my controls off USB Hubs directly and plugged directly into the computer as well. 

Don't know what caused it, just know it is a PIA.  Have you tried just unplugging throttle from computer and reboot and then plug back in?

[Rich46yo]

Make sure you have the USB bus set to never power down.  That can cause problems.

Just so you know Skuzz I went into settings AND devices and tried both to never allow windows to power down either root hubs or individual devices and both caused game crashes. I was unable to play AH-lll. What my problem was was one of my devices would disconnect for a second which threw my controllers off, deselecting my controller profile in Saitek SST. So I'd have to alt/tab to controller icon and re-assign a profile.

Im not saying it was Aces High because, well, how could it be? Eventually I figured it was a power issue centered on my keyboard so I took my keyboard and another game pad and connected them directly to Ports from my MB instead of connecting them to powered hubs.

I dont understand this problem, it really shouldnt happen. USB-2 is supposed to connect over 100 devices with powered Hubs. I suspect this is our friends problem. He is going to have to find some combination of port connections that actually work. I dont know if he's using hubs or not.

These things get so weird I have a pair of saitek rudders that windows will only read if I connect them thru a keyboard built in port. No other ports or Hubs will work.

[Skuzzy]

You can forget about the actual specifications for the USB bus.  There never has been a manufacturer who made a USB hub, which would actually handle the maximum power draw (including Intel) of the USB specification.

[Rich46yo]

Not only that but the entire thing is trial and error between your individual computer, your controllers, the actual Hubs themselves. Ive bought powered Hubs that windows doesnt even recognize even tho I have the same kind of Hub that it does. Even when I connect the one Hub to the same port the other one is recognized on windows still doesnt see it. Ive been thru this on 4 different boxes, this Digital Storm one has actually been easier then most but even with it Ive had issues.

Anytime you connect anything to anything you have a potential weak link in the chain. That and Ive found USB to be persnickity at best which is why I went FW-800 for all my video backup. Even then heres a list of USB devices I have on this box, a Saitek throttle/stick, a rudder, a mouse, a wireless mouse, a keyboard, a G13 pad controller, 2 printers, a fit bit, an entire racing setup with throttle-brakes and whoknowswhatelse, a Game head set, a TrackIR. And Im probably forgetting a few things. Windows and USB says there shouldnt be a problem but there is and its with windows assigning IDs to the devices and the ports/hubs reading them right.

There is no science to it, its trial and error. Saitek is a dream unit now compared to those first SST writes. What a disaster those were. I hope our friend stays with it. To be honest it sounds like a power issue. I have a Saitek throttle whose MFD light often goes out and I have to reconnect it to the powered Hub for it to turn on again.