Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: turt21 on October 22, 2012, 01:03:19 PM
-
I have a Saitek X52. LAst week AH started to forget some of the button designations. Now there are a couple that the game doesnt see at all. The buttons work on the Saitek software.Aslo Im not having any luck getting my vox working. I wouldnt think they were related but last night when I pushed the stick to the right I started getting feedback in my speakers like there was some kind of conflict.Ive reinstalles Orig Saitek software and also inst new dl version. Win 7 ASUS 3Ghz w 8G ram and a 2 G vid card. Comments? turt
-
Try using the stick without the Saitek software and see what happens.
-
I did a search on my machine and theres no Saitek software there now. When I try to program range and channel buttons even when I click OK when I bring up the channel buffer the chaznnel and range lights dont light up when I select the buttons.CAnt get flaps to work either
-
I did a search on my machine and theres no Saitek software there now. When I try to program range and channel buttons even when I click OK when I bring up the channel buffer the chaznnel and range lights dont light up when I select the buttons.CAnt get flaps to work either
For VOX, check the Options->Preferences->Game Sounds panel to make sure you have the correct devices selected.
-
for all the x52 buttons to work go to devices and printers> right click on saitek x52 then select game controllers, then click on x52 f;ogjt control system then properties. and leave it open. you must do that every time you play aces high. that's they only fix.
semp
-
^^^ always have to have game controllers/ properties open...pain in the bum but ho hum :aok
-
for all the x52 buttons to work go to devices and printers> right click on saitek x52 then select game controllers, then click on x52 f;ogjt control system then properties. and leave it open. you must do that every time you play aces high. that's they only fix.
semp
Must be a Windows 7 issue. Saitek X52 worked on XP & Vista, without having to do this.
Coogan
-
xp
little button by mouse on throttle to name but one button
-
Some of the Saitek buttons do not report to DirectX without the Saitek software being loaded.
-
Must be a Windows 7 issue. Saitek X52 worked on XP & Vista, without having to do this.
No Vista needs it to......if you want full directx functionality............... try it it gives you more functionality than the saitek software does..................
-
No Vista needs it to......if you want full directx functionality............... try it it gives you more functionality than the saitek software does..................
ummm, no it doesn't. To have that window open, in order to make the Saitek work, is kinda like pissin' in the wind. But, hey sounds like you know what you're talking about... :rolleyes:
Coogan
-
Ill try that. Might be just as easy to just use the keys to communicate. Never had this prob w XP.thanks all
-
2 words
Vista Sucks
Nuff said
LawnDart
-
Quote from semp:
for all the x52 buttons to work go to devices and printers> right click on saitek x52 then select game controllers, then click on x52 flight control system then properties. and leave it open. you must do that every time you play aces high. that's they only fix.
I get a blue screen from time to time while in turret view of a tank and my only solution is to type in the dot command "EF" to get back to the tower and escape the blue screen. I believe there is a stability issue with the x-52, dx9, and win7' so I will give semp's idea a try.
I have tried almost every video setting in the game with the same result.
(Radeon hd 7979 w/ 3 gigs ram) If I get the blue screen again I will post the dxdiag.
<S>
Mano
-
I installed win 8 about two weeks ago. I did the upgrade and not the usual format HD and go with the OEM version that I have done in the past when moving to a new version of windows. I am pleased to report I have not seen a single blue screen. I did have to d/l new video drivers but other than that Ah works great.
:salute
-
I have windows seven, for the last year I had been going to properties and settings and leaving it open so my x 52 would work properly. today while trying to change a view all of my numerical keypads changed. I tried to reset them by re-mapping the numbered keys. This did not work after getting frustrated I closed the X52 properties and surprise all the numerical settings worked correctly. But they will not work when I open the properties for the X52. :bhead any suggestions?
-
I have windows seven, for the last year I had been going to properties and settings and leaving it open so my x 52 would work properly. today while trying to change a view all of my numerical keypads changed. I tried to reset them by re-mapping the numbered keys. This did not work after getting frustrated I closed the X52 properties and surprise all the numerical settings worked correctly. But they will not work when I open the properties for the X52. :bhead any suggestions?
I tried reloading game over existing game with no results. Finally got disgusted and did a clean reinstall and now everything is working fine. So since the new beta patch I have reinstalled the game three times now!
-
Not sure what you are expecting here. The Saitek button issue has to do with Saitek. They chose not to pass through buttons to DirectX. We report every input any stick gives us via DirectX. That is all we can do.
We cannot fix it. Saitek can.
-
much obliged. LEaving the prop open does the trick