Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Swoops on February 09, 2012, 10:25:24 PM
-
Thinking about coming back to game, dug my x52 out of storage, and I remember that I used to have the zoom toggle and zoom in/out functions mapped to the little scroll wheel on the throttle quadrant. I have re-installed the latest drivers for my operating system from saitek.com. I do not use their profile editor I just prefer installing the drivers. I noticed that I have to disable "clutch mode" on the mfd page to use the button with the "i" on it (I use that for my WEP). But I have tried both "Clutch" and not "Clutch" modes and I am still having no success with AHII recognizing the scroll wheel on the throttle quadrant. Any hints, tips, tactics, or tricks for making that scroll wheel usable again? It is located just to the left of the 8 position POV hat on the throttle.
-
I have never been able to make it work. same for the button on the right side with the "i" on it. it doesnt work.
semp
-
There are inputs on the stick, which are not passed directly through DirectX, unless you map them using the Saitek software.
The game diligently shows all inputs the stick will give us.
-
Thinking about coming back to game, dug my x52 out of storage, and I remember that I used to have the zoom toggle and zoom in/out functions mapped to the little scroll wheel on the throttle quadrant. I have re-installed the latest drivers for my operating system from saitek.com. I do not use their profile editor I just prefer installing the drivers. I noticed that I have to disable "clutch mode" on the mfd page to use the button with the "i" on it (I use that for my WEP). But I have tried both "Clutch" and not "Clutch" modes and I am still having no success with AHII recognizing the scroll wheel on the throttle quadrant. Any hints, tips, tactics, or tricks for making that scroll wheel usable again? It is located just to the left of the 8 position POV hat on the throttle.
I programmed this one through the Saitek software. You can assign each "click" as a key press. I actually use this for flaps.
-
The only way I could get it to work was mapping through the profile software too.
Wiley.
-
Try leaving the page open (the one where you can see when you press a button, move the throttle etc) and map it then.
Wurz
-
On my X52 I had it programmed for zoom in/out. I also had it shifted for map zoom in/out. It worked rather well but yes I had to use the SST software to do it.
-
There are inputs on the stick, which are not passed directly through DirectX, unless you map them using the Saitek software.
The game diligently shows all inputs the stick will give us.
stupid question boss. how do we know which buttons are "passed on" by dx? the reason I ask is because the one button on my stick used to work in ah but now it doest work. it works in windows and if I map it thru trakir but not in ah
semp
edit: wow did you guys see that big flash coming from california? that was me. gonna map that button that works in trakir but not in ah to trakir and that frees up one of the buttons from trak so i can use it in ah. boy I gotta get me some more of those smart pills the doctor gave me.
another edit; i found out if i open the x52 properties in windows then the button is available in ah. not sure why but I do remember this happening before.
-
Look folks, we pass everything the stick will give us. The game supports 255 buttons, 8 wheels, and 8 sliders per stick.
Ask Saitek why they do not pass everything right on through, like most every other stick on the planet does.
-
I had the same problem buttons number 29 and 30 would not work in windows seven. I went to my control panel, devices, game controller, ex 52 properties while aces high was minimized and stick controller was in modified mode. Once I operated the stick in properties mode I went back to the game and it would work I then closed out the X52s game controller properties and it was good! My system is window seven 64 bit.
-
:bhead The only way I can keep buttons 29 and 30 working is to leave x52 flight controller properties open while I play the game. If I OK Properties and close I lose the setting in the game, any suggestions?
-
:bhead The only way I can keep buttons 29 and 30 working is to leave x52 flight controller properties open while I play the game. If I OK Properties and close I lose the setting in the game, any suggestions?
It's a known bug on saitek's side of things. Leaving the properties box open is the only work around that I know of.
-
Try checking this out:
http://www.saitekforum.com (http://www.saitekforum.com)
-
Here is how to deal with this issue:
1. Make a shortcut on your desktop for the X-52
(http://i343.photobucket.com/albums/o460/caldera_08/saitek-1.jpg)
2. Right click the icon and then left click Game Controller Settings.
(http://i343.photobucket.com/albums/o460/caldera_08/saitek-2.jpg)
3. Left click on Properties.
(http://i343.photobucket.com/albums/o460/caldera_08/saitek-3.jpg)
4. Leave this thingy open and then log on to AH. All of your buttons will now work in game. :aok
-
Try leaving the page open
This works ... no need to run the saitek configuration program, just click on the task bar icon, hit the control panel button, and LEAVE THE CONTROL PANEL RUNNING (on screen) on the desktop when you load AH ... You can then program the button and scroll wheel using the AH mapper menu. You have to leave the control panel ON everytime you start AH if you want to use those buttons.
:salute
-
Do yourself a favor and whenever you get a SST profile working right, or any other controller, make a copy of the profile on a separate flash drive. Or at least put it in another folder. Often it takes a hybrid profile thats a pain in the rump to redo from scratch and Ive lost my SST profile more then once. And yes, that wheel has to be mapped in SST. The actual wheel turning has to be mapped in SST.
-
Ask Saitek why they do not pass everything right on through, like most every other stick on the planet does.
I've done that ... talked to BRAD at Madcatz (they own Saitek) ... VERY FRIENDLY, but no real answers or solutions ... I don't think they do engineering or programing in-house. They're just merchandisers. I found their mapping software to be BUGGY and a real resource pig, I don't use it.
;)