Are you ready for llDetectedTouch*() ?

Hanging at Qarl's Office Hour, learned that all the crunchy goodness in http://wiki.secondlife.com/wiki/LSL_Touch_Position is soon to be merged, targeted for the 1.21 release.

Like... wow!

I was born ready.

Been waiting for this since I learned of it on RobbieRaccoon's blog.

What's "the U direction of tangent space"?

Thanks!

Can some one plz explain this in English?

/me gets drool all over her keyboard.


Instead of just knowing that "a prim" has been touched, we'll be able to find out where on the prim the touch happened.

Easy example: picture the controls on a CD-player.. Back, pause/play, stop, forward, etc. Today, doing that in SL would require at least one prim for each control if you want to find out what the user is trying to do. With this new stuff, you can have just one prim with a texture for all the controls then have the script check where on the prim the touch happened to see what the user is trying to do...

Right Sindy -- Cheewah, I bet you'd understand if you followed the link above. I just happened to post the most gibberishical part of it, at least, to us non-compus-mentis folks.

Wow! now i see why you guys are so excited that is amazing. This is the first I have heard of this but then again I rarely get off the island (ha ha I am not a prisoner I am a free man!)

: )

The Latin term "Non compos mentis" means, in a UK legal context: "not of sound mind and understanding".

hehe I had to look that one up. I think I am gonna put that on all my letter head at work!

Note that I used "non compUs mentis", a play on the Latin with a slightly different implication.

This sounds cooooool! Can't wait to use it!

The other options in that post sound a little confusing, though, but I'm sure I'll figure them out

so this means more than one sit animation in one prim?

I have a feeling "sit" (and "edit" don't generate touch events at all, so if I'm following the thread of your thoughts there my thinking is "probably not how you mean". It sure would be great if a different parameter could be passed to your script depending on exactly where someone right-clicked to sit (or clicked to sit, if that's the default click action) but I don't think it works that way.

Someone please correct me if I'm wrong! That would rock!

But it DOES mean things like true UI components (sliders, etc.) on HUDs! Also things like easily placing markers on maps and such. This will be a huge leap in interactivity. The possibilities are endless. Hopefully we'll also get those other input methods in soon too (like the text box one we heard about a while ago). Then we can all go banana wild! Woo hoo!

There are other ways to do that, depending on what you mean. More than one animation, no problem. More than one sit-target, no problem (the script moves the av). More than one sitter, the script moves the av after sitting so the sit target has room for a new sitter (or vice versa; it could move the sit target rather than the av).

For the latter two, there are issues. Mainly, the sitter can't choose their position by clicking, they'd need to do it by explicit interaction with the script, such as menus or taking controls and using movement keys. These new functions could provide a different means of doing this, *after* sitting. It wouldn't be intuitive, and it might be more troublesome than helpful due to misclicks.

Heck, I'd be happy if it could just tell me which side of the prim was being touched.

That would be llDetectedTouchFace.

This looks amazing.

I wonder how lag will affect this.

If by that you mean will lag cause it to fail or return incorrect results, I doubt it. The viewer can tell exactly where you touched, no matter the lag, and it'd be the viewer telling the sim where you touched, as it's always been (though until now "where" has only meant "which prim".

I have an info board mothballed until this is released. There will be a lot fewer prims needed in such applications. And in just the twelve seconds I considered it I can think of two other projects of mine that will benefit.

Huh. On the other hand, llDetectedTouchPos() will be complately useless for attachments if it'll only return region coordinates. I'd MUCH rather see it return prim-local coordinates, from which we can calculate anything else appropriate to the prim/object. Hmm. I'll see if I can give that feedback somewhere.

EDIT: Oops. I can see that's been debated quite a bit in the JIRA already, but I did have another simple and useful suggestion that I have added to it. I hope it's not too late for it to be considered.

What Anti and Lear said, but with a slight, almost useful twist: Iff the sat-upon prim does not have a sit target, at the time the CHANGED_LINK event is raised, the sitting avatar's location still reflects where they're standing. (Rotation too, I suspect, though I've never tried that.) So I have a dopey 1-prim sofa made from a carved up tube that will sit the avatar in the vacant seat nearest where they stand when they try to sit. Of course, it's subject to all the vagaries of convincing an un-sit-targetted prim to let anybody sit on it at all. Hence "almost useful."

It would indeed be grand to get llDetectedSitPos() or the like, but I don't think this is it.

Hey I just found out about these proposed features.

Quick everyone visit the JIRA and vote for this...

http://jira.secondlife.com/browse/SVC-1902?ticket=ST-204-W26G5cBqg9NJMz4vbXYqvb1Di105HQyoNpv-20

Texture coordinate maps are sometimes called "UV maps" because the texture axes are labeled U (horizontal) and V (vertical), probably just to distinguish them from the X and Y axes of 3-D space. In this case "U direction" basically means the positive horizontal axis of the relevant texture and "tangent space" is a plane which is, well, tangent to the surface.

Just for clarity, it's not really necessary to vote for a jira once it's been assigned; after it's been imported, it won't be re-triaged and re-prioritized just because more people vote for it. And in this particular case, the whole jira was created by the Linden who took on the project, as a way of getting developer feedback. This particular one has been out there for a while, but I started this thread now because Qarl sounded pretty confident that it will be in the next generation of releases (1.21) and hence might be worth considering what fun can be had with it when it's finally available.

Thanks. I always wondered what UV meant too, but not being much of a texture guy, didn't dwell on it.

Too awesome!! I had been thinking of making a few 'button' controlled objects, and that little script will prove totally useful! Kinda feel sorry for all those people that have used prims and such in the past though.

Can't wait to use it! =)