Just wondering if trim controls can be put onto a potentiometer, or it its confined to a button. Potentiometers would give us actual trim wheels!???

(CFS2)
Any one know? ???

Forgot to say CFS2 and FS2002/2004 use more or less the same technique.

Welcome to the Homebuild Cockpits section Thunderboy, npbosch and decoy.

I don't know about CFS2 or 3 but in FS2004 if you go to the settings section and look in the joystick configuration assignments.... you can find all the settings that can be assigned to "axis" type copntrols....... ie. - potentiometers.

best,

.................john

PS:  (edited) In reading the recent messages, I just noticed that Will also mentioned this concept in the chopper collective question  .

Ok, Im not sure you can add the elevator axis to CFS2. Here is the data:

Analogue Axes
The analogue inputs are enabled by:
1.      Adding a 'bit' into the AXIS_FLAGS for that input. Add values together, as follows:
     1 for Axis 0 (the X axis, typically aileron)
     2 for Axis 1 (the Y axis, typically elevator)
     4 for Axis 2 (the Z axis, typically throttle)
     8 for Axis 3 (the R axis, typically rudder)
     16 for Axis 4 (the U axis)
     32 for Axis 5 (the V axis)
     64 for Axis 6 (this is actually the "POV", Point Of View hat)
     
     So, for example 15 indicates the usual basic 4 joystick axes (X,Y,Z,R).
2.      Adding 3 lines per Axis:
     AXIS_EVENT_nn=<control name>
     AXIS_SCALE_nn=<scale>
     AXIS_NULL_nn=<null>
     where:
     nn is the Axis number (00-06)
     <control name> is simply that: select a suitable analogue control from the list!
     <scale> controls sensitivity. For any well calibrated joystick, the value 64 is usually the best start here for all normal axes, although 128 for full throttle (THROTTLE_SET) works well. A negative number here reverses the sense of the control, making it increment with the opposite movement.
     Note: for discrete value axis controls, listed later, the SCALE value needs to be 1 or -1 (although the negative value won't find much use). Such controls need to be allocated only to Axis 6 in each Joystick section, as the other inputs will be affected by calibration.
     <null> is best set 0 for throttles and analogues other than the three primary flying controls, unless the analogue axis concerted has any "jitter" (i.e. is not stable at centre or either extreme, wherever the 'normal' setting is). The null zone on the main flying controls is a matter for personal preference-for helicopter flying I'd advise a very small amount!
     Note: Always set a zero value for the NULL zone for discrete value axis controls, as described later.
Note that, apart from the convention already adopted, and for compatibility, there is no specific requirement to associate throttles with Axis 2 and ailerons with Axis 0, and so on. However, you should note that the "centre" calibration system, as appropriate to aileron, elevator and rudder, is only applied to X, Y and R axes. Where centering is not important, as in most all other cases, this allocation is not really so relevant.
=================================
CFS2:

[JOYSTICK_MAIN {6F1D2B70-D5A0-11CF-BFC7-444553540000}]
LOCKED=0
AXIS_EVENT_00=AXIS_AILERONS_SET
AXIS_SCALE_00=127
AXIS_NULL_00=1
AXIS_EVENT_01=AXIS_ELEVATOR_SET
AXIS_SCALE_01=127
AXIS_NULL_01=1
AXIS_EVENT_02=AXIS_THROTTLE_SET
AXIS_SCALE_02=127
AXIS_NULL_02=1
AXIS_EVENT_05=AXIS_RUDDER_SET
AXIS_SCALE_05=127
AXIS_NULL_05=1
BUTTON_DOWN_EVENT_00=FIRE_PRIMARY_GUNS
BUTTON_DOWN_REPEAT_00=1
BUTTON_UP_EVENT_00=STOP_PRIMARY_GUNS
BUTTON_DOWN_EVENT_01=FLAPS_INCR
BUTTON_DOWN_EVENT_02=FIRE_SECONDARY_GUNS
BUTTON_DOWN_REPEAT_02=1
BUTTON_UP_EVENT_02=STOP_SECONDARY_GUNS
BUTTON_DOWN_EVENT_03=FLAPS_DECR
BUTTON_DOWN_EVENT_04=GEAR_TOGGLE
BUTTON_DOWN_EVENT_05=DEC_COWL_FLAPS
BUTTON_DOWN_EVENT_06=ORDNANCE_RELEASE
BUTTON_DOWN_EVENT_07=ORDNANCE_CYCLE
BUTTON_DOWN_EVENT_08=WAR_EMERGENCY_POWER
BUTTON_DOWN_EVENT_09=NUMPAD1
POV_MOVE_EVENT_00=PAN_VIEW
POV_MOVE_REPEAT_00=1
-------------------------------------------------------------------

The only thing I noticed is that the Axis #'s skip from 0-2, and then 5, with 3-4 missing. So maybe you can add:

AXIS_ELEV_TRIM_SET, But it looks like its not supported. Any thoughts?

Thanks! ???