@ Karnak:
The Control Manager of course has an online-help, but you're right: there are no printed manuals - since the CHs can be bought separate and combined any way you like, providing a paper manual would increase the price, unfortunately.
On the boards of
The CH-Hangar you can find a "Dummie's Guide" and a pdf of the online-help (somewhere... feel free to contact me if you shouldn't be able to find it).
As for the CHs being hard to map and/or hard to program... you must be joking!
For an absolute beginner, CH's GUI with simple drop-down menus definitively is much easier to use than TM's text-based mapping with its DOS-like slash-codes.
For a normal user a GUI still is easier to use than a text-based system.
For an experienced user who actually is interested in really programming his controllers (as opposed to simply mapping it), Bob Church's current state of CH's scripting with its plain text statements and functions definitively is much easier to get into than Bob Church's original (in the meantime ancient, however) logical programming with its raw and rough bit-wise digital logic!
Yes, that's right: it's the same man's work we're talking about: it was Bob Church who introduced true programmability (on a rather basic and raw level, but powerful anyway) to the TMs, and it was (and still is, mind) BOb Church who introduced true programmabilty (on a really sophisticated level) to the CHs. The programmability of today's HOTAS Cougar is based on what he had developed for TM's F-22 Pro almost a decade ago, and Guillemot just slightly enhanced and improved it for the HOTAS Cougar - but they did not develop it any further. But Bob Church developed (and still is developing) CH's Control Manager with its scripting further. Draw your own conclusions...
@ Wilbus:
At least it's no hardware problem - no spiking pot, I mean, for the stock springs
could be considered a hardware problem.
One thing to keep in mind while modifying your controllers' analogue settings: if you do so, do it either
only via the game's control-options,
or only via the stick's software - if you set up a custom response via both ways, i.e. set a custom curve in the CCP or the .tmJ
and modify the settings in the game's control-options, then you apply the modified settings on an already modified axis! No way to predict the results of such a mess...