Innula Zenovka

I use the Blue Goo style, made by Cerise, and available from userstyles.org, and this is what I see:

One of the things people who make RLV stuff have to watch out for is that attachments rez, and are able to ask the wearer's viewer -- via llOwnerSay -- if RLV is turned on well before the viewer is able to reply, so you've got to allow 30 seconds or so to stand any chance of getting an answer. Are there any circumstances in which the regular viewer can talk direct to attachments? I don't know if there are or not, but if it can, you might be able to use that. The other thing, off the top of my head, that might be worth exploring is that, according to the wiki, llGetAgentSize returns 1.9 exactly as the z component if the avatar's not fully loaded, and it notes that it's going to be so rare for an avatar to be precisely that size normally that, if this is what it returns, the avatar is probably ruthed. So maybe if you check llGetAgentSize(llGetOwner()) in the on_rez event?

Ah.. this, from DanielRavenNest at SLU, may cast some light on the problem: There appears to be an issue with newer Nvidia drivers which have deprecated some old openGL features. I was getting some crash-on-startup problems too, and have rolled back to 260.99 to see if that helps. LL is aware of the problem (ie they used some old open GL code) and is working on updating those parts.

You don't need a script in every prim for particle emitters any more. We've now got llLinkParticleSystem.

I don't think Emergence is maintained any more, so teleport failures wouldn't surpise me. Why not try another viewer -- if you really don't want a V2-based viewer, I would recommend Singularity or Rainbow (which has come out of hibernation), which both look and feel very much like Emergence. So does Phoenix, of course, but I find that viewer considerably slower and more buggy than the other two.

Baloo Uriza wrote: Maddy Gynoid wrote: But I ask myself, if the issues with the newer NVidia drivers are related to wrong viewer code, or are based on bad driver software? Or is it a combination of both? Why hold Windows without blame, since this problem doesn't exhibit itself on Linux? I'm willing to eliminate the viewer from fault here given the codebase is the same either way, which leaves Windows itself and the Windows driver for nVidia as likely suspects. I most certainly hold Windows responsible for this. Quite simply, as far as I can make out, the drivers Windows 7 helpfully installs for my card, a GeForce GTX 460/PCI/SSE2, either aren't always identical to those available on the Nvidia site or something goes wrong in the installation process. Certainly, I repeatedly had this problem each time Windows performed an automatic update and was always able to resolve it by uninstalling the driver and installing a new one, downloaded direct from Nvidia. And I have not experienced it since I (belatedly) put two and two together, turned off automatic updates for Windows 7, and signed up to obtain notifications from Nvidia of their recommended updates.

I've just taken a look at the scripts, which I found at http://www.free-lsl-scripts.com/freescripts.plx?ID=1601 According to the comments in the code, it's trying to stop people resetting the script to revive the pet after something's gone wrong and it's moved into state dead. So I guess it's another way of doing, in state default, something like state_entry() { if(!~llListFindList([llGetCreator(),llGetInventoryCreator(llGetScriptName())],[llGetOwner()])){ state dead; } else{ //do stuff to initialise script } } I've only taken just a quick look at them, but it seems to me that none of them need anything changing other the first few lines, where you set passwords and channels and stuff. Whether they do actually work out of the box, I don't know, but they seem to be written so to do.

Gimp: http://www.gimpusers.com/tutorials/glowing-text

You know best, but I really suspect 100 scripts sending link messages round may be overkill. One script in the root can detect which part of a particular face on a particular prim you've touched, and figure out from that what button you've clicked, and then, knowing that, it can tell any particular prim in the linkset to do pretty much anything, using llSetLinkPrimitiveParamsFast. As to the second question, knowing which link number is which, I would use link names (or descriptions) to read the names of the prims and thus assign their link number to a particular variable. Then I would stop worrying about what the actual numbers were. To give a trivial example, if you do something like this, you can forget about which link number any particular button is -- so long as it has "red" or "green" or "blue" as its description, so long as you haven't changed the description since the last time you relinked it, the script should know what to do. integer red_button;integer green_button;integer blue_button;find_prims(){ integer max = llGetNumberOfPrims()+1; while(max--){ string s = llToLower(llStringTrim((string)llGetLinkPrimitiveParams(max,[PRIM_DESC]),STRING_TRIM)); if ("red"==s){ red_button = max; } else if ("green"==s){ green_button=max; } else if ("blue"==s){ blue_button=max; } }}vector colour;default{ state_entry() { find_prims(); } on_rez(integer start_param) { find_prims(); } changed(integer change) { if(change & CHANGED_LINK){ find_prims(); } } touch_start(integer total_number) { integer n = llDetectedLinkNumber(0); if(n==red_button){ colour = <1.0,0.0,0.0>; } else if (n==green_button){ colour = <0.0, 1.0, 0.0>; } else if (n==blue_button){ colour = <0.0, 0.0, 1.0>; } llSetLinkColor(LINK_SET,colour,ALL_SIDES); }}

Deej Kasshiki wrote: Canoro Philipp wrote: the UI of V2 is just fine, i can do everything with it, i walk, i teleport, i chat in IM, i create prims and texture them, listen to music, open my inventory... all the functions are there. the only problem is the user, who is not used to. we will be in viewer 5 and some users will still use V1, its ok, if some people still want to use windows 3.1, is their choice. Swell. Great for you. Oh btw, a well-designed and thought out UI shouldn't completely break from what came before and force the user with years of experience and muscle memory to radically change their workflow and lose productivity in order to adapt to it. It should be the other way around. In what sense, unless you're making clothes, does the UI radically change your workflow other than when you're setting a lot of different permissions? I spend most of my time in SL scripting (primarily) and building, and didn't find things had changed a great deal when I switched to V2. I agree they missed an opportunity to adopt some of the enhanced building tools from the TPVs, which I am told is primarily an issue with various open source licences, but I don't think things changed much from the official viewer, did they? Admittedly I've used the Starlight skins for most of the time I've been using V2, so maybe things are different in the unchanged version -- can't recall. But my overall impression was that, while things took a bit of getting used to, I found myself on reassuringly familiar territory with scripting and building.

I think it's a message from Phoenix, not from LL -- I have just tried logging in with both Cool VL and with Catznip, neither of which are in the TPV list (though perfectly "legal") and did not receive any such message. I wouldn't worry about it.

They are apparently working on it -- the problem seems to be getting bi-directional text rendering to work properly in the viewer so that both left-to-right and right-to-left scripts work properly in the viewer. See Merov Linden's comment in the jira.

What happens when you try? Do you get an error message of any sort, and, if so, what does it say? Or does the viewer just crash?

According to Rodvik, who sometimes posts over at SLU, "Next up will be a focus on bugs, usability in the main viewer and (hopefully) some large GUI changes later in the year."

Baloo Uriza wrote: That said, I tend to prefer Imprudence and OMVViewer, though I've heard good things about Hippo, Ascent and Kirsten's. I would take a close look at those five before considering Phoenix. Ascent isn't maintained, as far as I know. However, Singularity is based on it, and is an excellent viewer -- it looks and feels very like Phoenix but is far faster and less buggy, at least on my machine. It's frequently updated, and should have mesh pretty soon.

Over at SLU, Cristiano strongly recommends advertisers link their ads to the Marketplace rather than to SLURL on the grounds that SLU's largest traffic is during business hours in the US (which says something about work ethic in the US, I suppose). Many people who click on your ad cannot sign in to SL, thus they are unable to see anything about your products. That is a potentially lost sale or visit to your store or business. Better alternatives are to link to a blog/website or your SL marketplace store. Hell, even linking to your posts in the New Product Listings forum is better than a SLURL. I would like the advertisers here to get the most out of their advertising, which is why I always advise against SLURLs. I don't know, obviously, but I suspect browsing habits are similar with these forums.

Broken link, I think, Darkie -- that goes to a site about a conference in London.

LL don't look at these forums -- this is just ordinary residents trying to help each other. What happens when you try to log in with your new accounts? Do you get an error message or does the application just crash or what? ETA -- since you say you've tried resetting your modem and that doesn't work, that suggests to me you've got a fixed IP address. In which case, I guess the simplest solution to ask your ISP to reset it for you. Other possible measures are discussed here.

You don't need to know anything about scripting to use the MLPV scripts -- it's just a matter of entering stuff on notecards. Take a look at https://wiki.secondlife.com/wiki/MLPV2_Tutorial for full instructions.

Void Singer wrote: correction, multiples of the SAME layer.... which is only really useful for lots of tattoos that haven't been sold with alternate layers. Sorry, Void, but I have to disagree with you there. I find being able to use multiples of the same layer really useful when putting outfits together. I like wearing long blouses and shirts, and these never look quite right when made up from a shirt and a pants layer -- they always work better as jackets. But so do jackets, of course. One of my main reasons for switching to V2 was that at last I could wear long shirts and the like with my biker jackets and greatcoats. It's really extended my wardrobe. The second reason I like multiples is that I can now buy one base skin, and then mix and match cosmetics, using a tattoo layer for lipstick, another one for eyeshadow, another for for blusher and so on, rather than have to buy -- at considerably greater expense -- several skins identical save for the make up.

And there's llGetAnimation(), too, if it's necessary to distinguish between walking, crouch walking and running.

What collar is it, and what viewer are you using? As valerie suggests, it certainly sounds like an RLV issue, but to recommend a fix -- assuming that you want to be able to wear the collar when you feel like it, but not all the time -- requires a bit more information.

When some friends of mine had a disagreement with the owner and found themselves locked out of a private sim of which they'd been renting half and unable to pick up their buildings and other property, they asked Live Help for assistance, and LL re-opened the sim to them for a couple of hours, by arrangement, to allow them to pick up their stuff. If you are a premium member, it can't hurt to contact Live Help and ask for their advice and assistance. That might be a better way to proceed than an AR.

You might be interested in this, somewhat similar, proposal https://jira.secondlife.com/browse/VWR-11679

Sounds like a badly-scripted security orb to me. I would just mute (block) the damn thing and forget about it.