Jump to content

GadgetKit Vectoscope

Resident
  • Posts

    6
  • Joined

  • Last visited

Everything posted by GadgetKit Vectoscope

  1. Ah, just moving the llPlaySound to the top of the timer() event, alone, fixed it! Perfect! Conversely, adding a -1 after FRAGMENT_COUNT resulted in the Script Warning/Error/Debug box. But that doesn't matter, because the script works! A great big THANK YOU, again, for all of your help! 🙂👍💯
  2. Hmmmm... this worked nicely (thanks!), but with one odd wrinkle; it plays all 4 sound files, in order, but then immediately repeats Sound File #1 a second time, before ending. Otherwise, it's perfect. No error box, no constant looping.
  3. I just gave that a try. It worked on the first click, which seemed promising, but then a Script Warning/Error/Debug box popped up, telling me it could not find sound, so it was disabled for any further clicks/activation.
  4. First, thanks everyone for your help and patience so far, I really appreciate it. I re-tooled the script in such a way that it does precisely what I want it to do, with the major exception that I still can't get it to stop repeating the 4 sound clips in an infinite loop. Ditto the chat text (when included in the script; currently it isn't). A couple of variations I've tried either restricts it to the normal 2-sound-file limit (which doesn't loop), or which plays the 4 sound clips, in order, with no loop, but each sound file requires its own separate click of the prim to play (they aren't strung together). Just to clarify, this is what I want the scripted prim, which is a button that is worn by the avatar, to do: 1.) it can by selected/clicked by any nearby user, myself included. 2.) the click activates the string of sound files, of which there are 4, which play in order. 3.) this isn't crucial... but ideally, a text message plays, once, in local chat. 4.) after the 4th sound file plays, the sequence stops automatically, both sound and text, without the need to click the prim button a second time to stop it. To repeat it would require another click of the button. Seems like this would be very simple to achieve. Here's my simplified new version of the script, which is minus any chat text function (which, in its current looped form, spams local chat terribly): Again, this does exactly what I want it to do, except for the automatic, endless repeating.
  5. Thank you. That definitely got rid of the delays. The main problem now is the running timer; it stays in a loop. I've tested putting llSetTimerEvent(0.0) in various spots in the script, but that either does nothing, or pre-empts the 'Multiple Sound Fragments' feature (which allows the prim play 4 sound clips in order, rather than the usual maximum of 2), depending on where I place it. I think I'll just have to go back to square one and learn/re-learn lsl scripting basics. I seem to know just enough (usually by accident!) to sometimes tweak an existing script a little bit to my liking, but it's not as though I have a firm grasp of the concept of events, states, strings, constants, variables, integers, etc. I examine most scripts and my eyes glaze over and I get a bit lost.
  6. First off, forgive me, because I'm a beginner who barely knows what I'm doing, as far is scripting is concerned. For all I know, the answer to this is probably very simple and is staring me right in the face... I found an old, free script in my inventory, 'Multiple Sound Fragments Player", and tried to mod it into a hybrid with a "Sound & Text on Touch" script. The goal was to have a prim attachment play 4 sound files (rather than the usual 2), in a certain order, when touched. This version of the script does this, but unfortunately loops both the sound and the chat text indefinitely. I want to have it play all this stuff just once, whenever the prim is touched, with no automatic repeats. The other drawback is that there is a considerable time delay (6+ seconds) prior to the first sound clip playing and between the subsequent the sound clips. I've tried setting the llSetTimerEvent to lower numbers than 10, but it didn't seem to make any difference.
×
×
  • Create New...