Jump to content

Profaitchikenz Haiku

  • Content Count

  • Joined

  • Last visited

Community Reputation

304 Excellent

About Profaitchikenz Haiku

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Add to them "If SL was a game, what type would it be" I'll get me coat...
  2. Not sure anything lasting longer than 2 hours would qualify as a movie But if it was a movie, I'd title it "Pulp Friction"
  3. flashback to Rowan Atkinson "Will this wind be so mighty as to lay low the fundaments of the uuuuuuuurth?"
  4. Confusing, a 3-prim object linked together is one object, so just move the root to wherever you want it to go, with the caveat that you can't move more than 10 metres at a time (unless you use llRegionSetPos) If you're saying that in a large build there are three children that you want to move together as if they were a linked set than it becomes a matter for using PRIM_LINK_TARGET in llSetLinkPrimitiveParamsFast, but you will have to calculate three separate local position adjustments for the children.
  5. I beg to differ, they'd wrap the letter round a crossbow bolt and fire as far towards the target as they could.. That station pulls the bolt out of what it hit, checks the address, and fires it as far towards the target as they can...
  6. Let's see if I can slide this one past the censor-sensor... It could be the OP is embarrassed to post a message of the form "Error trying to play animation 'Deep-Eye-Watering-Bert-Fork' because ...."
  7. I vote we set up a "Preppers" version of SL using packet radio and Radegast. Then it will be immune to sudden loss of DNS.
  8. I've not had any problems with Radegast on Windows 10, but older viewers such as Alchemy, Onlook, and Ctrl-All_Studio ? all give the rainbow problem.
  9. I don't know for certain in LSL, but in other languages floating point calculations are always slower than integer-based addressing, which is what the two situations are here: either do sixteen FP calculations once and retrieve the results by two sets of lookups based on integers, or calculate whenever you want to access a cell. The implementation I am basing my judgement on is a 64 by 16 screen for a retro-computer display in SL, the volume of calculations would have been 1024 each time the display changed. The lists required to run the screen fitted easily into the script memory. Once memory has been grabbed for chunks such as the lists there is no further performance overhead. But since I'm as lazy as you and can't be bothered to make a test harness we're never going to know.
  10. I agree that for small numbers of cells calculations might be simpler, it's a trade-off between that and pre-calculated lookups which might be quicker for a busy script doing lots of updates such as a message board.
  11. Don't use llSetRegionPos. I assume this script is to go into the child prim to be moved up and down, so you need to use llSetPos, and the position you are going to be getting and varying should be relative to the position of the root prim in the link set. Use llGetLocal Pos which gives a vector of the child position relative to the root prim, and after adding to or subtracting from this value, use llSetPos to reposition the child prim.
  • Create New...