Jump to content

Raena Parx

Resident
  • Posts

    106
  • Joined

  • Last visited

Reputation

18 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Wow. Definately some great options. It's so awesome to have such great scripters here! And Gayngel, I really like the alternative of not having to use the llSensor altogether. Will definately be checking that option out also. Thank you!!! Thank you everybody!
  2. Hello. I'm using llSensor for the first time. My doctor wears a bracelet that sends commands to my button (this script that uses llSensor). Before any command is processed, this script (button) checks to be sure the doctor is within range of 2.5 meters. I had a problem with finding where to place the commands llSensor() and sensor (). I believe they are placed correctly, as the sensor does detect whether the doctor is close or not. However, the calling llSensor() command is later in the script. When the llSensor() command calls the sensor() subroutine, it detects the doctor and assigns a value of isDoctorNear=1 . This works fine, and debugging show that. But... The problem is once the sensor() subroutine is completed, the value of isDoctorNear ALWAYS comes up zero, even tho it was detected in the sensor() routine. This is the line directly after llSensor(). I cannot figure out why the value of isDoctorNear=1, and then the next script line llOwnerSay show it as zero value. It's a huge script, so I dummied it down to bare bones to show the problem. It most likely will not run as-is, but is more a placeholder so you can see the structure of the code. Any anyone explain why the isDoctorNear value changes on the next line after llSensor() ? And how to fix it? Thank you so much!
  3. Thank you so much for the explanation, and the code. I "kind of" understand it, but it is a little over my head yet. I did find a solution already. But I really like the code you gave me to check if the toucher is in the Region. Thank you so much!
  4. Oh cool! Thank you Quistess! I'll definately play with it. Thank you for explaining how it works ☺️
  5. Well...I rescind what I thought was the solution. lol So it worked perfectly in test environment where the strings were pre-filled when creating the stringnames. But when I got it into my build, it didnt recognized the strings as they had been updated throughout the code. Not sure why it would take the updated string values. So, I ended up having to just using the llOwnerSayTo command 7 times to get all the text to display. But it was MUCH faster then using InstantMessage! I never knew that command existed. So thank you!
  6. Thank you Quistess. I've never used the debug channel, how is it used? For debugging I usually just llOwnerSay().
  7. Just an update. The llRegionSayTo worked perfectly. Turns out it's so fast, it doesn't need text-line grouping like I thought it would from when I was using llInstantMessage. It displayed the text in order, privately and fast...awesome! Now if I can figure out how to avoid the timestamp when copy/pasting it from chat it'll be perfect lol. Thank you for the code Wulfie. Yours is the code I used mainly because I could understand it, and it was short and sweet and functional. I wasn't sure I understood the advantage of counting backward, so I used what I was more comfortable with. Though that may be a great option too if I understood it better lol. THANK YOU TO EVERYONE for being so helpful!!!. I really appreciate it!!!
  8. Just want to say thank you all again for all your help. I can try to do some coding on my weekend (which starts today). I really appreciate everyone's help!!!!
  9. Thank you Wulfie. The code is awesome, and will simplify sending all the strings. What I was trying to figure out tho, in the prior messages, is how to group the strings into larger strings that are as close to 1024 characters, so bulk-sending in a way. The code would need to calculate the length of each current string ( no problem there), plus the string length of next string, then decide if it can be added to a groupstring that's <1024 characters, and if so, how much space is left , then repeat til all strings are sent. I can probably figure it out, but I guarantee it'll be like 20 lines of code more than is needed lol. I'll let you know what I come up with so you can have a good laugh lol. πŸ™ƒ Thank you for your help
  10. Thank you for the suggestion. The receiving avatar would be on the same region because it's activated on-touch. The strings are already formatted with "\n'"'s, but vary a lot in size. I'm a bit lost on how the "For" operators works in .lsl. For example, i found this on the lsl wiki: /block statement integer a = 0; integer b = 10; for(; a < b; ++a) { llOwnerSay((string)a); llOwnerSay((string)b); } why does it start with a semicolon? does that mean there's no initializer? - i'm just guessing. and the ++a....is that a counter? meaning "a" will increment plus one each loop? trying to figure out how I would write a loop that reads all the data, one string at at time (so using lists for the string names, i'm guessing), and arrays?...(that's where I really get confused), then join the strings together into strings no longer than 1024 characters. Not sure I'm that program-savvy. But if I understand the concept, I might be able to pull it off. Thank you for your help
  11. Thank you. So just to confirm the IdOfAvatar is the Avatar Key, correct?
  12. BTW, I'm looking at the command - it goes to a channel (rather than an avatar key) - so how would I direct the output to the avatar that's inquiring? Thank you agin.
  13. Thank you Frionil. I didnt' even know that command existed (llRegionSayTo), I only knew of llRegion Say. I will definitely test it out! Thank you so much. β˜ΊοΈπŸ™ƒπŸ˜„
  14. Hello. I have several text strings (basically data fields), each with it's own string name. The strings range from short or long depending on the data needed. I'm trying to send these strings privately to the individual who requests them on touch, so I'm using llInstantMessage, but am running into a few issues. 1. If I send them one string at a time it's s-l-o-w a-s m-o-l-a-s-s-e-s. 2. There's no way to combine them into one long string before sending with llInstantMessage to speed things up since a string field cannot be more than 1024 characters. Can someone suggest the best way to send several text strings privately on-touch? Thank you in advance.
  15. Hi All. I've never worked with deformers before. I did purchase Bento Buddy 2023. I watched a tutorial that looked really easy here... https://www.google.com/search?q=deformer+with+bento+buddy&rlz=1C1UEAD_enUS1007US1007&oq=deformer+with+bento+buddy&aqs=chrome..69i57j0i546.4264j1j7&sourceid=chrome&ie=UTF-8&bshm=bshqp/1#fpstate=ive&vld=cid:e3c204c8,vid:VwZfIAycZBU I followed every step, with exception of instead of moving the breast bones, i moved the hip bones. I'm trying to make a deformer that makes you're avatar s-u-p-e-r skinny (like cartoon skinny) when worn. The only volume bones I see to edit on the skeleton are the hips so I tried to move them closer to eachother. I'm not even sure if I moved the bones correctly. I exported it as a deformer in Bento Buddy. I'm using Firestorm just to follow the tutorial. However, when I try to upload the mesh model, the physics tab gives me this error: "One or more dimensions is less than 0.5m, only hull-based (analyzed) physics shapes will work correctly." And...consequently, the uploaded model does not work. Any idea what may be causing this, and how to get around it? Or if I'm even doing this right? Any help is appreciated.
×
×
  • Create New...