Very, very basic question

[Malta]

This is a very, very basic question. I have been trying to get to the equivalent of "Hello World!" in CMS scripting with no luck. Reading the help file a couple of times still hasn't gotten me there. :wacko: How do you get CMS inputs recongized under directx?

This is what I have done so far: Open CHCM-> Map Wizard -> Figherstick, ProPedals-> Don't combine Controllers-> Do include CMS cabability ->Finish to create a blank map. The Program Settings, Fighterstick, Pro Pedals, and CMS Controls Device Tabs are shown.

I write a basic script using the CM Editor:

script
IF (JS1.B1) THEN
CMS.B11 = TRUE;
ENDIF
endscript

Test the script, download the map, test it, but it behaves as in direct mode with the above script not working. :(

I have the CM Device 1 shown under Figherstick, the CM Device 2 under ProPedals, nothing is shown under CMS Controls but directx is checked . Do I need to map the CM Device 1 (the Fighterstick) to the CMS controls? If so, is there some sequence?

If there is a FAQ or some basic scripts/map files that would help. However, I think I am at the "communicating with the device" stage here.



Any clues are much appreciated,


Malta

[Malta]

Hi again,

I found an answer to my previous question. I assigned "directx CM Device 1" and "directx control button 11" to "CMS Controls" button 11 (CMS.B11). That allowed "directx button 11" to become 'true' when the Figherstick button 1 (JS1.B1) was pressed. I noticed along the way that I could not assign the Fighterstick button 11 to "CMS Controls" button 11 using the same directx device (CM Device 1) and directx control (button 11).

Can you assign two directx buttons to a another single directx button? For example, If a you want gun camera and guns for JS1.B1 on a Figherstick then do you need to go outside of directx and map keyboard commands? Maybe I am too caught up in directx.



Regards,

Malta

[Bob Church]

No, and DirectX is better than characters if it's available so don't worry about getting "too caught up". :) The trick there would be to split the button down in the script:

script
cms.b1 = js1.b1;
cms.b2 = js1.b1;
endScript

Then assign guns to cms.b1 and gun camera to cms.b2 up in the GUI. Actually, that's more for illustration since I think that's what you were looking for. Script assignments don't limit button assignments. For example, if you wrote:

script
cms.b1 = js1.b1;
endScript

you could assign the guns directly to the trigger up in the GUI and just have to use CMS for the camera control. There's a sample in the Users Guide that uses an OFFDELAY to hold the gun camera on for some amount of time after you release that you might want to look at, too, if gun camera is really what you're interested in.

- Bob

The StickWorks
http://www.stickworks.com