Jump to content

Phate Shepherd

Resident
  • Content Count

    160
  • Joined

  • Last visited

Community Reputation

67 Excellent

About Phate Shepherd

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. There are a number of them... pick one based on the features you need: http://wiki.secondlife.com/wiki/CatText
  2. Rigging clothing is far, far easier if you do have the dev kit. I doubt the Maya female shape weights are going to be anywhere near what a particular dev kit uses.... especially when you take into account fitted mesh with the added volume bones. It is far easier to build your mesh to the dev kit, and then copy weights from the dev kit. (There are a variety of steps that can help with this, like using a shrinkwrap modifier before copying weights.) What you will run into really fast is the limit on total weights allowed per-vertex. SL only allows 4. This wasn't much of a problem with non-fi
  3. What's sad.... I forgot I submitted that before the previous reply.
  4. Not sure it has been mentioned, but the 10,000 item limit isn't just imposed on individual objects within a coalesced group, but also on object inventory within those objects. So, say you had just 2 boxes of DFS stuff, each with 5001 items in them. You now can't rez the coalesced group that is just 2 boxes. This bit me in the butt as one of my products has over 4000 items in each objects inventory. So, rezzing/deleting/picking up more than 2 of them will trigger the "No can do" error. I can't remember if I ever got around to submitting a JIRA request that coalesced groups be deprecated/
  5. If that were the case, the gnomes would all be sporting Rapunzel length hairstyles. Using the id key field as a second string is so commonplace that a significant number of beds and chairs in SL would break if it were changed. Several very popular scripts rely on it, such as AVSitter and FURWARE text. llMessageLinked Wiki: "You can use id as a second string field[2]. The sizes of str and id are only limited by available script memory."
  6. Many good points, but I can see that without clarification of intent, and assuming something like shooting a bullet, it wouldn't be unreasonable to want to have an unequivocal answer to "Did I hit my target, or did something get in the way?"
  7. Scripts have no way to detect when an animation loops. You can create a "sequence" in avsitter that changes animations every x seconds, but there is no guarantee that it will coincide with the end of the animation. That also doesn't automate changing positions, just automates changing animations. To change seating position, you would have to have a script that monitors the link messages from avsitter when someone sits, and then issue commands to avsitter to move that person from position to position. It could be a little tedious to keep track of who is seated, where they are seated, what
  8. If you just wanted it to face the closest person, shouldn't need camera perms... just their position to calculate the relative rotation between the two positions? It would look strange switching from person to person as other people got closer. (partial pseudo code) Set up llSensorRepeat for avatars in state entry. Limit range to maybe 20 meters. In detected event: vector r = llRot2Euler(llRotBetween(llGetPos(), llDetectedPos(0))); llSetRot(llEuler2Rot(0, 0, r.z)); (Or some variation on this) It is driving me nuts.... I can't remember the movie where a guy ge
  9. Rick-Rolled on the sl forums. Well done PH, well done 😉
  10. Funny you say that. Linden Lab created Sansar to do just that... after years of development, it didn't work out as expected. It used c# as its script engine. Many will argue about why it didn't succeed, but in the end, having "better" technology isn't always the solution.
  11. I'd say about as far as you could go before losing your mind would be something like a BASIC interpreter with a text only, or very low rez B&W display. I've done 128x128 bitmap displays in SL without using MOAP. Going much beyond that and it gets complicated very fast. An 80x24 text display would be easy enough. I've seen LSL scripts for parsing math, but can't remember if it could handle variables.
  12. linkset numbers don't change unless you add/remove/relink prims in the object. What does happen is that the viewer goes stupid and incorrectly tells you what the link numbers are. I know Firestorm does it, not sure about others. Relogging is one way to see the correct link numbers again... picking the item up and re-rezzing should too.
  13. When speed isn't particularly an issue, I like to take that same method and turn it into a function... it also avoids having to have a change event handler to detect when the linkset is changed. integer NameToLink(string name) { integer count = llGetNumberOfPrims(); integer i; while (i < count) { ++i; if (llGetLinkName(i) == name) return i; } return 255; } // Now you can reference prims by name instead of number anywhere in your code... llSetLinkPrimitiveParamsFast(NameToLink("Knob"), [ PRIM_COLOR, ALL_SIDES, <1, 0, 1> , 1 ]);
  14. I can barely code in C, never-mind C++ or any objective languages and managed to compile the MacOS SL viewer a couple years back to add in the mirror diff. Compiled the PC version as well (in-world mirrors refused to work on the Mac, but the viewer ran fine.) Took about an afternoon of setting up the dev environment according to the wiki. I doubt that just adding a command line switch to build an M1 version or a fat binary with both X86 and M1 code will be that easy due to numerous tools needing fiddling with to make them behave under Big Sur. Its going to take a Mac die-hard at LL to convinc
  15. If you are trying to send more than 1024 bytes, I'd be looking at something simpler... splitting the string into smaller chunks like 512 bytes, and putting a header on the front with a x of y parts and timestamp info on the front. Then reassembling on the other end if all parts have arrived, and the timestamps match. (Messages aren't guaranteed to arrive in order)
×
×
  • Create New...