Brad:
I replied to your question in the thread in the Hardware and Software forum. I hope I explained where everything goes and how you use Control Manger.
Precha:
If you look at the thread I to which I refered above, I provided a link where you can download my profile.
I think this is the link. It's pretty complex, but I've programmed all of the buttons and axes (including the microstick) on the stick and throttle to perform multiple functions. It may not suit your tastes, but perhaps you can use it as a learning tool.
I've actually created a considerably updated profile, which includes new stick trimming functions and remaps some of the keys to a more logical layout. If you're interested, I could make the associated files available for download when I get home tonight.
Regarding Oaktree's advice, note that the approach he suggests is certainly valid, but it is different than the one I have taken. What he is suggesting is that you set all of the stick and throttle buttons to DX (i.e., DirectX) buttons so that AH will recognize them. Having done that, you can map the button presses to AH commands from inside of AH. To do this, start Control Manager, and press each of the stick and throttle buttons and hat switches, one-by-one. Each time you press a button or hat switch, the CH Manger display should switch to displaying the graphic for that button or switch. When it does so, check to make sure that the DirectX mode box is checked, that the DX Device box displays CM Device 1, and that the DirectX Control box displays a button, like "Button 2".
(I suspect that the reason that you aren't seeing any throttle buttons in AH is that you've run out of DX buttons. When you set up your mapping (using the wizard), that you can only select 32 DirectX buttons (I suppose this is DirectX's limit for the number of buttons on a single device). You have many more buttons than this, if you include the POV hats on the stick and throttle and particularly if you use a shift key and the available modes. Thus, when you run out of buttons on CM Device 1, select CM Device 2 in the DX Device box pull-down menu for the remainder of the buttons. If you run out of buttons in CM Device 2, just start using CM Device 3. AH should recognize those different CM devices just fine.)
If you decide to go that route, you can test to see if you've got everything set up correctly before starting AH. Download the profile by pressing the appropriate key in the toolbar. Note that if you've assigned the same DX button (e.g., CM Device 2, button 3) to more than one physical button, you will get an error message here. Once you've corrected any such errors and successfully downloaded the profile, press the "Test/Calibrate" button in the toolbar. It should display a menu with each CM Device (e.g., CM Device 1, CM Device 2, and CM Device 3) that you've included in your profile. Select one of them and click OK. Now press the buttons you've assigned to the selected device and make sure they register in the display (the "LEDs" should light when you press the corresponding button) as expected.
It's probably not a bad idea to calibrate your axes, as well. To do this, press the "Direct" button in the toolbar and press the "Test/Calibrate" button again. This time, the three physical devices (i.e., Fighterstick, Pro Throttle, Pro Pedals) will be displayed. Select each in turn, and follow the calibration directions. When you're finished, make sure to press the "Mapped" button next to the "Direct" button in the toolbar. If you don't do this, your CH gear will not use your profile.
One more tip, make sure that you close down CH Control Manager before you start AH. The reason is that CH Control Manager includes the feature that when you press a button or axis, it switches to that button or axis in the programming display. Well, it still does this if you leave it running when you start AH and will cause a stutter when you move your axes and a slight delay when you press a key.
The advantage of using the DX button assignments and mapping your controls inside of AH is that it is relatively simple to set up. The disadvantages are that you lose a lot of programming flexibility and that every time you set up AH, you will have to go through the process of repgrogramming your keys (unless you copy over the appropriate file containing that information from your previous setup.)
Finally, I know it's a bit of a pain, but Control Manager does come with an integrated and well-written help file. If you have any particular questions, I'll be happy to help if I can. You can reply here or send me an e-mail.
Good luck!
- JNOV
