
hen
I first discovered the Controller Command Module, I found it a
little confusing. Then I read the "manual" a little more closely,
found a basic tutorial and now can't figure out why more people don't
use it!During normal operation, the user will see this "console" screen. After enabling the appropriate template (more about templates in a minute), the "minimize" option will place the CCM in your systray, ready for use with FS2000, FS98, X-Plane or more.
To fully utilize the CCM, you'll need to specify at least one template (which essentially identifies the flightsim you be flying - it will also work with many games) and the keystrokes you want to be available with your joystick/controller.
Here you can see the configuration screen. I've specified my CH Yoke
LE. Mine works off the USB port, but CCM will also work with devices
running via the standard gameport.
On the left side you can see the "events" listed. You can assign keystrokes, force-feedback effects, sound files and mouse clicks to your joystick/controller. The mouse clicks have certain, obvious limitations to them, but the fact they can be used at all is a tribute to the flexibility and versatility of this utility. A typical design session begins with the keystroke events.
The user establishes a "profile" and identifies the buttons/functions on the controller, giving them "names" that better identifies them. After all, it can often be confusing when referring to "button 6" and trying to remember which button that actually is. In my case, I referred to buttons as "left inside", "left outside", "top left button" and "top left rocker" to better identify which physical button/rocker I would be using.
On the left side you can see the keystrokes I've recorded for use with CCM. To "assign" the keystrokes to a button/rocker on the controller, you simply drag and drop from the left side to the right side and presto! - you've assigned the keystroke sequence to the controller.
You can also see in the above screen shot I'm using the FS2000 template, the controller is the CH Yoke LE and the Profile is FS2000. Obviously, one could use the same controller with different profiles and different templates.
Note also the row of what looks like LEDs near the right center of
the picture. These are used for the various "modes" CCM supports.
There are up to five available modes. In each mode, the buttons (and
even the axes if you like!) can assume different functions. Since I'm
using keystrokes to change modes, all ten buttons on the controller
can have functions in each mode. Theoretically, that gives me 50
different programmable functions through the five modes. I'm
currently only using two modes - I'm darned if I can figure out what
else to do with the other available modes!
Using my CH yoke for FS2000, gives me "normal" functions in mode one - I can control rudder, ailerons, throttle, gear, flaps, trim, prop and mixture (and the differing views with the hat switch). Switching to mode two gives me specific control over FSNavigator. I can toggle FSNav on and off, dock it, zoom in and out, click on the "follow aircraft" function and select any of the three views (map, plan and FMC) offered while viewing FSNavigator - all from the yoke!
CCM is offered as shareware by Sim Systems. At $29 U.S. the price is comparable with most of the currently popular shareware add-ons many of us are using with FS2000. Registration keys are distributed in a similar manner (such as Radar Contact, FSNavigator and FSTraffic) to other shareware add-ons. Once I decided to purchase CCM it only took a day or two to receive the registration key. Without the key the user is only allowed 15 minutes of operation.
With the comprehensive documentation and support offered by Sim Systems, I've found this utility to be very enjoyable. I would rate this product 90 out of a possible 100.
Visit Sim Systems web site.
Download
the Controller Command Module demo.
Art Burke
ABurkeNC@aol.com