Jump to content

Rolig Loon

Resident
  • Posts

    46,151
  • Joined

  • Days Won

    5

Everything posted by Rolig Loon

  1. GenysisGwynn Nicoletti wrote: [...] if a person owns something then shouldn't they be able to retain it until they sell it? Since CR was not paying for land, (my understanding from CR is she paid a hefty price for this land) and was behind on prim payments I would think the LL would've given the option to sell the land to make up for the arrears, but again I don't understand how this works, how can you purchase land from someone who is effectively "renting' themselves? This sounds shady to me, but again I admit I'm not well versed in this, so that's why I posed the question here...Your response would work well If I needed a lesson in becoming a landlord, I'm asking I guess from the tenant side, but again I thank you immensely for your response... To be a knowledgable tenant, you have to know something about how the landlord's business works. That's why I bothered to explain. The point is that CR does not "own" the land at all. As I explained, the only owner is the landlord, and he is only actually renting it from LL. CR's landlord may have offered her a one-time "set-up" fee and then be charging her a monthly prim fee after that, but she is still on his region, paying a fee for continued use of the land. If she doesn't keep up her end of the bargain by paying that fee, the landlord can look for another tenant who will. He still has his own rent to pay to LL. (In fact, the deal he offered to CR is similar to the deal that LL made with him. He paid a one-time fee to "buy" the sim and is obliged to pay LL a monthly land use fee to stay on it.) Yes, the arrangement is ripe for abuse, and a mercifully small number of landlords do abuse it. You make your own decisions about whom to trust and what risks you are willing to take. Personally, I think CR got a pretty good deal and it sounds as if the landlord did cut her some slack for a while.
  2. I'll answer the philosophical part of your question separately. "Lastly, but this may be rhetorical at best, why make these beautiful items with scripts if they're known to be complicit in causing lag, why make items with resize scripts at all, why not make the item modifiable? I know some things require scripts but what is the happy medium between not being a contributor of lag and script errors and owning beautiful items that require scripts ?" It's true that scripts contribute to lag, but it's a little unfair to go overboard and avoid necessary scripts. Without scripts, after all, we'd have no AOs to control our animations, no HUDs to control vehicles or help us fly above the 300m ceiling,..... It's wise to avoid wearing unnecessary scripts, though. Resizers are in a murky category. Personally, I don't use them because (1) they resize things but can't reshape them to fit my body better and (2) I find it a lot easier to hop up on a pose stand and make alterations myself in a couple of minutes. Many SL residents don't care to learn to do their own alterations, though, or don't want to spend valuable time fiddling with them. Resizers are "necessary" convenience for them. One rational solution is to sell clothing and hair with copy perms that include self-deleting resizer scripts. That way, creators can retain some control over the types of modifications that they allow, and buyers can get rid of the scripts when they don't need them any more. Many creators do exactly that. My own solution, as a clothing designer, is not to offer resizing scripts at all, and to sell everything with copy/mod perms.
  3. There are many good scrubber scripts around SL. The best ones are free, so don't pay good money for one. See >> http://community.secondlife.com/t5/LSL-Library/Script-Remover-for-Linksets/td-p/721141 and >>> http://community.secondlife.com/t5/Scripting-Library/Zen-Scrubber/td-p/236177 Scrubbers will remove all traces of other scripts, and can reset prim properties that are normally set by scripts (particle effects, for example). They cannot do anything at all if you drop them in a no-mod object, however. After all, no mod means NO mod, including removing scripts. Also, when they remove scripts, they eliminate them completely. They don't just move them to your inventory. If your object was no-copy, you'd have no backup --- no way to replace the scrubbed scripts if you wanted to. So ..... (1) If you have copy perms on an object, make a copy and scrub it after you have done any resizing or color changes that you needed its scripts for. (2) If you do not have opy perms, do not use a scrubber. Instead, do any resizing and recoloring and then manually drag/drop its scripts to a backup folder in your own inventory and delete them from the object. (3) If the object is no-mod, forget any of this. You can't do a thing. Finally, the way to find out if a script is safe to remove, is to remove it and find out. If you're working with a copy and you screwed it up, there's no loss. If you have dragged the scripts out of a no-copy object and you regret it, drag them back in. Again, no loss.
  4. The landlord owns the region. He can deal with others in the region in either of two ways: (1) he can divide it into parcels that are deeded to a rental group (or perhaps just kept in his own name) and then place rental boxes on each parcel or (2) he can deed individual parcels to individuals or groups. In either case, he is still responsible for paying the monthly land fees to LL, so he has to collect L$ from each person on those parcels. Call it "rent", or call it a "usage fee" or whatever.... the person on each parcel has to pay the landlord, not LL. The difference between the two arrangements is subtle. If the parcels are all owned by a rental group, then they share a pool of prims. If one parcel is vacant or underutilized, perhaps left as park land, the landlord can use bonuses to transfer some of its prim allowance to occupied parcels. That way he can offer a small parcel with bonus prims for a higher rental fee. The down side is that the tenants on all parcels belong to the same group and can potentially use more than their prim allotment by using a neighbor''s. They can also rez on each other's land. The landlord therefore has to do more police work and bookkeeping with that arrangement. If parcels are deeded to separate groups, on the other hand, the landlord has less work to do and the tenants are less interdependent, but they also can't benefit from sharing prim alowances with other parcels. The landlord on my own sim uses both methods. Long-term residents like me mostly have deeded parcels; short-term renters are in a communal rental group. The landlord can redistribute prim allowances among the renters in that group, and can "borrow" prim allowance from an unrented hilly parcel. Nobody builds on my parcel or uses my prims but me. The bottom line, though, is that in either arrangement, the landlord owns the sim, is responsible for paying LL, and has full control over setting and enforcing its convenant. He has the right to eject anyone who is not paying on time or who is breaking the covenant.
  5. You'll have to tell us what the problem is if you want an answer. If this is related to a previous question, please do NOT start a new thread. You can add important information to your original question by clicking on the Options link in its upper right corner and selecting EDIT.
  6. Viewers are not designed for specific computers, and certainly not for specific cell phones. Take a look at the few limited applications available for mobile systems here >>> http://wiki.secondlife.com/wiki/Third_Party_Viewer_Directory. There are a couple that will give you text capability so you can send IMs, for example.
  7. You will have to tell us more information before we will have any hope of knowing the answer. What computer are you using? What graphics card? What error messages are you receiving? What have you tried already? You can add important information to your question by clicking on the Options link in its upper right corner and selcting EDIT. Please do NOT start a new question.
  8. That's a communication problem between your computer and SL's servers. Information about your appearance has to be "baked" onto your avatar on your own computer, saved there, and then uploaded to SL before it's fully visible there. If the necessary information is messed up in transmission, you may end up with a borked file on your computer, or SL's servers may end up with a borked file. Either way, your av's appearance defaults to a fluffy cloud. What works to repair the damage for one person won't necessarily work for the next person, and it may not be the same thing that works for you tomorrow. See the full list of possibilitites here >>> http://wiki.phoenixviewer.com/doku.php?id=fs_bake_fail . Start with the simple things at the top of the list and work down until you find what works for you today.
  9. So, if you want it to talk to the person, do exactly what Innula and the others suggested. Use llRegionSayTo on the public chat channel instead of on the non-zero channel I chose. It will speak to the sitting av instead of her attached HUD. No big deal. And if you want to send the same annoying message over and over again, trigger a timer event with the message in it as soon as the av sits down. ETA: As I read your message again, it seems to imply that you and some other person are both planning to sit on the object at the same time. You can only have one sit target in a prim, so the person identified by the script as llAvatarOnSitTarget will be the person who gets there first. An additional person on the same prim is not on the sit target, so will not be interacting with the script.
  10. This may depend on which viewer you are using and how you have it configured. In my viewer (Firestorm), I have chosen never to dock any floating windows, so I can grab the top bar in the IM window with my mouse and drag the window where Iwant it. If your viewer docks windows by default, just click the tiny UNdock arrow in its upper right corner and then drag it.
  11. The default for beacons is Sounds, so unless you set it to be a beacon for something else when you open the control window with CTRL + Shift _+ Alt + N, that's what the purple box is identifying. You don't really need a beacon, though. To highlight transparent objects, you need CTRL + Alt + T. Once you do that, your invisible box should show with a red color. All you have to do is right click on it and select "Detach". You could also just go to your inventory, open the Worn tab, find the object there, and right-click and select Detach.
  12. Here's a simple script for the seat.... stopAnim(){ list temp = llGetAnimationList(gAv); integer i = (temp !=[]); while(~(--i)) { llStopAnimation(llList2String(temp,i)); }}key gAv;default{ state_entry() { llSitTarget(<0.0,0.0,0.5>,ZERO_ROTATION); //Change this sit target as necessary } changed (integer change) { if (change & CHANGED_LINK) { if(llAvatarOnSitTarget()) //When Av sits down.... { gAv = llAvatarOnSitTarget(); llRequestPermissions(gAv,PERMISSION_TRIGGER_ANIMATION); } else // When Av stands up .... { llRegionSayTo(gAv,-47102,"Good Bye!"); //Message to HUD script } } } run_time_permissions(integer perm) { if(perm & PERMISSION_TRIGGER_ANIMATION) { stopAnim(); llStartAnimation(llGetInventoryName(INVENTORY_ANIMATION,0)); llRegionSayTo(gAv,-47102,"Hello!"); //Message to HUD script } }} And here's an accompanying HUD script .... default{ state_entry() { llListen(-47102,"","",""); } listen(integer channel, string name, key id, string msg) { if(msg == "Hello!") // The sit down message { llSetColor(<0.0,1.0,0.0>,ALL_SIDES); } else if (msg == "Good Bye!") // The standup message { llSetColor(<1.0,0.0,0.0>,ALL_SIDES); } }} The trick here is that the llRegionSayTo function speaks to an attachment that the av is wearing (the HUD in this case) if the message is sent on a non-zero channel. Because the message is aimed at the AvatarOnSitTarget, the only HUD that will hear it is the one being worn by that particular av.
  13. This is a good place to point out that mastering syntax is the easiest part of learning to script. The hard part is logic, and that is almost independent of the scripting language and its syntax. Map out (on paper if necessary, but at least in your head) what the path from your starting point to the finish line has to look like. Where are the decision points along the way? What will happen at each of them if the user makes a different choice or if the script's environment changes? What pieces of information will you need in order to make decisions at each of those points? How will you know when you have reached them? If you can create a logical map that answers those questions, finding the syntax to describe the map is relatively simple. In this case, remember that LSL is an event-driven language. Actions in the environment trigger events, and all actions take place in those events. Once a timed event is triggered, the action that occurs happens in the timer event.
  14. The table at http://wiki.secondlife.com/wiki/Rotation is about as comprehensive as you're going to get. That whole article is helpful. See also http://wiki.secondlife.com/wiki/User:Void_Singer/Rotations
  15. Now that you have the llMessageLinked syntax figured out, get rid of it. If all you are doing is changing a texture in the other prim, use llSetLinkTexture. That lets you change the texture in the other prim directly and it gets rid of an unnecessary script in that prim too.
  16. It's not clear to me why you want to clear cache. That shouldn't be necessary unless one or more of your cached files (inventory, appearance, preferences...) has gotten out of sync with SL's servers. Othrrwise, clearing cache has little effect, excpt that it slows down rezzing the next time you log in because your computer is having to reload all the files you wiped out. If you really want to clear your cache, though, you don't have to be in SL to do it. Clear your cache manually. See >>> http://wiki.phoenixviewer.com/doku.php?id=cache_clear
  17. Call the billing office and ask why. LL's billing team is available 24 hours a day, seven days a week. Toll-Free (US/Canada) 800.294.1067 Long-Distance 703.286.6277 Local Toll-Free numbers * France: 0805.101.490 * Germany: 0800.664.5510 * Japan: 0066.33.132.830 * Portugal: 800.814.450 * Spain: 800.300.560 * UK: 0800.048.4646 * Support is in English Only
  18. Yeah.. annoying. :smileysad: It should be easy to find, though. A script can't do anything unless it is in an object, and the object must be attached to you. So, open your inventory, click the Worn tab, and look for unfamiliar objects. You're looking for something named Croft Window. When you find it, detach it and delete it from your inventory. If you want to put off the search for some reason, you could always just mute the thing for now.
  19. Yeah, it could be LL's servers doing something wierd. It could also be your own system. Textures in SL are rendered in four passes, increasing in resolution on each pass. That saves your GPU from having to render sharp images that you won't see for more than a fleeting glance. If your connection is good, the textures are already cached on your machine, your drawing distance is reasonably short, there aren't a lot of things to render in your field of view, and LL's servers aren't lagging, it usually takes only a few seconds to go from the first pass through the fourth one. The more work your GPU has to do and the crummier your connection, the longer it takes .... sometimes an hour or more. It's hard to sort out which factor is the limiting one. If you want an independent reference point, though ...... I haven't seen any change in rezzing behavior anywhere I have been in the past month or two.
  20. Rumors are worth the paper they aren't written on.
  21. I suspect that the reason is partly financial and partly social. The financial part, as others said, is that mesh costs more to upload than a simple image. You can run up a big bill very quickly if you are uploading test meshes to the main grid, and LL probably wants to know how you are going to pay for it. The social part is just my guess, but I think it's one way for LL to deal with people who might be tempted to upload stolen mesh. If you have payment information on file, you can't be anonymous. I know people have been able to upload ripped off image files since Day One, too, but it's too late to go back and make everyone have PIOF (although it would be a great idea). This way they can start with a clean slate and at least minimize mesh theft. BTW, I agree. We have complained for a long time about how hard it is for an OP to respond to her own thread here. You seem to have figured out our clunky system, though. Congratulations.
  22. No. That username is like your Social Security Number in RL. It's yours for life. You can open a brand new account if you like, or you can use a Display Name, but there's absolutely nothing you can do to your username.
  23. Nope. Your chat logs are not saved in the SL servers. They are only in the Local files on your machine. If you erase those files, they are no longer a historical record. They are history.
  24. There are free door scripts all over SL. For a start, take a look right here in the LSL Scripting Library. If you want a nice, simple rotating door, see >>> http://community.secondlife.com/t5/LSL-Library/Simple-Hinge-Action/td-p/875331. If you want a sliding one, try >>> http://community.secondlife.com/t5/LSL-Library/Linkable-Multiprim-Sliding-Door/td-p/722649
  25. Rolig Loon

    Shoe light?

    See my response in IM. You aren't making it light by right clicking on it. You are selecting it and seeing the selection highlight. A face light is not like a flashlight. Don't expect to see a beam. A face light makes YOU light up by brightening everything within the radius you have set in it. It doesn't make ITSELF brighter.
×
×
  • Create New...