Rolig Loon

thesandboss wrote: Thanks guys. I checked on the computers in the computer lab and sure enough their graphics was set to low. From what I'm gathering from the rest of the conversation is that the objects actually have the glow. I'm guessing I'm going to have to go in and change each specific objects properties so they don't do that. This sounds like a fun point and click project. That happens. People who work on computers with a low graphics setting overdo glow because they can't see it. It's like deaf people shouting because they can't hear themselves. Unless you really want the radioactive effect, you should never set glow higher than about 0.1.

George Orellana wrote: It might be what she wants and it might not. If she is building something for a university I am assuming she wants to see what most people will see while building. I remember when I was a newbie and I built my first thing in SL I was happy about my first made thing, it all went crashing down when a friend told me she couldn't see anything all she saw was a very bright glowing object, that is the day I learned there were other graphics settings, lol. Yeah, that's true. In a great many cases, though, the truly annoying glow happens when some bozo has turned on glow at maximum strength and it cuts through any object that has a 32-bit texture on it. As you walk around, opaque textures block the glow. When there's an alpha-textured object between you and the glow, however, the ghastly radioactive aura hits you in the face again. It looks random, but it's really just a matter of which textures are in your line of sight. If that's the issue, the only way to beat it is to kill the glow as I recommended.

Go to your Advanced (CTRL+Alt+D) menu and choose Debug Settings. From the pulldown menu, select RenderGlow and set it to FALSE. That will turn off all glow anywhere. It will only affect what you see in your own viewer, but that's what you want.

Take a look at THIS JIRA REPORT. If the images there look like what you are seeing, it's a driver issue with your ATI graphics card. Download the latest Catalyst driver (11.2) and it should clear up.

Cloey Langer wrote: i must maby explaine more the grey area will be a open hole so i see throw it Either one of Dilbert's suggestions will do that. If you create a texture with an alpha channel, there won't be a physical hole, but the piece will have a transparent spot that looks like a hole, which is just fine. It's the same thing as making a wall texture with an alpha window in it. If you really want a hole, though, make a sculpty that starts with a torus stitching type. It should be easy to flatten and stretch a simple torus to the shape you want.

Geez, you guys have been busy while I was sleeping. :smileytongue: Sion, as you've discovered, there's nothing magical about standing that makes a pose stand work. You can trigger the poses any way you like. Darkie's got it working here. If you want to add dialogs, one of the best tutorials to get you up to speed is THIS ONE. I also recommend learning how to fly Void's Multipage Dialog system, which makes it easy to daisy chain one dialog into another and keep the buttons organized. @Darkie ... The line that says llSetObjectName("") is there to suppress the object's name in chat. You'll see that wherever there's a llSay it starts with /me to complete the process.

It's also possible that you are buying boxed items and have been wearing the boxes instead of unpacking them. Find a nice sandbox or somewhere else where you are allowed to rez objects, drag your purchase from inventory to the ground, right click on it, and select OPEN. When you do that, the object's contents will be transferred or copied to folders in your inventory, ready to wear. Remember to take or delete the box when you are finished, instead of leaving it around. Oh .... To find a sandbox, use your Search function (upper right corner of the screen if you are using the V2 viewer) to look for the keyword "Sandbox". You'll find loads of them.

It sounds as if something you did with the Debug Settings has screwed up your client, but I don't have a clue what it was. If it were my own machine, I'd be inclined to save the trouble of finding out by cleaning things out and reinstalling SL from scratch.

I hate it when that happens. Usually it's when there's something else running on my computer, competing for the hard drive or for bandwidth. It will happen sometimes if Microsoft or my Anti-Virus routine starts downloading an upgrade, or when some program starts a scheduled scan. Sometimes, though, it happens for no discernible reason. Like most of the problems that people have with SL, it happens because something in or close to your own computer is competing for SL's attention, and SL is a real attention hog.

I was caged once about 3 years ago, but by a very dumb cager. I TP'd out, came back around the corner a few seconds later and scared the wits out of him. Other than that, I've seen a few lame self-replicator griefings but nothing to write home about. The bad guys aren't in my neighborhood, I guess.

It's a fairly simple matter to write a script that will look for any SL resident and tell you whether s/he is in world, so there's really no foolproof way to hide. You can uncheck the "LookAtMe" box next to anyone in your friends list, so that they can easily see when you have logged in, and of course nobody can tell where you are, even if they do know that you're in SL at the moment. That's usually enough to keep all but your most persistent friends away. The only other solution is to create an alt and don't tell anyone her name.

I'm afraid it's gone forever. Even before they were ejected, the only way for you to get the full list of names would have been to copy them out laboriously by hand. You can't cut and paste from the group member list, and there's no way to export it. On the positive side, that makes it really hard for some spammer to grab the list. On the negative side.... well, you've seen the negative side. :smileysad: Looking ahead .....There are ways to build a list of group members by having them enroll by clicking on a prim that is specially scripted for that purpose. You could dump that list to chat and copy/paste it onto a notecard. Then you'd have it for the next time disaster strikes, or for whatever other purpose you might want it. Take a look at THIS THREAD in the Scripting Forum, for example.

At the risk of giving too much information, I'm going to cut and paste a lovely, complete answer that was posted by the vastly knowledgeable Irene Muni a while ago: :smileyhappy: - 1 - If you want acces to Adult lands an content IS NOT necessary be Age Verfied, it's enough be Account Verified. See http://wiki.secondlife.com/wiki/Linden_Lab_Official:What_are_the_different_types_of_Account_Verifica... That document explain the differences. Extract: In order to access Adult Content in Second Life, your account needs to be verified. You may have heard the terms "Account Verification" and "Age Verification". While related, they are in fact different! Here's what you must know: Account Verification is an umbrella term which contains different ways of being Account-Verified. Having "Payment Info on File" means you're "Account-Verified" , but not necessarily "Age-Verified". You can be neither, either, or both. For example, if you purchase goods from Xstreet with a credit card, you have Payment Info on File status, and are "Account-Verified". But, you're not Age-Verified unless you explicitly go through the Age Verification process. Furthermore, even if you have both Payment Info on File and are Age-Verified, to access a Region, your Preferred Maturity must be the same or greater than that Region. For example, to access an Adult-rated Region, you need to set your Preferred Maturity rating to PG, Mature and Adult. Similarly, to access a Mature-rated Region, you need to set your Preferred Maturity to PG and Mature or PG, Mature and Adult. -2 - But if really you need be Age Verified, and you have problems doing ir automatically, you shoul use the Manual age verification. See http://wiki.secondlife.com/wiki/Linden_Lab_Official:Age_Verification_FAQ#What_happens_if_I_experienc... What happens if I experience problems when I try to verify my identity?The new age verification feature is in beta. Please be patient as we continue to improve the feature. We are committed to making sure the process is as smooth and user-friendly as possible; however, we understand that this represents a change for Residents. We have also tested the system extensively with our systems provider, Aristotle-Integrity, which has delivered this type of technology to other companies. If you continue to have problems verifying your identity, please go to the Second Life Support Portal and submit a ticket (select Special Questions - Basic account or Guest Login from the Ticket Type dropdown, select Account Issues from the next dropdown, and choose Manual Age Verification from the next). Please attach an electronic (scanned) copy of one of a Government issued identification that has your name and date of birth clearly displayed. This identification could be one of the following: Birth Certificate Driver's License Passport State or National ID To attach a file to your ticket: Log into the Second Life Support Portal and click the My Support History tab. Click the Ticket # of the age verification ticket you submitted. Click the Comment button. Click the Attach a file link. Browse for the file on your computer and click Open. To attach another file, click the Attach another file link. Click the Submit button. The files you specified will be uploaded and attached to the ticket. Please expect manual verification to take 5-7 working days.

What? You aren't going to offer a plywood box too?

You may find a friend who is willing to let you rez a booth or vendor panel in her/his shop, but in general it's a bad idea to try and do it on land that that you don't own or rent. For one thing, rezzed prims count against the land owner's prim allowance, and for another, you are making a profit without paying appropriate rent. If you are lucky, you will just have your booth returned. If not, you'll find yourself banned and AR'd.

There is no "group account," except as a transient bookkeeping entity. Any money that is credited to a group is immediately split evenly among group members, provided that their roles allow them to share assets. It's been my experience that "immediately" means "within a few minutes, at most." If a transfer appears to take longer than that, I'd guess it's because some other step in the process is slow. For example, group liabilities and dividends are figured on a weekly basis.

When that happens it's usually because you have included a script, a texture, a sound, or some other component that is non-transferable.

I haven't bothered to read any of his posts in the new forums. Now that the moderators dispose of them quickly, they aren't even much of a nuisance any more. It's sort of pitiful, really, that he hasn't figured out that nobody cares about his delusional ramblings.

The parameters you have written should give you the result you wanted. You might set CAMERA_BEHINDNESS_LAG to 0.0 so that there's absolutely no delay in response as you move. Other than that, the only thing I can suggest is that the parameter list really should be in a run_time_permissions event instead of your touch_start event.. That is ... run_time_permissions(integer perm) { if (perm & PERMISSION_CONTROL_CAMERA) { //Do stuff} } In practice, it shouldn't make any difference since permission is granted automatically when you sit on or attach the scripted object. Still, it's never a good idea to assume that any requested permission has been granted.

You will never be redundant, Marigold. Out of a job, perhaps, but never redundant. :smileywink:

According to Torley, who knows everything :smileyhappy: Here's what all the abbreviations mean: B = Base - The object can never be more permissive than this. O = Owner - The permissions the owner (you) currently has. G = Group - The permissions group members currently have on the object. (The group the object is set or deeded to is shown next to Group: above.) E = Everyone - The permissions everyone else has on the object. N = Next Owner - The permissions the next person to own the object will have. F = Full/Folded - The permissions of the object as a whole, including all permissions of the object's contents. For example, a copyable object which has a no-copy item added to its contents becomes non-copyable as a whole because it's restricted by the no-copy content item. M, C, and T = Modify, Copy, and Transfer - Standard permissions. V = Velocity - This actually means "can move" permissions. For instance, if an object shows "E: V", this means everyone can move this object around inworld, which is the the same as Allow anyone to move being enabled. * = Slam bit - Explained more in the next section. You can see the extended answer at http://wiki.secondlife.com/wiki/Debug_Permissions

It can't have anything to do with the computer you used. Any time you buy something, it is stored on SL's asset servers, not your own computer. The listing you see is essentially a table of "pointers" to storage locations in the servers. Having said that, however, it is possible for the inventory listing that you see to get out of sync with the asset servers. You can cure that, if it's the problem, by clearing your cache (click the "Clear Cache" button in Preferences), logging out, and then logging back in at a really vacant sim like Smith or Pooley. When you log in, open your inventory and type anything -- the letter "A" for example) to force the asset servers to rebuild your local copy of the inventory listing. Don't do anything while it's rebuilding. Just go out for a cup of coffee. When it's done, your inventory should be properly synced. Now, if you do that and the items are still missing, then check your Transactions log to verify that you actually bought and paid for the items and then contact the seller with that information. If the items were copiable, you ought o be able o get a redelivery.

Take a good look at Marigold Devin's response to the same question in THIS THREAD. The steps she advises almost always cure ghosting. Good luck. :smileywink:

When you are setting permissions, be sure that you are always doing it on a rezzed copy, not on something in inventory. Permisssions only "stick" on rezzed items. That might account for some of what you're seeing. My guess is that a prim somewhere in your build isn't really set full-perm the way you think it is. Offhand, though, I don't know how to explain the fact that your prim names are wonky. I've found that it helps my peace of mind to activate Debug Permissions in the Advanced (CTRL-Alt-D) menu so that I can see exactly how permissions have been set for the next owner ( N: ) on any item I create.

Ishtara Rothschild wrote: (But now I had the "invalid HTML" error again. It seems that the </blockquote> tag always ends up at the wrong spot in the automatically generated HTML code. That's probably also why you see so many messages where the text under a quote is italicized and appears to be part of the quote, like in Rolig's message above). Hmmmm... That might be it, but if so it's not consistent. I haven't messed with the HTML in this post, for example, and my text is showing up as roman (not italic) despite the quote. The software got it right without intervention this time.