Void Singer

if the link message is coming from the named prim you get it for free in the first integer. ... if the named prim will be unique in the set, then it's easy enough to save all of the link names to a single list, in order, use list find list, and add one to the result. when the changed event fires with CHANGED_LINK you can clear the list and redo it. (*as Rolig demonstrated) if you need to target multiple prims of the same name, but only need to worry about a single name, you can do the same thing. if you have multiple names, with multiple targets each, my approach has been to record a name, count, and indexes... the count tells you both how many prims of that name, and how many entries before you get to the next set of names, although you can cheat and record the name, and insert any link numbers in front of it, when checking the list subtract 1 and check if it's a number, if it is, it's a link named to your target, repeat until you counter falls below zero, or you find a text list item. ETA: *Must learn to type faster

in addition to the other two suggestion, check an make sure that you did not recently wear a new item with an alpha layer (shoes are a big culprit).... if the alpha layer was blanked too close to a seam in can often blead over onto the left leg, cousing an annoying hole.... other alpha layer items may cause holes in different places...

good point... and I think most of the regular scripters are looking at it and going "meh can't trust it, why use it..."... ok maybe that's just me, but I do think that programming it to jump through the asynchonous hoops then add in a fallback is just a little much effort to say "hi xyz" when the person getting the message knows they are "abc" account name.... I guess I'm just agreeing an exmplifying that the user aren't the only lazy ones =X lol

thanks for the confirm on that, I only mentioned the ISP because another poster had mentioned that Orange may be filtering SL (although I didn't realize till I looked it up... Orange has fingers in the broadband pie over half the globe! so local policies may differ even if it were true in one area) personally I like linksys for routers that work with minimal fuss the best... netgear is an iffy second follow by d-link, and belkin seems like nothing but headaches in my exp... haven't seen too many zonet's so not sure about those or other less common comercial brands)

adendum to that: the newer functions to look up display names A) take up to 24hrs longer than the viewer to display B) don't consistently work for the the fast version C) the version that works consistently requires an asynchronous lookup, forcing a pause at best, or lots more code and processing and placeholder variables at worst (and can still fail) [D] all of the above

pretty nifty, I like.... one major limitation though.... it doesn't care if you are sitting on legit items or not... it will roust you from anything if youare in the sphere of influence (might make some local TP devices act twitchy too)

have you tired it from both the website and inworld (from a client that uses old style profiles) ? might let you get around it while you wait for your ticket to be solved (I'm assuming that live chat support just tells you to file a ticket)

might add a check to see if there are more than 8 items before calling the timer, and if not, just set the text. (might also want to remove the script itself from the list) I like it though... I did something similar for a leader board scroll.... 5 name at a time, dropping through the top 30

it's basically the same as an ankle lock animation... short ease-in, long ease-out, hands relaxed and looped, at priority 4, and ONLY the wrist joint keyframed. then play the animation from a script and replay it every few minutes (incase anothe p4 animation overtakes it)

You can assume it's Netgear's fault on the basis that either the particular model does something it's not supposed to, or their other models allow something they aren't supposed to (which would mean SL is also doing something it isn't supposed to, and makes them partially complicit). that's assuming it's just the router, and not something the ISP is doing inbetween. if a different router does not work, you might try contacting the ISP, and/or reviewing their policies to see if SL use is somehow limited. If it's not, and they are somehow blocking it, then you may be able to file a civil complaint of some type (I'm sorry, I don't know UK law well enough to say further)

what you can do is apologize, personally to all of those people you sent out a generic notice to... that should go a long way toward making your case as not being a spammer... and never ever do that again. for the record what you did was spam (albeit on a small scale). you sent a generic advertising message to multiple people, who never asked for it... never a good idea for a reputable business. in the future, if you are going to take the care to hand select people to send a message to, you can also take the care to personalize each message.... for instance, stating where you got their name from, or how you know them and why you are contacting them specifically.... then OFFER to extend them further information/services to them if they like it... this puts the ball in their court and lets them decide... you may even get a few referrals this way. and I for one disagree about the reporting frequency.... if i'm going to be bothered enough to tell you I'm reporting you, it's because I already did, or have the window open to do it. people that don't care enough to report usually just mute you.

they has been no public announcement of improved methods of access control or prevention of disposable accounts, nor even a mention of consideration for it. there are multiple open Jira's on the topic, and you may want to add comment to any that you think are workable, as well as selecting "watch" (and while it's still around, you can vote for it, though that may not have an impact) to be updated on the issue, and show your support. I personally suggest the one the mentions applying the hardware ID (which LL has acces to) to parcel bans on the server side. This would be the most significant improvement to slowing down the worst of the disposable accounts, and stopping some of the less persistent ones cold.

No, in fact all keys are accessible via various methods, and just as good as names Donation Linden: 2a49a617-49c1-4f6a-902d-4adb79a8da08 American Red Cross (which is who Donation Linden is giving to) would be more direct, but they do not have an official presence in SL, so if you want to target them directly, I'd link to their website. alternatively, you could link to the SLMarketplace listing for Donation Linden, which has bears for sale, as a donation gift for the relief fund.

psst Dante, unless you are talking about just the account name (which display names break) then most people coming from other platforms and games would consider the ability to completely change your appearance at whim as having multiple avatars on the same account. might be worth pointing out;)

you can export items you are the creotor of AND have full permissions on. if you are not the creator of the images used they will default to the plywood textures. the problem being, the format that the exporter spits out is simply an XML list of the object properties as found in SL.... currently there are no good export methods that will get you a file of the type you would want or could use for a 3D printer. on the horizon, a few months off (we hope) is the ability to import .obj meshes... and one assumes, export them as well, but that still leaves creation outside of secondlife. in the meantime the only likely candidate (that I am aware of) for taking an SL object an exporting it in a useful fashion, is to use an inworld nurbs recorder... to place the nurbs surface, and import the data that it spits out to a program that supports nurbs surfaces.

instead of focusing on the long goal, set your sights closer to the path your are on... walk yourself step by step through the things that need to happen... to rez an object, make it move in relation to a space, etc etc then tackle learning those by examining scripts that also take those those small actions.... once you have all the small actions understood, you'll find writing the rest is just a matter of gluing the pieces together.

Two situations A) Ridiculous lag makes the script slow enough that it can't respond fast enough to catch multiple sitters at once (unlikely, but possible) B) The script is incorporated into a larger script, and another event or processing causes the delay of the changed event and more than on person sits (a very real possibility) the only real trickery is the line that gets the prim count.. llGetNumberOfPrims returns a count including avatars (which can't be present if it's an attachment), llGetObjectPrimCount give accurate counts, ignoring avatars, but is bugged on attachments to return 0. So to get accurate prim count regardless you have to use both. llGetAttached NOT'ed twice gives a true/false value to multiply by (letting you cancel the one you don't need)... The reasoning behind doing it is so that the changed event doesn't get triggered in an infinite loop (since we're comparing prim to avatar counts) if for some reason the object is also attached latter. the reused variable is technically not good practice, since code that comes after may expect it's original contents, but it does save creating a new variable. the bitwise operation of (-~) is equal to adding 1 to the value, in this case one link number past the end of prim linkset, which is the first seated avatars linknumber...

Dale Innis wrote: Kaiser's idea is, I believe, that different people's browsers would render different sets of prims in the same area. That way I can have 10,000 prims in my skybox that's just above your head, but since your viewer doesn't render them you will see just open sky and not suffer any lag from having to render my prims. And vice-versa, looking down from my skybox I will not see any of your prims down on the ground. what has been failed to be mentioned is that all this extra is hosted on the OP's servers, with exclusive right to sale built on by the OP, and doesn't address permissions on exporting items (see OP's complaint about that back here) which would have been a death knell for TPV inclusion even if OP had complied with the rest like available source (it aint) and privacy policies (non existent), etc ad nauseam. OP has a novel idea that could be a useful add-on feature, but low ethical standards, and this ridiculous stealth marketing campaign (like the recent absurd shill post where op forgot to log into a different account with exactly the same ad copy, that is now deleted, where I called OP out as liar.), the lack of any type of offical business contact information, etc etc... I wouldn't touch it with a ten foot pole. I recommend the same to everyone else. wait for somone that will do the idea legit.

default{ changed( integer vBitChg ){ if (CHANGED_LINK & vBitChg ){ vBitChg = llGetNumberOfPrims() * !!llGetAttached() + llGetObjectPrimCount( llGetKey() ); while (llGetNumberOfPrims() > vBitChg){ //-- you could insert animations or other player abuse here, reposition them, etc llUnSit( llGetLinkKey( -~vBitChg ) ); } } }} this will catch all avatars on the object, and requires no sit target... (if you only target the one on the sit target, you miss the ones that might not be on it)

I would suggest waiting until 2 business days to file a ticket with LL... not everyone is available to work over the weekends and the may not respond during that time.

needs linking to localized language versions, for example French --> Menu_Préférences

Salut, s'il vous plaît vérifier Préférences -> Réseau -> Bande Passante Maximale: 1000 à 1500 Préférences - Graphiques -> Qualité et Performance: Ultra Préférences -> Graphiques -> Configuration du matériel -> Activer le VBO: Oui Préférences -> Graphiques -> Configuration du matériel -> Mémoire vidéo: 512 écran plasma est bon pour jouer a Second Life.

more than welcome... I figured I'd cover the technical and political reasons for and against since no one had... I try to be fair, even though I personally despise v2 for many specific reasons, but I won't that block out what good features are there... everything has it's limitations and perks and while i like the Phoenix radar, it's too big IMO and I like the thinner one in Cool... I need to go in and tweak the layout file for that on my machine....

it IS possible on V2, just not implemented... however, that double click to look at someone in Phoenix, is also built on top of the LSL bridge... meaning that it uses script to do it's magic... mostly because the servers do not correctly report height to the viewer minimap above a certain level (1024m), but a script can request the exact position of an avatar. why doesn't LL put that in there? probably because: A) there is a perception of snooping B) it requires the addition of a scripted object for full functionality C) they don't think it's valuable enough to include other features that have been in high demand from users and included in TPV's have been added to V2, such as radar (used to be there was none at all), multiple attachments (although it's arguable that the V2 code is still limited compared to the old xml hack), doubleclick to teleport, shadows, and even external script editor ability.... all adopted from various TPV's. TPV's have an advantage in featuresets though, because they can implemet features that LL might feel are too complex, or are not in line with what they want to present, and the TPV's can cater to specific requests that LL might not feel there is a large enough demand for.

Ordinals is the simplest method, although potentially the least accurate depending on accumulated time dilation for the day. the other two are more accurate in the frequency they report at (with an average deviance of half the timer cycle) but mean that all boards are going to report in at about the same time. both Roligs and Ordinal's methods will be delayed by script down time (region offline, script set to to not running or taken back to inventory), that delay amount will set the new standard. Mad's will only be pushed to the next check after the delay, and then resume it's normal reporting time. Mad's does require a variable to save and check for the change using a random number from 1 to 86400 generated at start up, and added to llGetUnixTime, and checking that in the timer versus a day change, would break up the reporting for all devices, as Ordinal's does, but still allow them to report at roughly the same time of day as Rolig's and Mad's do, and resumes normal reporting time after a delay as mad's does. it does require a global variable as Mad's does code for generation would be something like gIntNxt = llGetUnixTime() + (integer)llFrand( 86400.0 ); or if you like Ordinal's offset based on rez time... gIntNxt = llGetUixTime() + gIntNxt = llGetUnixTime() % 86400; and the check code would be if (llGetUnixTime() > gIntNxt){ while (llGetUnixTime() > gIntNxt += 86400); //-- could be written as gIntNxt = llGetUnixTime / 86400 + gIntNxt % 86400; //-- phone home } this is obviously the most complex code of all the options, which is the price you pay for incorporating all the features of the others.... the whole point being what limitations and benefits each method offers, depending on what your needs are... honestly fo most things I'd go with Ordinal's suggestion PS you can get an extra timer for the current state only (gets wiped on state change) by using the no_sensor event, and llSensorRepeat( "Null", llGetKey(), AGENT, 0.01, PI, timer_length );