PDA

View Full Version : cant get ANY scripts to work



gutted
23rd March 2004, 01:17 AM
i got my full CH setup last week, i have some background in C++ programming so i immediately decided to tinker with the scripting capability after setting up my controllers to mapped mode.

i've tried making several scripts and not one worked, though they compiled fine. i go into my game nothing happens, i look in the test/calib screen to see if its working.. nothing happens.

so i tried downloading some scripts, i would paste them in the editor.. download the map to the stick, fire up the game and try.. and no work.

hmmm

so then i tried out the simplest script i could find in the CMS help file. pasted it and downloaded the map to the stick.

SCRIPT
CMS.B1 = NOT JS1.B2;
ENDSCRIPT

button 1 should be the opposite of whatever state button 2 on my stick is. so i fire up the test/calib screen to check it. i dont touch anything, so button 2 should be OFF and button 1 should be ON.

nope... both are off. pushing button 2 just makes button 2 go on and off.

i've spent several hours wondering what's wrong, even unistalled everything CH on my computer and reinstalled it and still nothing.

any ideas? did i miss something trivial?

Bob Church
23rd March 2004, 01:26 AM
Well, this probably won't answer all your questions, but I suspect that you didn't assign CMS.B1 to anything when you did:

SCRIPT
CMS.B1 = NOT JS1.B2;
ENDSCRIPT

You've passed the inverted state of button 2 on the stick into the CMS.B1 variable, but that doesn't automatically come out anywhere. Up in the GUI, you then need to select the CMS Controls and assign CMS.B1 to go to something like Control Manager Device 1, Button 17 (or some button that's otherwise unassigned). After you download the map, if you look at the Control Manager Device in the test screen, you should see the 17th button and it should be "NOT JS1.B2".

- Bob

The StickWorks
http://www.stickworks.com

gutted
23rd March 2004, 01:47 AM
/me slaps head

that answers ALL my questions.

must have skimmed over that part of the help file, trying to get to the nuts and bolts of the scripting language :P