ISSUE: Tutorial does not work

[Apprentice]

A syntax error, that's odd. Try changing the extension to .wav and see if it will compile like that.

Doesn't compile either, same error message . . .

[Boothand]

Could you post the entire script?

[Apprentice]

This is the working script:

 

 

affect ( "rotadoor1", /*@AFFECT_TYPE*/ FLUSH )
{

    task ( "drota1" )
    {
        rotate ( < 0.000 -90.000 0.000 >, 2500.000 );
    }

    dowait ( "drota1" );
}

 

This is when I try to add sound:

 

affect ( "rotadoor1", /*@AFFECT_TYPE*/ FLUSH )
{

    task ( "drota1" )
    {
        sound ( /*@CHANNELS*/ Include Error!!!, "sound/aurelia/holodeck_door.mp3" );
        rotate ( < 0.000 -90.000 0.000 >, 2500.000 );
    }

    dowait ( "drota1" );
}

[MoonDog]

Did you setup BEhaved properly? I don't think so. Follow these steps again.

 

http://jkhub.org/tutorials/article/148-icarus-scripting/

[Apprentice]

It was installed with GTK Radiant (1.4) . . .

[MoonDog]

Yes, but you should still setup the pref's properly........................................................................................................................................ I can do exasperated dots too. See?

[Apprentice]

[MoonDog]

Click set all options to JKA and set your prefs up again. I have a feeling you aren't pointed correctly at the SourceForBehavEd folder. It could also be that you aren't pointed at behaved.bhc for Command Description File. Try the usual Windows 7 junk of running in admin and compatibility just in case.

[Apprentice]

Don't know how but after resetting everything again, it works now. Only problem that I have that the sound is being played everytime I hit the trigger. Is there a way to play the sound only when the doors move ??

[Boothand]

You mean if you spam the trigger button while the doors are already moving?

If so, you could use the key "wait" on the door, in GTKradiant and set it to the equal amount of milliseconds that the door is moving. This will unable you to press the trigger until the door has stopped moving.

[Apprentice]

You mean if you spam the trigger button while the doors are already moving?

If so, you could use the key "wait" on the door, in GTKradiant and set it to the equal amount of milliseconds that the door is moving. This will unable you to press the trigger until the door has stopped moving.

That works but I was wondering if I could get the same result by scripting . . .

[Boothand]

To achieve the same result by scripting, you can use set_inactive (true/false).

 

Drag a "set" into the task, and find "set_inactive" under booleans. To bring up the true/false alternatives, it's a bit weird, but this is the way I make it work: Click OK after selecting set_inactive, and then double click on it again to bring the event editor back up. Now click the "helper" button and then just click "Reset!" again, and it should now display a true/false alternative. So if inactive is true, the trigger cannot be used, and if it is false, it is active and can be used.

 

So, put shortly, you can set it inactive in the task, and set it active again after the "dowait", with the same method. That means once it runs, it inactives itself, and after it is done (dowait) it becomes active.