Jump to content

Rolig Loon

Resident
  • Content Count

    40,107
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Rolig Loon

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. Welcome to Second Life, Franswar. You have just discovered lag. There are many causes of lag, but many of them are under your direct control. Take a look here >>> http://wiki.secondlife.com/wiki/Lag and here >>> http://wiki.secondlife.com/wiki/I_have_a_lot_of_lag._How_can_I_improve_performance for some of the basics and for good suggestions about what you can do. The bottom line is that you are asking your computer to do more than it can do comfortably, so you are going to have to adjust some Preference settings and make some decisions about how much you load onto your avatar. Even at that, you will find that some areas in SL that are loaded with textures or physical devices, or that have loads of people in them (like clubs, sporting events, and live music venues) will always have lower performance than normal because there is such a heavy load on servers in those places.
  11. There's nothing showing on the Grid Status blog today, but they will be doing scheduled maintenance on the asset servers early tomorrow. If there is a server issue, it may clear up then.
  12. Beats me. Go to your Dashboard at http://secondlife.com and click on Accounts >> Transaction History to see who you paid money to. You can adjust the dates to look back as far as 30 days in your transaction history. If your balance has changed, the information you need for tracking it down will be there. If you have made Marketplace purchases, they will show up there also, but without details. For details on those transactions, open Marketplace and look at My Marketplace >> Accounts.
  13. If you find one, it will be a rare stroke of luck. Most builders in SL create things Lego-style. We take basic prim shapes, stretch them, tweak them, and stack them until they look like something. If you are trying to replicate something that exists in RL, it sometimes helps to have a few photos to work from. For something as simple as a lighthouse, of course, all you need for the basic shape are a few tapered cylinders. If you are just beginning as a builder, I recommend visiting the Ivory Tower of Prims in world and doing loads of tutorials, or taking a class or two at Builder's Brewery. The real beauty of any build, of course, is in the texturing. Without good textures, all you'll have is a plywood lighthouse that looks like a kid built it. You can probably find freebie masonry textures that will do for a first project. If you want fancier ones, you can start shopping in the zillion texture shops in world and on Marketplace, or you can learn to make them yourself with Photoshop or GIMP.
  14. As you have discovered, there have been many bugs in recent upgrades of LL's V2 viewer. If you are having better luck with a Third Party Viewer, then I'd say go with it, by all means. The Firestorm viewer is proving to be very stable for most people, for example, and they have a responsive amd helpful support team. If you like the V2 user interface, you'll find Firestorms' default screen familiar. If not, you can easily customize it to look much like the classic V1 interface. There are many other TPV alternatives (http://wiki.secondlife.com/wiki/Third_Party_Viewer_Directory) and you can always go back and try earlier versions of V2, if they worked better for you (http://wiki.secondlife.com/wiki/Category:Release_Notes). Just remember, if you install an older V2 version, to go to Preferences >> Setup and UNcheck the box that enables automatic upgrades.
  15. You have to convert your L$ to dollars by selling them in the Linden Exchange (See https://secondlife.com/my/lindex/sell.php), then you have to issue a credit transfer to have the dollars sent to your PayPal account. You have to transfer out at least $25. See http://community.secondlife.com/t5/English-Knowledge-Base/Account-balance/ta-p/700015 .
  16. There are several possibilities, and it's hard to tell which one is the right one. In some cases, you get that error if you have corrupted drivers in your router or, simply, if your driver needs to be rebooted (unplug it for a minute or two, plug it back in, the reboot). Check the Internet to be sure that you have up-to-date drivers and consider downloading and re-installing whatever is there now. You could also have corrupted user settings files, in which case the solution is to find and remove them and then relog to force your viewer to create new ones. (See http://wiki.secondlife.com/wiki/User_settings) If you do that, I would also delete your cache files. If neither of those appoaches works, the viewer itself may be borked, in which case I suggest removing it entirely from your system and then downloading and installing a fresh viewer.
  17. When you are in BUSY mode, your Avatar does not hear nearby chat, IMs receive the “busy mode” response, and all inventory and teleport offers are automatically declined. You will not get your stuff. Follow Valerie's advice.
  18. Where are you getting that message from? Without some context for your question, it's hard to know what it means. You can add details to your question by clicking on the Options link in its upper right coprner and selecting EDIT.
  19. iggur wrote: cant i make another script saying if (name of the script) runs ones...stop? or something like that? Nope. No modify means NO modify. You cannot change your script to make it respond to you or to another script in a different way than it already does. Contact the original scripter or write a new script.
  20. If you tried clearing cache manually, as I described earlier (not by just clicking the "Clear Cache" button in Preferences), and it still did not work, you can still try the more drastic step of completely uninstalling your viewer (See http://wiki.phoenixviewer.com/doku.php?id=fs_clean_reinstall or http://blog.nalates.net/2011/02/22/second-life-clean-install/ ) and installing a fresh copy or a completely different viewer. Your newly installed viewer will be forced to build a locally cached copy of your inventory from LL's servers. If you want to go straight to filing a support ticket, go to https://support.secondlife.com/create-case/
  21. I am not sure that I understand all of your question, but the answer to the part that I do understand is NO. If a script is no mod, you cannot change it in any way. That's what no mod means >>> NO modification. If you want to have a script that does the same calculations but works correctly, you will have to write a new one or talk to the scripter who wrote this one and ask her/him to repair it..
  22. Sharing the cache folder between multiple viewers is a primary cause of “inventory loss” which many experience, although not the only cause. It also frequently results in crashes or erratic behavior. Clearing your cache manually will “cure” all manner of odd behavior and is the suggested procedure before resorting to more drastic steps like reinstalling the viewer. 1. Open Preferences → Network & Cache 2. Go to the first path “Cache Location” and click the “Open” button behind the path. This will open a file explorer window displaying your current cache location. 3. Logout (close the viewer) and then delete everything inside the cache folder displayed in your file explorer. Now continue as follows: 1.Log back into SL, to a quiet region (try Smith or Pooley). On your inventory window, click “Recent Items”. 2.Wait for your inventory to repopulate fully. The process may be sped up, if necessary, by typing random letters into the search bar. 3.While inventory repopulates, do not teleport anywhere, and do not attempt to access anything in your inventory. Talk to people or surf the web, or just go out for coffee 4.Watch as it repopulates. As long as you can see (Fetched…) at the top of the inventory window, it is still loading. 5.Once inventory has repopulated, log out of SL once more, then log back in. That process works in a very high percentage of times. If it does not work for you, then I suggest filing a support ticket that details what you have already tried and asks LL for their help.
  23. You can download any previous V2 version from http://wiki.secondlife.com/wiki/Category:Release_Notes. I strongly suggest that you manually delete the current version before installing the replacement, instead of installing the new one on top of it. Then, before you log in, type CTRL + P at the login screen to open your Preferences. Then go to setup >> disable automatic updates so that it doesn't automatically update itself again.
  24. Hmmm... I so rarely use that feature that I guess I wasn't aware that it ever saved outfits in the Clothing folder. I can't find any LL documentation to verify that it did either.
  25. Good rant. Unfortunately, Lindens rarely come here. We're all SL residents, just like you. Just so you know, LL hasn't removed any viewers at all. You can still download and install 1.23 (currently still the fourth most popular viewer among SL residents) and a full range of third party viewers at http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers . If you're ticked at the current version of the V2 viewer (who isn't?) but are still interested in running a previous version, you can get any of them at http://wiki.secondlife.com/wiki/Category:Release_Notes . If you actually have a question, feel free to add to your post by clicking on the Options link in its upper right corner and selecting EDIT.
×
×
  • Create New...