Innula Zenovka

Ah. That's the normal edit view; the child prims are highlighted in blue and the root prim in yellow. In V3, the highlighting vanishes when you touch the arrows to move the skirt around, so that's not an issue. I can't remember what it's supposed to do in Phoenix but I think there's a setting somewhere in Phoenix preferences to control the thickness of the highlight. Someone who uses Phoenix would be able to tell you.

In answer to your question, to dial the USA from anywhere abroad, you need to enter 001 and then the US city code (415 for San Francisco) and then the local number. However, the course of action LL recommend -- and, I would think, require -- in such cases is that you submit a support ticket, as described here. So that's what I would do in your situation.

Make sure that "Select only my objects" is *not* checked (under Build>Options).

Congratulations, JolieElle. To be specific, you are now eligible to upload mesh models to SL. To do this, you need to be using a recent version of the official viewer (I'm told you can do it with Firestorm, too, but that the results are sometimes not particularly satisfactory), to have model to import, of course, and to follow the instructions here: Uploading A Mesh Model

JeanneAnne wrote: Yeah! "Common thieves" like Robin Hood: "One hacker said the goal was to pilfer funds from individuals' accounts to give away as Christmas donations..." Well, that's not too bright a way of doing it, to my mind. As the article explains, the breach doesn't necessarily pose a risk to owners of the credit cards. A card user who suspects fraudulent activity on his or her card can contact the credit card company to dispute the charge. So all they're actually doing is causing a deal of inconvience and expense not only to the card users and the credit card companies, but also to the recipients of these donations. The credit card companies can, if they want, recoup the administration costs through their overall charges, but the charities are being put to unnecessary work in sorting out the mess for no good purpose other than to give these people some lulz.

As I mentioned when we spoke in world, that sounds to me as if you are somehow going into wireframe view -- I have no idea how that can be happening -- it should look more like this If that's what's happening, you should be able to restore the view to something like the second picture by using CTRL+SHIFT+R (assuming you're using Windows -- not sure what the equivalent Mac shortcut is). But I am baffled as to how you're going into wireframe by accident. You mentioned you're using Phoenix -- maybe their help group could suggest what's going on (there may be an option in Phoenix to go into wireframe when editing -- which can be useful at times -- that you've turned on by accident)

Agreed about counting backwards. That's always far easier and more efficient when you're deleting stuff. I think the issue with an automated takedown by LL is that -- at least going by previous attempts to do them -- there's a very serious risk of removing the animations from sexgen products people bought before Stroker distributed the animations full perms, and (at least in the case of Craig Altman's animations) from legitimate products that are nothing to do with sexgen.

Mayalily wrote: I didn't know they upgraded V1 to mesh until I read this. Why on Earth did LL put us through all that waste of time with the V2 and V3 viewers when they just could have upgraded? How many "bugs" on the mesh V1 viewer? LL haven't upgraded their viewer. Henri Beauchamp and Siana Gearz backported mesh code into their viewers, Cool VL and Singularity respectively, quite some time ago, and Phoenix have recently adopted Henri's code. I don't think any of them, as yet, allow you to upload mesh, since that relies on proprietary code, and none of them, as yet, allow you to wear multiple clothing layers, which could make wearing mesh while using one of these viewers rather difficult (since mesh frequently requires you to wear an alpha layer, too, as frequently do shoes, too, and you won't be able to wear both while using one of these viewers -- though Henri is working on that, apparently). Other than that, there's no major issues with viewing mesh using any of these viewers that I know of. I don't know about viewer-specific bugs, but there's nothing major, as far as I know, in Cool VL. If you want to continue using a Snowglobe-based viewer (V1) and to see mesh, there's nothing to stop you, IOW.

Hi, Sue. Welcome to SL. I'm not sure what you mean by "negative type mode". The edges of the skirt should glow when it's selected, but that doesn't sound like "negative type mode" to me, so I'm wondering if it's something else. In general, I'd recommend finding a pose stand from somewhere (many merchants give them away free with purchases, and I know the Adult Hub has free ones, but if you get stuck, IM me in world and I'll send you one). They normally put you into a dead straight position with your arms stretched out, which makes aligning stuff easier. There's a couple of video tutorials about editing attachments on YouTube. There's a very and a far Because they were made some time ago, the user interface is rather different (assuming you're using a recent viewer) but the main editing tools are unchanged, and they might be some help.

I don't know about showcasing. All I'm saying, I guess, is that there must be plenty more people than me who are interested to see what's available in mesh, either because we've heard so much about it or because we've seen some and formed the view (at least I have) that there's certain things that mesh is very good for. Certainly, the next time I want some jeans, I'm going to get mesh ones, and if I can find a short skirt or dress I like in mesh, I'll get it. Also, I've seen enough mesh dresses to know that, if I can find something in a style I like, it will be worth having. It's just that the styles I've seen, by and large, while very nice, just aren't what I normally like to wear. At the moment, if I don't find out about it from a store update group, I'm having to make a conscious effort to look for stuff, at SLU or in blogs. And it would be nice for me, and I would think for a lot of other people too, particular Phoenix users who can now at last see mesh, to be able to look in the Marketplace and readily find out what's available. It's something new, and there's increasing interest in it, and I'd like help finding it, is all.

I don't see any necessary connection between the number of people who can see mesh and whether or not it's a good idea to make mesh goods easier to find in the marketplace. While we can debate about number who can see mesh, the fact of the matter is that a not-inconsiderable number of people certainly can, that there are plenty of viewers that now support it, and mesh could certainly be made easier to find. The fact of the matter is that -- as someone who is quite interested in seeing what's available in mesh -- I find it considerably easier to use SLU's new products section, where I can easily filter for mesh (and not get hundreds of listings for stockings) than do I find it to use the search tools available in the marketplace. And this seems to me unfortunate.

Cat Slade wrote: And to above posters - there are plenty of viewers that don't 'see' mesh yet. LL's 1.23 doesn't see mesh, and neither does Imprudence (I think) nor old versions of Phoenix. Which other ones don't?

Tari Landar wrote: Showcasing mesh when the majority of your customers(and even more of your potential customers) cannot even see or make use of it, would not only be a waste of time, but also just give more cause for people to wonder what exactly the powers that be are doing up(down?) there. I'm not sure your figures are right there. According to Charlar Linden, on the 19th, "it looks like 55% of users logging in are running mesh capable viewers.." It's not quite clear when those figures were collated, but since Phoenix had released their mesh capable viewer only a week before, the figure must be higher now than then it was.

You don't need a poseball. You can achieve exactly the same effect, and save a prim and have a better looking vehicle, by putting the animation in the root prim of the bike, adjusting the rider's position using llSitTarget(), and letting the main bike script handle animating the rider. That's a more sensible way all round, to my mind, since the main bike script has got to plenty of stuff anyway when the rider sits down or gets off -- it might as well handle the animations at the same time. That's the way vehicle scripts normally work. And my strong suspicion is that if and when you get round to putting a vehicle script in your motorbike, that's going to fight with the poseball. There's a very good, very old, script buried in the old Scripting Library by Cory Linden, which is a heavily commented example of how to make a basic motorbike script. It's what started to learn about vehicles from. I'll drop you a copy in world.

I think the idea is that, since there's clearly doubt about whether Stroker was within his rights to distribute any of the animations, other than the ones he made, full perms, prudent content creators -- and particularly those who remember the Eva Capalini debacle (which I do, all too well) -- might not want to run the risk of the aggrieved animators filing DMCA take-down notices at some point in the future and LL then deleting the animations from items in customers' inventories. ETA -- @arabellajones -- if you check the link in the wiki that appears in the script, http://wiki.secondlife.com/wiki/Stroker_Serpentine_Sexgen_Animation_Set, you'll find the views of one of the animators, Corsi Mousehold, on the subject. Another animator affected, Craig Altman, made his objections to his animations being thus distributed very clear over at SLU. The script also includes a link to a google spreadsheet I made that lists who made what animation: http://tinyurl.com/5wk3mr2

Assuming it's a simple box, try pathcut start=0.125, end=0.625 and adjust the size accordingly.

I think I've seen that error before, and I'd assumed -- I can't remember why -- that it meant the Marketplace had not been able to get a response from the vendor's "Magic Box" that sends out the goods in world. This may have meant there was something wrong with the box, or just that the sim where the box lived was offline at the time. I'm pretty sure I got an automatic refund, though.

Animations are all rendered client-side, I thought. What we should be hoping for, to my mind, is that LL adopt these improvements as part of the standard viewer.

Unless you use a hud that actually rezzes poseballs, like the "Sex Anywhere" huds (anywhere, that is, that lets you rez stuff), then I'm afraid not. This isn't because of a lack of ingenuity on the part of scripters; it's because of the constraints of LSL. I don't want to get too technical, but, essentially, you can't rotate avatars unless they're sitting on something or unless they're using RLV (and even if they're using RLV, you can't rotate them any where near accurately enough to line them up for a kiss), and, anyway, scripts in attachments can't measure the rotation of the avatar who's wearing them particularly accurately unless the avatar is in mouselook at the time. What happens when someone accepts your offer of a kiss is (normally) that one script in your hud holds the object of your affections in place while another script calculates the distance between you and then moves you that distance, give or take, towards your target. What it can't do is turn you round so you're facing in the right direction before you start, or calculate with sufficient accuracy the angle at which you should be moving to end up face-to-face. This is an area of scripting I know pretty well, and if you wanted me to move a prim so it ended up nicely aligned with another prim, I could do it for you. But I just can't do that with avatars, I'm afraid. LSL won't let me. ETA The only work-round (sort of) for this is to use something like this Micromover Hud in conjunction with a hug/kiss device, so you can adjust your position (though not your rotation) in small units when you reach the person you want to kiss, sliding yourself slightly to the right or left.

I suspect it's to do with Google turning off their free Translation API, which a lot of translator huds depended on, as did the built-in translators in newer viewers. If you update to anything based on V3 (including, I think, Firestorm), you should be able to use Bing's translation service (see Inara Pey's instructions on how to set it up) or, if you want to use a hud-based service, the IOL Q-Translator still works very well (others may do, too, of course, but I mention that one because I use it, and it was working well yesterday).

Assuming these are linked prims, llSetPos() tells them how to move relative to the root, while llGetPos() returns the region coordinates of the prim. For the prim's position relative to the root, you need llGetLocalPos(). But I think you might find this a lot easier if you try using llSetLinkPrimitiveParamsFast and PRIM_POS_LOCAL and PRIM_ROT_LOCAL.

Storm Clarence wrote: SLum is totally borked. I have new followers PM'ing telling me they miss my 'pearls'. I am sure your "jewels" are sadly missed by many, Storm.

I can't remember where it is in Phoenix -- not used that viewer for ages -- but I'm pretty sure there's a setting in Edit-Preferences to disable previewing textures before accepting them into your inventory. If you can't find it, simply setting ShowNewInventory to FALSE in debug settings should do the trick, I think.

I just right-clicked on the desktop shortcut and opened the properties window, and copied the Target, "C:\Program Files (x86)\Vim\vim73\gvim.exe" (including quote marks).

I was concerned about this for a while, but when Firestorm adopted mesh, I started wearing the few mesh clothes I've liked enough to buy, and very few people have complained about them looking strange. The one time someone has, it turned out he -- a Phoenix user -- was the one person in the group of half a dozen of us who couldn't see them properly, and that was before Phoenix became mesh-capable. My advice is not to worry. I find this particularly ironic, in fact, when I remember how upset some Emerald, and later Phoenix, users became if they were wearing stuff on one of the "illegal" extra attachment points and someone complained their belt was floating round a metre or so away from them.