Jump to content

Rolig Loon

Resident
  • Content Count

    40,225
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Rolig Loon

  1. Talvez meu tradutor está tendo dificuldade em entender Português, ou talvez eu só não entendo o que você está tentando fazer. Por que você nunca quer bloquear ou silenciar alguém em sua lista de amigos? As pessoas usam essa opção para que eles não ouvirão o discurso ofensivo. Se você bloquear um amigo, o amigo vai naturalmente supor que você encontrá-la ofensiva. Essa é uma mensagem cruel de dar um amigo. Se você não quer manter a amizade com alguém, removê-la da sua lista de amigos. Se você quiser apenas para mantê-la de ver que você está no SL, desmarque o "olho" símbolo ao lado de seu nome.
  2. Well, you can log in to SL first and use your in-world Destinations Guide or any LM or SLURL you have handy. Or you can fix Firefox. Go to your Tools menu in Firefox and select Options. In the Options window, click the Applications tab and scroll down to find secondlife files. Highlight it and then, in the right column, use the dropdown menu to select "Other ..." and then specify the viewer that you are using. Until you do that, Firefox doesn't know what to do with a SLURL or any other URL that it custom-designed for SL. Making that small change points it to your viewer, which DOES know.
  3. Doing the Character Test rebuild doesn't work, eh? Try going to your Library >> Clothing >> Initial Outfits folder in Inventory and wearing any of those outfits. It should have the same effect as doing Character test, except that it's loading a different basic av on you. If that still doesn't work, I suspect that there's something borked in one of the avatar files on your hard drive. Before you try reinstalling your viewer, remove all files associated with this one manually. Writing over them with a new install may just pass the bug along. See http://blog.nalates.net/2011/02/22/second-life-clean-install/ or http://wiki.phoenixviewer.com/doku.php?id=fs_clean_reinstall
  4. Hmmmm... My response to your last question was about as simple as it gets. Crash logger errors usually indicate that there's something wrong with the SL viewer you are using. Deleting your user_settings folder, which contains your Preferences, often clears things up because it forces your viewer to create a new, clean folder the next time it fires up. If that didn't work, chances are that the viewer itself is damaged (or that your computer does not meet LL's recommended standards). Take Darkie's advice and try a different viewer. Before you install it, however, be sure to completely remove the one that's there now instead of loading a new one on top of it. That way, your new viewer will avoid inheriting any damaged files. Meanwhile, please do check https://secondlife.com/my/support/system-requirements/?lang=en-US to be sure that your computer meets LL's standards and is capable of running any viewer.
  5. If you don't read anything else, read this >>> http://secondlife.com/my/whatnext/basics/index.php?lang=en-US Welcome to Second Life, liko.
  6. It may be a temporary suspension, if you are lucky. Call the number, as suggested, and watch for e-mail.
  7. Premium accounts with 512m2 available tier qualify for a Linden Home. For example, if you have a new premium account — you've just joined Second Life as a premium account or upgraded from a basic account — and haven't changed your land usage, then you have exactly 512m2 of available tier. You can also use tier to buy land on the mainland or rent land on a private estate. This is essentially free land. If you don't use it for a Linden house, you use it elsewhere. If you want more than the 512, then you pay for the extra. It's all part of the deal in becoming Premium. If you go back to Basic, the deal's off. No house, no free land. You're welcome to rent and do all of the other things that non-landowners do, though.
  8. Void Singer wrote: we used to have all sorts of programming related discussions, and I know I would more than welcome having them again. Me too. We don't often get chatty here, but I think of the forum regulars as friends and am always pleased to see when two or more of us chime in on a challenge. Even better, when one of us poses a knotty problem that the rest of us wish WE had asked.
  9. It is hard to give helpful answer without knowing what sort of error message you are seeing when you try to log in. Let me take a wild stab, though..... Does it say "You cannot log into Second Life from this location" ? This error message may also appear as: Login failed. Second Life cannot be accessed from this computer. These messages generally indicate you have been blocked from the Second Life servers by Linden Lab as the result of: Documented cases of fraud Use of Second Life by a minor Exceptionally flagrant abuse activity Note that someone else in your household may be responsible for this activity, not necessariliy with your account. You should have received an e-mail from LL explaining the action and telling you about your options for appeal. If you cannot find it, check your e-mail's spam filter. If you believe that this is an error, submit a support ticket via the support portal. To help customer support determine what block has been placed and why, include in the ticket your Second Life account name and any Second Life accounts that log in from your location. If that is not the error message you are getting, please add more information to your question by clicking the Options link in its upper right corner and selecting Edit.
  10. Do you have a question? You can add information to your post by clicking on the Options link in its upper right corner and selecting Edit.
  11. Open Preferences (CTRL + P) >>> Network & Cache and look for Chat Logs Location: Shows the location of your chat logs. (Chat logging is enabled in the Privacy tab.)
  12. It is possible to do, but it will take a lot of work on your part. You can create a group for all tenants in your parcel and then give each of them a prorated portion of the parcel's total prim allowance. Because they are all in the same group, they'll end up having building rights in each other's shops or apartments, and there is no straightforward mechanism for enforcing the prim limits. As the landlord, you may find yourself having to respond to complaints about who gets to build where. You can get a script to keep track of how many prims each person in the parcel owns (or can hire a scripter to write one), and then you can decide how to deal with the information if it shows that someone is running over their allotment. The bottom line is that you can't expect to be an absentee landlord.
  13. Rolig Loon

    premium count

    There's an easy way to know whether your membership information was recorded correctly. Go to http://secondlife.com and log in with your user id and password. If you can log in, your account is active. Then, click on the Account link on the left side of the page. The Account Summary will show your membership status and tell which plan you are enrolled with. You can check all the other options to verify that your billing address and other details are correct.
  14. I suppose in theory you could make a device that sits in a region and then uses llGetParcelDetails(Pos,[PARCEL_DETAILS_NAME]), looping around possible values of Pos in 4m increments to make a list of all parcel names, then removes duplicates, and moves on to the next region. Talk about a colossal and endless pain in the butt, to say nothing of impractical ........
  15. If you want help with one you are writing yourself, ask in the LSL Scripting Forum >>> http://community.secondlife.com/t5/LSL-Scripting/bd-p/LSLScripting. Otherwise, post your question in the Wanted section of the Commerce Forum >>> http://community.secondlife.com/t5/Wanted/bd-p/Wanted or look in any of the shops in world (or on Marketplace) that sell basic scripts.
  16. No. If you want to raise your arms, you need an animation that does it. If you are lucky, you can find one in the many animations stores in world and on Marketplace. If not, you'll either have to convince an animator to make (and sell) you a custom animation, or you'll have to learn how to make one yourself. Once you have the animation, you can trigger it with a gesture or put it into a script that will activate it when you want it.
  17. PRIM_POSITION is global. To move the child prim, as Void says, you first need to know what it is (hence the need to use GLPP). Then you need to convert it to a local position (hence the need for the calculation). THEN you get to set it with SLPPF.
  18. This emphasizes again the reason for doing a Clean Install. The Firestorm team is very clear about that. If you are going to update Firestorm, always delete it completely from your computer before installing a new version. Do not install a new one on top of an old one, or expect a new one to like the user_settings file that you made for the old one. That's true for LL's V2 and most other viewers as well. It's best to start with a clean slate.
  19. Just remember Darkie's very cogent warning about dropping scripts into objects. To quote from the LSL wiki: "Scripts are an exception to what is allowed to be dropped in. If a user without modify permissions to a prim attempts to drop a script into it, the inventory addition is rejected and the prim shouts (sic -- shouts, not says) "Not permitted to edit this!" This is for obvious security reasons. If you own the prim and have mod rights to it, you can drop a script in. Friends who have mod rights to your stuff can also drop scripts in. " So, if you are going to use this approach, be sure that you give next owner MOD rights to the object. Darkie's got the answers to the three questions you just posed. I agree with him that the llMessageLinked approach is still the most efficient way to handle things, from the scripter's perspective. It requires less event handling, is faster, and is a zero lag solution. From a user's perspective, the solution I proposed may be easier to understand, if only because most novice scripters are more familiar with chat and more likely to screw up an unfamiliar linked message. I'm really not making a strong argument for it. I just proposed it so you could see that there is an alternative.
  20. I think we're mostly on the same page, Innula, although I'm less impressed by the fact that Singularity and CoolVL will have mesh viewing capability. Those are fine viewers, but they have a niche following. The big dog is Phoenix/Firestorm, which currently have #1 and #3 place for total users. It's a fair bet that Phoenix users will move to Firestorm as mesh and other developments make V1 less attractive. In the end, then, what Firestorm does to handle mesh is what really counts. Once they can let people see mesh, it will start to take off --- if the economics is right and if the other limitations people have talked about here don't put people off. As I said earlier, I'm in no big hurry to start spending L$ on mesh, and I have enough other projects on my plate that I'm not eager to rush into making mesh objects to add to my shop. I'll wait and watch.
  21. Darkie Minotaur wrote: OOne general remark: People can't drop scripts into objects that don't belong to them - the wiki would have told you that as well Oh, yeah. I forgot that too. :smileysurprised::smileysad: So much for a cool solution.
  22. A script cannot listen to chat generated in the same prim. However, it can listen to chat generated in another prim in the same linkset. Like Darkie, I think that llMessageLinked is generally the preferable solution because all communication is internal, requiring no listeners at all. If you're interested in what's likely to be easiest for a potential user, though, I'd suggest creating a two-prim object. (Put your own script in a small root prim and leave a BIG, obvious child prim for the other person to drop their script in. ETA: See below )Then issue one simple rule: Your script must contain this line in state_entry: gChannel = (integer)("0xF" + llGetSubString(llGetKey(),0,6)); and chat messages must be in the form llWhisper(gChannel, message). Then just be sure that your own script contains the same definition of gChannel and has an open listener tuned to it. That guarantees that your script and the new one will always be communicating on a high negative channel that is unique to the object itself (since it is based on the object's own UUID). That simple rule is easy for others to follow and minimizes lag issues with chat. ETA: Anything the user drops in the object will end up in the root prim (d'uh, forgot that), but you can move it as soon as it's dropped in. Just write: llGiveInventory(llGetLinkKey(prim),gThisScript); if (~llGetInventoryType(gThisScript)) { llRemoveInventory(gThisScript); }  where prim is the number of the child prim (2) and gThisScript is the name of the script someone just dropped in.
  23. Well, no. Or not exactly. LL has not offered support for its own V1 viewer, 1.23, since last year. As they continue to add features to the V2 codebase -- including changes in the server software as well as their V2 viewer -- it will become harder and harder for the TPVs to keep pace by adding patches to their V1 viewers. Some of the new features are simply incompatible with the old architecture, and some of the old V1 features will start breaking as the servers no longer have the infrastructure that they depend on. LL won't need to "close" V1 viewers, but the effect will be the same. In a reasonably short period of time, people who are still using 1.23, Phoenix, Imprudence, Singularity, and the other V1s will find that they are spending more time complaining and less time enjoying SL, because things just won't work right any more. Despite the series of bugs that have plagued each of LL's recent V2 releases, the balance is continuing to tip toward the V2s. Phoenix is still the most popular viewer in SL, but it is followed by LL's V2 and then Firestorm (also a V2), and then 1.23. The fact that Firestorm is already in 3rd place while it is still in beta is an indication of how near we are to the day when V1s will have simply faded away.
  24. First, check to be sure that your laptops meet LL's recommended standards >>> https://secondlife.com/my/support/system-requirements/index.php?lang=en-US . Not all laptops do, especially if they have built-in graphics chips instead of graphics cards. If they do meet standards, avoid trying to use wireless. Many people have trouble with wireless connections in SL, because they are often less stable than a direct cable connection and they can suffer from interference from cell phones, garage door openrs, and other appliances, to say nothing of everyone else in the Starbucks or your residence hall. Those steps will address a couple of the most common reasons for disconnection problems. If you are actually crashing, though (that is, you are getting a system error message that says LL is unable to log you in, or whatever ...), it's hard to know what the next step is unless we know what the error message is. You may add more information to your question by clicking on the Options link in its upper right corner and selecting EDIT.
  25. When you've done that, use your in world search to look for groups that are related to scripting. You'll find that many of your special interests groups are represented there.
×
×
  • Create New...