Aces High Bulletin Board
Help and Support Forums => Aces High Bug Reports => Topic started by: oboe on May 12, 2010, 09:11:45 PM
-
Online, offline - using hat switch or keypad - many times after releasing the key or hatswitch, my default view is the rear view. Only way I can reset it is to hit the rear view key, then it resets.
Hard to fly looing backwards though.
-
This bug, which had disappeared on its own a few days after this post, is back with the new release (2.19 patch 3).
Weird.
-
Now I'm thinking this is a joystick issue after all. Think the hat switch is going out on my Cougar. Doesn't register the hat switch at all when I select Properties in Game Controller settings under Windows Devices...
-
I you go into Options->Controls->Map Controllers while the view is in its "stuck" position, you'll be able to tell if the game thinks the back view button is pressed by seeing if the "Hat Switch Back" function is highlighted in the list.
- sudz
-
I don't even get the hat switch circle diagram in Windows controllers - AH map controllers is not seeing any hat switch (any buttons on the controller for that matter).
It started right after the last update, but I think it must be a controller problem. Have uninstalled and reinstalled drivers, nothing helps.
Windows devices is showing it as a keyboard icon....
-
I know something like this happens if you're using the views whilst typing - could you be having something related to this?
-
You mean typing in the text box? Right now, the problem is also occurring completely outside of AH. If I go to the properties window of the Cougar in Windows Controllers, I no longer have the circle diagram for the hat switch (the one that shows the red arrows indicating which hat switch direction has been pushed). Its just not there at all anymore.
-
Online, offline - using hat switch or keypad - many times after releasing the key or hatswitch, my default view is the rear view. Only way I can reset it is to hit the rear view key, then it resets.
Hard to fly looing backwards though.
Well last night this problem started as described in the original post, except I fly with the TM Warthog now. Haven't done much debugging/testing yet but I wanted to get this reported before the new version release, so its clearly not related to the new version. (I have not downloaded the beta).