Innula Zenovka

Intan is a system, and a very good one, that rezzes poseballs for couples dances all over a sim, if you want. You touch a remote unit -- which can be anything that contains one of the copiable Intan remote scripts, and this gives you a menu of the couples dances you've loaded into the main unit. The main unit, which can be hidden anywhere, then delivers a pair of posealls to where the toucher is. The couple jump on and and off they go, tripping the light fantastic. They delete themselves when you get off. The system doesn't, as far as I recall, come with any dances, but the great thing about it is that you only need to buy one copy of each dance you want in order to animate as many people as want to dance it. So it's ideal for large clubs. It supports couples dances from most of the main animators, and isn't too difficult to set up, so long you're good at reading instructions and following them carefully. Otherwise Intan can recommend trained people who will install your dances for you for a very reasonable fee. Danceballs, of which there are many, are good for individual dancers. Again, you only need one copy of each dance to animate multiple people. Basic idea is you touch the big dance ball (typically it's rezzed well overhead) and it offers you a menu of dances from which to choose. So an ideal set-up for you would be an Intan for couples and two dance balls for singles, one with men's dances and one with women's. The only thing to watch out for is that you buy singles dance balls that are capable of delivering different dances to different people at the same time (unless it's a line-dancing club or something!).

Glad it helped. I think if you want to control the speed, llRotLookAt might be what you want (it works on both physical and non-physical objects) and, as I only discovered the other day, with Void's help, you can just use the formulae Chalice gives there to get the rotations you need for the rotation "target" in llRotLookAt. Certainly worth a play.

I asked Blondin Linden about this at the Adult Content Users Group meeting that's just finished. He confirms it's a mistake and has promised to get it fixed.

We used to have high hopes for llCastRay way back when. Since the only place it works at present is, apparently, mesh-enabled sims on Aditi, is it reasonable (and/or correct) to infer that it might hit the main grid if and when mesh does? And if we do get it, might that not provide another option?

I am not sure I understand exactly what you want to do, but you might find this little tutorial by Chalice Yao over at SLU helpful. Even if it's not what you're trying to do, it's still worth a read -- it was her walkthrough that got me on the road to understanding how to use llRotBetween.

It's one of those things that you think might be useful, but I really don't think it is. People who script stuff for RLV (as I do a bit) have had that functionality for ages -- @getdebug_AvatarSex -- but I've never found a use for it in practice, as opposed to theory, and I've never, in fact, seen it used.

As Peter and Rollig have said, using collision events with a melee weapon like a sword isn't going to work. The usual way to do it, as I understand it, is to fire off llSensor in the same control event you use to swing your sword. If it detects your opponent is standing just in front of you, then you register a hit.

Thanks for the heads up, Nyll. I've put this on the agenda for Blondin Linden's next Adult Content User Group meeting (http://maps.secondlife.com/secondlife/Bronlen/107/224/36 tomorrow, 18 April, at 11 am SLT, if anyone wants to attend). ETA -- For heaven's sake! I've just tested it by creating an alt and verifying her with my UK passport number. It accepted it with no difficulty. Apparently, as PeeWee suggests, Jeremy has got it completely wrong. He seems to have confused Age Verification with Payment Info, which many people do, of course, but not all of them are paid by LL to write articles in the Knowledge Base, and then has further compounded the error by, it would seem, getting it mixed up with fact PayPal hasn't worked for non-US residents for several months. If he isn't sure, why on earth can't he ask one of his work colleagues to check what he writes?

As PeeWee suggests, you need to set your preferences generally to be able to access Adult content. Your Preferences tab should, in a V2 viewer, look something like this. After you've set it, you need to relog.

No, you won't hear anything about the result of your report; see Linden Lab Official:I've filed an abuse report, I haven't heard a thing, and the offender isn't banned -- why? LL used to publish a digest of "incident reports," at least those that resulted in any action being taken, giving the time and place of the incident and noting what was done as a result, but no names. I think it was last updated in January last year and seems to have vanished since.

Are there any megaprims close by (maybe a sim surround or a giant sculpted prim) and are you trying to sit on some scripted furniture that offers a variety of sits but doesn't use poseballs? This sounds like a very common issue, you see, that drives furniture makers like me nuts. For technical reasons I won't bore you with, if you're inside the collision box (which isn't the same as what you can see, necessarily) of a large prim and try to sit on certain things, the sim gets confused and thinks you're trying to sit on the sim surround or the giant rocks or something, rather than the furniture. There is a workround, fortunately, most of the time. Simply drop this script default{ state_entry() { llSitTarget(<0.0,0.0,0.1>,ZERO_ROTATION); llRemoveInventory(llGetScriptName()); }} into some of the child prims of the furniture on which you're having difficult sitting -- doesn't matter which prims. Just use Edit-Linked Parts and drop this into chair legs or whatever. It will then delete itself after setting a dummy sit target and then, with luck, you should find you can sit on stuff.

That sounds like a looping error to me. Try integer TEXPointer = 0; list TEXLISTTemp = llCSV2List(llStringTrim(gNotecardDataTEX,STRING_TRIM)); integer max = llGetListLength(TEXLISTTemp) -1; llOwnerSay(llDumpList2String(TEXLISTTemp,"\n")); while(TEXPointer < max ) { integer wall = (integer)llList2String(TEXLISTTemp, TEXPointer++); string tex_name = llList2String(TEXLISTTemp, TEXPointer++); vector repeats = (vector) llList2String(TEXLISTTemp, TEXPointer++); vector offsets = (vector) llList2String(TEXLISTTemp, TEXPointer++); float rot = (float) llList2String(TEXLISTTemp, TEXPointer++); vector color = (vector) llList2String(TEXLISTTemp, TEXPointer++); float alpha = (float) llList2String(TEXLISTTemp, TEXPointer++); llSetLinkPrimitiveParamsFast(wall, [PRIM_TEXTURE,0,tex_name,repeats,offsets,rot]); llSetLinkColor(wall,color,0); // llOwnerSay("Wall is "+(string)wall+":"+(string)[PRIM_TEXTURE,0,tex_name,repeats,offsets,rot]); } in the link message (I've tested it, but simply by reading the card rather than in a build).

Try cleaning up your data before processing it, thus, and see if it helps: if(data != EOF){ data = llStringTrim(data,STRING_TRIM);//chop off leading and trailing spaces if(data!="" && llGetSubString(data,0,1)!="//"){//if there's still anything left and it's not a comment //process it }} It can't hurt, and at least it would rule out one cause.

default{ state_entry(){ llSay(0,"Wow, thanks Cerise!"); } } Yay! So easy. Thank you so much.

That's what I thought. When I raised the question in the SLU thread, it was because I was making something that uses llTextBox and was a bit nervous that some people might not be able to use it. Admittedly the device I was making also uses RLV, so that meant I only needed to worry about TPVs, but certainly we've had no complaints from people who can't use llTextBox, as yet.

I don't think there's any way with LSL to control viewer settings, though I'm open to correction. The only way I know in most cases for scripted objects to control your viewer settings -- as opposed to the behaviour of what's effectively an in-world object normally controlled from your viewer, like your camera -- is to use a specially compiled viewer (like RLV, which won't be any help here) with an API you can access with LSL functions such as llOwnerSay().

Depending on who's using the item, you might also consider using not llWhisper but either llOwnerSay(float_text) or llInstantMessage(id, float_text).

The only "God Mode" of which I've ever heard in SL is http://wiki.secondlife.com/wiki/God_Mode. No, your collar can't give you powers reserved for LL employees, if that's what you are asking!

Can anyone think of a TPV that doesn't support llTextBox()? Cool VL, Dolphin, Phoenix and Singularity all do, as far as I know, and I think Imprudence does, too. ETA We had a chat about this a while ago in another place, and no one could think of a viewer in reasonably common use that doesn't support it.

Sorry. I was misled by the reference to RLV -- all you can do with RLV is block IMs completely (though you can set exceptions, so some people can still IM you) and (I think, if you know which bit of xml to tweak) send a custom message. But blocked IMs are discarded, I'm afraid. So if you want somethng like Phoenix's autoresponder, I'm afraid RLV isn't going to offer any solutions. I'm wondering if Singularity or Imprudence have a feature similar to Phoenix's autoresponder and, if they do, if they would run on your machine.

The RLV part of it is easy. You don't need a relay to use RLV commands on yourself -- you just need an object or an attachment that belongs to you that can issue the appropriate llOwnerSay commands. Something like this, worn as a hud, will turn your IMs on and off for you, I think: integer toggle;//turns IMs on automatically when attached/detached or on_rezdefault{ attach(key id){ llOwnerSay("@clear"); toggle = FALSE; } on_rez(integer p){ llOwnerSay("@clear"); toggle = FALSE; } touch_end(integer n){ toggle = !toggle; if(toggle){ llOwnerSay("@recvim=n"); } else{ llOwnerSay("@recvim=y"); } }} However, the autoreply message people receive when they try to send you an IM is a very different kettle of fish, because that's sent by the viewer. I've got an idea you can edit the viewer's xml files to set your own autoreply -- I think I saw something in a blog once about how to do it -- but I could well be mistaken. All I can suggest is getting in touch with Marine or Kitty to ask for their advice about what -- if anything -- you need to alter to set your own default message.

Depends where your friend is based, but if she's in England or Wales she's guilty of fraud by false representation, contrary to the Fraud Act 2006. I would imagine most other places have similar legislation.

There's an invite-only (to ward off spammers) group in-world, For Sale By Owner, which is primarily for people who want to buy and sell full sims. I've always used that group, and have been quite content with the results.

Thanks. I had had a look in the forum but will search through the server release notes. I wish I could remember the details of what I was told; it was back in the old forums late last year, and I mentioned 4.0 as the maximum and someone -- I can't remember who, but it was certainly someone who usually knows what they're talking about when it comes to viewers and server releases -- corrected me, saying it had just recently changed.

Yes, I know a lot of people do. But I'm wondering if, in fact, there is now any difference between 3.0 and 4.0 or if it maxes out at 3.0. Dolphin 2 certainly won't let you set it higher than 3.0.