CH Control Manager has no adverse affects, so long as you download the map and then quit the program before starting AH. (If you leave it running, it will cause delays and stuttering when pressing buttons and moving axes.)
The AH mapper works fine, but you are missing out on a TREMENDOUS amount of programming power if you don't use Control Manger with scripting. Maybe it's just that I like to program, but I think it is way too cool. Here are some of the things I've implemented with scripting:
1. I've set up two shift buttons (the pinkie and forefinger keys on the stick), so I am able to map absolutely any dot command that I would ever use to keys on my HOTAS (e.g., a full selection of ".speed" and ".salvo" commands, a full selection of ".radio" commands, ".squelch 1", etc.) Also, I use the pinkie button to toggle gun zoom and the forefinger button to call "check six!" I do this by parsing the buttons using time. That is, the shift buttons only perform their non-shift function (i.e., toggle gun zoom, "check six!") if pressed for a sufficiently short period of time. It works like a charm. For example, if I quickly press and release the pinkie button, it toggles my gun zoom, but it always works as a shift button.
2. I use the microstick as an engine brake for two-engined planes, so that the differential thrust generates yaw. I find that this helps planes like the 38 turn and hammerhead. If I pull the microstick to the left, the left engine brakes, inducing yaw to the left. If I pull the microstick to the right, the right engine brakes, inducing yaw to the right. If I center the microstick, both engines are controlled by the throttle input. If I press my first shift key, the microstick acts as a mouse, which is convenient for getting hte mouse pointer off the screen.
3. I have set up a number of view toggles. For instance, I define an elevated view for all planes using AH's alternate forward view, in which the "pilot's" head is as high as possible. This gives extra visibility over the nose for landing, taxiing, or trying to find that plane that you've pulling lead on. Also, sometimes I just want to maintain a particular view (e.g., elevated six view) without holding the POV hats. The view toggles allow me to do this.
4. I have set up "stick trim" that allows me to control AH's trim functions using my stick and rudder. When I activate the function (by pressing a particular key), the trim keys corresponding to the stick and rudder deflection are activated until I release the activation key or center the axes. Thus, for example, pressing the activation key and deflecting the stick axis left causes AH's left aileron trim key to be pressed. For me, this is a nice, intuitive way to trim the plane.
5. I have set up stick sensitivities that I can change during flight. For instance, I use one sensitivity for landing (particular helps when missing a wingtip) and another for combat.
6. You can set up "state machines" that can be used for any number of applications, such creating an arbitrrarily large number of modes.
The sky's the limit, really. I've used Cougar's programming package extensively, and it doesn't hold a candle to CH's Control Manager.
Just my $0.02,
JNOV
