PDA

View Full Version : Do you profile your controls or use ingame configuration?



galneon1
06-04-2008, 06:23 PM
I just got a HOTAS and am struggling with constantly changing controller IDs (I have other gamepads plugged in as well)... I'm wondering if most people manage their controls in profiling software using keymapping while keeping in-game keys default, or if they configure all controls in the game itself (save special controls that can only be profiled, such as stick-mouse functionality on a CH Pro Throttle, for example). Which do you recommend? I have a Fighterstick and Pro Throttle.

R_Target
06-04-2008, 07:05 PM
The controller software is good if you're running out of buttons and need the extra functionality, but I don't even have all my buttons assigned yet. Using TrackIR frees up a lot of hat switches. http://forums.ubi.com/groupee_common/emoticons/icon_cool.gif I do use the CH Manager to set a gain curve for my rudder pedals, and IL2 JoyControl (http://mission4today.com/index.php?name=Downloads&file=details&id=1021) to set sensitivities, filtering, and deadzone on stick, throttle, and pedals.

galneon1
06-04-2008, 07:21 PM
Thanks, it looks like I'll only need CM for special functions I can't set in the game. Now my controller IDs keep switching so I keep having to redefine my keys... There's no way to set controller IDs in XP, but can you specify a component as the main controller in IL2? Currently, my throttle has ID1, stick ID2, so the input options menu only works for the throttle. This is maddening.

Chris0382
06-04-2008, 07:51 PM
Re-assigned controls and a little script.


// CMS Script File

SCRIPT

//ALL FLAPS UP OR DOWN TOGGLE

IF (JS1.B4 AND JS1.B6) THEN
CMS.B1 = TRUE;
ELSE CMS.B1 = FALSE;
ENDIF

//RUDDER MOVEMENT

// Rudder Iinitial Centering
IF( FIRSTSCAN ) THEN
CMS.A3 = 128;
ENDIF

//Incase Immediate Change in Rudder Direction Needed.

SEQUENCE
WAIT( JS1.B8); //Sets AXIS-3 to Center Immediatly
CMS.A3 = 128;
ENDSEQUENCE

SEQUENCE
WAIT( JS1.B10); //Sets AXIS-3 to Center Immediatly
CMS.A3 = 128;
ENDSEQUENCE

//Moves Rudder Left or Right

TIMER ( INTERVAL, D1, 1, 1 ) = JS1.B8 AND NOT JS1.B4;
TIMER ( INTERVAL, D2, 1, 1 ) = JS1.B10 AND NOT JS1.B4;
IF ( D1 ) THEN
CMS.A3 = CMS.A3 - 1;
ENDIF
IF ( D2 ) THEN
CMS.A3 = CMS.A3 + 1;
ENDIF

//PREVENTS X-AXIS OVER-TRAVEL

IF ([CMS.A3 > 255]) THEN
CMS.A3=255;
ENDIF
IF ([CMS.A3 < 0]) THEN
CMS.A3=0;
ENDIF


// First set up an interval timer to generate the clock
// ticks. The timer is active when the hat is centered.
// The js1.b21 reference is hat center.
//
TIMER( INTERVAL, D3, 1, 5 ) = JS1.B21;

// Now see if the timer ticked
//
IF( D3 ) THEN

// If it's too high, drop it by 1
//
IF([ CMS.A3 > 128 ]) THEN
CMS.A3 = CMS.A3 - 1;
ENDIF

// If it's too low, increase it by 1
//
IF([ CMS.A3 < 128 ])THEN
CMS.A3 = CMS.A3 + 1;
ENDIF
ENDIF

//END OF RUDDER SCRIPT

//CONSTANT BOMBING

TIMER ( INTERVAL, D5, 1, 5 ) = JS1.B3 AND NOT (JS1.B4 AND JS1.B3);
CMS.B7 = D5;

//COCKPIT VIEW TOGGLE

IF (JS1.B4 AND JS1.B2) THEN
CMS.B8 =TRUE;
ELSE
CMS.B8 = FALSE;
ENDIF

//EJECT "CTRL-e"

IF (js2.b1 and JS1.B4 AND JS1.B5 AND JS1.B2) THEN
CMS.B9 = TRUE;
ELSE
CMS.B9 = FALSE;
ENDIF

//POSITION MOUSE OVER MAP

IF (JS1.B5 or JS1.B7) THEN
SCREENX = 1450;
SCREENY = 100;
ENDIF

//MINIMAP ZOOMING "R-CLICK USIN JS1.B5"

TIMER ( INTERVAL, D11, 1, 7 ) = JS1.B5 AND NOT (JS1.B4 AND JS1.B5);
CMS.B11 = D11;

TIMER ( INTERVAL, D14, 1, 7 ) = (JS1.B7 AND JS1.B4) ;
CMS.B14 = D14;

//ZOOM IN "KP-4" JS1.B7

TIMER ( INTERVAL, D12, 1, 5 ) = JS1.B7 AND NOT (JS1.B4 AND JS1.B7);
CMS.B12 = D12;

//ZOOM OUT "KP-6" JS1.B9

TIMER ( INTERVAL, D13, 1, 5 ) = JS1.B9 AND NOT (JS1.B4 AND JS1.B9);
CMS.B13 = D13;

//JS1 SHIFTED HAT COMMANDS

IF (JS1.B4 AND JS2.B25) THEN
CMS.B17 = TRUE;
ELSE
CMS.B17 = FALSE;
ENDIF

IF (JS1.B4 AND JS2.B27) THEN
CMS.B18 = TRUE;
ELSE
CMS.B18 = FALSE;
ENDIF

IF (JS1.B4 AND JS2.B29) THEN
CMS.B19 = TRUE;
ELSE
CMS.B19 = FALSE;
ENDIF

IF (JS1.B4 AND JS2.B31) THEN
CMS.B20 = TRUE;
ELSE
CMS.B20 = FALSE;
ENDIF

//SNAP VIEWS

IF (JS2.B25 AND NOT JS1.B4 AND JS2.B25) THEN
CMS.B21 = TRUE;
ELSE
CMS.B21 = FALSE;
ENDIF

IF (JS2.B27 AND NOT JS1.B4 AND JS2.B27) THEN
CMS.B22 = TRUE;
ELSE
CMS.B22 = FALSE;
ENDIF

IF (JS2.B29 AND NOT JS1.B4 AND JS2.B29) THEN
CMS.B23 = TRUE;
ELSE
CMS.B23 = FALSE;
ENDIF

IF (JS2.B31 AND NOT JS1.B4 AND JS2.B31) THEN
CMS.B24 = TRUE;
ELSE
CMS.B24 = FALSE;
ENDIF

ENDSCRIPT



//MOUSE LOOK ON 8-WAY HAT

IF( NOT XRELATIVE ) THEN
CMS.A4 = 128;
ENDIF

IF( JS2.B27 AND NOT JS1.B4 ) THEN
CMS.A4 = 250;
ENDIF
IF( JS2.B31 AND NOT JS1.B4 ) THEN
CMS.A4 = 5;
ENDIF

IF( NOT XRELATIVE ) THEN
CMS.A5 = 128;
ENDIF
IF(JS2.B25 AND NOT JS1.B4) THEN
CMS.A5 = 5;
ENDIF
IF (JS2.B29 AND NOT JS1.B4) THEN
CMS.A5 = 250;
ENDIF

//AILERON TRIMMING

// AILERON Iinitial Centering
IF( FIRSTSCAN ) THEN
CMS.A6 = 128;
ENDIF

//Moves AILERON Left or Right

TIMER ( INTERVAL, D1, 1, 1 ) = JS1.B4 and JS1.B27;
TIMER ( INTERVAL, D2, 1, 1 ) = JS1.B4 and JS1.B31;
IF ( D1 ) THEN
CMS.A6 = CMS.A6 - 1;
ENDIF
IF ( D2 ) THEN
CMS.A6 = CMS.A6 + 1;
ENDIF

//PREVENTS V-AXIS OVER-TRAVEL

IF ([CMS.A6 > 255]) THEN
CMS.A6=255;
ENDIF
IF ([CMS.A6 < 0]) THEN
CMS.A6=0;
ENDIF

//END OF AILERON SCRIPT


//MAP TOGGLE "u"

IF (JS1.B5 AND NOT JS1.B4) THEN
CMS.B10 = TRUE;
ELSE
CMS.B10 = FALSE;
ENDIF


/FLAPS-15 MOVEMENT WITH AXIS 6

//FIRST PART INCREMENTING

// Following sequence determines if incrementing the flaps
// has been requested.
//
sequence

// Wait until js1.b29 closes.
//
wait (js1.b29 and js1.b4);

// Set the a36 flag to "1" to enable incrementing.
//
a34 = 255;
a36 = 1;

// Increase the target flaps value by 20.
//
a35 = a35 + 15;

// Prevents over travel greater than 255
//
if([ a35 > a34 ]) then
a35 = a34;
endif

endsequence

// The following sequence increments the flaps to the new
// target value.
//
sequence

// See if the increment flag is set
//
if([ a36 == 1 ]) then

// It is set, add 2 to the flaps register
//
cms.a1 = cms.a1 + 2; // movement

// If the flaps value is has passed the target
// value, set the target value and disable the
// increments by clearing the a36 flag.
//
if([ cms.a1 > a35 ]) then
cms.a1 = a35;
a36 = 0;
endif

Bearcat99
06-05-2008, 05:45 AM
Originally posted by galneon1:
Thanks, it looks like I'll only need CM for special functions I can't set in the game. Now my controller IDs keep switching so I keep having to redefine my keys... There's no way to set controller IDs in XP, but can you specify a component as the main controller in IL2? Currently, my throttle has ID1, stick ID2, so the input options menu only works for the throttle. This is maddening.

Go to : C:\Program Files (x86)\Ubisoft\IL-2 Sturmovik 1946\Users\doe
with doe being whatever user you use as the pilot that is you.. I use a different one so mine has my name... it will use whatever you have as the pilot's last name.. not the nickname.. anyway.. R click the settings file and then L click Properties. Make sure it is NOT set as read only.

As for your original question.. I use the profiling software... IMO that is the best way to get full functionality out of any joystick. If you just assign the controllers in the sim as in Flaps = ID2 button 1 etc .. you will be limited to the number of inputs on your stick. Using profiling software you can take an 8 button joystick and turn it into a 14 button joystick by simply setting one button as a switch and then assigning the appropriate commands in the sim. For example... set one button to CTRL.. then whatever functions you have set for the other 7 buttons... A,B,G,X etc... set another function as CTRL+X... and you can use one key for two commands... if you set your CTRL button for comms then you also have comms on the joystick... Not having to take your hands off the stick will definitely increase your flying skills. In your case with a HOTAS it is even better... I have every function in the sim programmed on my sticks.. it takes a little while but once you remember it you remember it.. so you arent saying... "CTRL+X is drop tanks.." You are saying "The A button in mode 2 is drop tanks.. ) I have my MSFFB2/X-45 combo set up set so that on the X-45 each mode is for different functions.. for instance.. Mode 1 is TO & Landing.. so my wing fold (which is set as a two handed command so I dont fold my wings in flight accdentally), canopy, tailhook, chocks, landing gear (manual & auto) and a few other things.. are all set in mode one... Mode 2 is combat/flight so things like nav lights (which we use to locate each other in the air since although we fly with icons they are very tight so if you are more than .8 away you wont see a friendly icon, .7 for enemy), supercharger, drop tanks etc are in mode 2... Mode 3 is for rarely used things ... and miscellaneous functions like auto pilot, reticle dimmer etc...

Jyust something to think about..

By backing up your users folder you can make sure that in the event of a system crash or HD failure you can re-install all your controls with a few clicks instead of having to reprogram everything... just back up all your profiles and your users folder.

galneon1
06-06-2008, 01:26 PM
Thanks guys, I think I've found a good balance. The profiling software effectively overrides Windows' IDs, and I'm toying with scripting now.