Jump to content

Rolig Loon

Resident
  • Posts

    46,150
  • Joined

  • Days Won

    5

Everything posted by Rolig Loon

  1. Essentially, but it really depends on the size of the prim. You can see megaprims much farther away than jewelry, for example. You have to be close to smaller things to see them. Draw distance just sets an upper limit.
  2. I'm with Darkie. The question is more than a little confusing. However, I get the idea that you want objects to disappear if the rezzer that created them also disappears. Right? You can do that either of two ways: (1) The Rezzer knows that it is going to disappear, so it sends a pre-emptive message to everything that it has created, saying, "I am about to die, and you're going down with me." The rezzed objects hear the message and commit suicide. (2) The Rezzer dies unexpectedly, leaving orphaned objects that it rezzed. It has left each of them with a message that says, "If you hear that I am dead, kill yourself." Case #1 is easy. The script in each rezzed object has a listener that is waiting for a message on a special channel. When the Rezzer sends the message, the receiving script executes llDie and poofs. Case #2 is only a little harder. You can use a "heartbeat" approach in which the rezzer sends a secret message every ten minutes or so. If the rezzed objects hear the message, everything is OK. Otherwise, they poof. Or you can use a "ping" method, in which the rezzed objects call the Rezzer and wait for a response (or just use a sensor). If they don't get a response, they poof.
  3. That probably was not a good idea. Character Test should be one of the last things that you try, not the first ones. Often, all that it takes to clear a bake fail is to type CTRL + Alt + R, or change your hair base or your active group. There's a list of increasingly more powerful methods at http://wiki.phoenixviewer.com/doku.php?id=fs_bake_fail , as Angel pointed out, with Character Test at the very end. Start with the simple things at the top of the list and work down until you find what works for you today. You may find that the bake fail problem comes back repeatedly, even after you fix it with one of the suggestions on that wiki page. If so, you have a chronically weak Internet connection. There are many steps to take for repairing it. Perhaps the simplest ones -- ones that work best for most people -- are: (1) Don't Use WIRELESS. Wireless connections are inherently less stable than direct cable connections and are more vulnerable to interference. Then, (2) Reboot your router. Unplug it from the power for a few minutes to let it clear its RAM. The plug it back in and let it get a fresh hold on an IP address.
  4. See >>> https://jira.secondlife.com/browse/VWR-26759 What you are describing may be the same thing that has been reportd by others. If so, this looks like a problem that may take a long time to solve. You can help by adding your own constructive comments on that JIRA. Just log in to it and use the Comment box at the bottom. It will be most helpful if you provide full information about your computer and Internet coinnection and about which viewer you are using. You can get all of that information by lauching your viewer (Do NOT try to log in. Just get to the login page) and then clicking the Help or About button in the extreme upper left corner of the screen. Cut and paste that information into your report. (Of course, it might have been helpful if you had provided the same information in your question here too.)
  5. No. They are TGA files, but they are not being rendered as images.
  6. The textures just have to be within visual range of an av for the trick to work ... not necessary visible. So, yup, that's a good strategy.
  7. And color that back face black, so that it isn't obvious that you are rezzing a pic on it. You can also rez a different pic on each ot the other four sides, thus pre-loading up to 5 pics before you actually rotate them onto the front face.
  8. Try this first .... Set Preferences → Network & Cache → Cache Size to maximum (10240MB or the maximum space available, whichever is less) If it doesn't work, then try this .... Disable Preferences → Graphics → Rendering → Use HTTP Textures; that done, please go to Preferences → Network & Cache and click the Clear Cache button, then relog.
  9. Get in touch with the owner of the sim where you lost it. Ask him/her to do two things: 1. Look for your car at the sim's garbage collection spot, location < 0.0,0.0,0.0> . He'll probably find a lot of lost things there --- maybe your car. 2. Open World >> Debug >> Top Scripts and look for your car by either your name or its name. If you can't find the car with either of those two steps, then it is either in your invenory, but not showing up in your locally cached copy, or it is lost forever. If it's just not showing up in your locally cached copy of invenory, clear your cache and rebuild it. You may want to do that manually, from outside SL >>> http://wiki.phoenixviewer.com/doku.php?id=cache_clear . Those instructions will work for any viewer, but were written for Phoenix/Firestorm users.
  10. I have absolutely no idea. After all, every product like this has a custom-designed script that is unique to that product. Because the script is almost certainly no-mod, there's no way to guess how the scripter wrote it, or why it isn't doing what you expect. All I can suggest is 1. Try sitting in a different seat 2. Try resetting the script 3. Try reading whatever instructions came with it 4. Try contacting the creator again.
  11. From the superb support staff at Firestorm ..... Chances are good that the problem lies with the SL servers or the voice provider, Vivox. Still, there are things you can try: What sometimes also helps to get voice working is disabling voice in Preferences → Sound & Media -> Voice Settings, hitting apply, waiting a minute and then enabling voice and hitting apply. When these methods fail (assuming voice usually works for you) it is usually the Vivox voice servers that are the problem.Try going to another region to see if voice works there. If so, then the issue is the region you were in before. Was voice disabled there? If not, a region restart might solve the problem.Try a relog, or even a reboot of the computer.Sometimes device settings can reset, so check in Preferences → Sound & Media -> Voice Settings → Audio Device Settings, to be sure that the input and output are set correctly.
  12. Wait until tomorrow. Most sims are getting a server upgrade tomorrow that should fix the problem. ...... Stuck Presence IssuePosted by Status Desk on January 28th, 2012 at 10:15 am PST [postED 10:03AM 28 January 2012] We are aware that some residents are experiencing log in issues caused by a stuck presence from their previous log out from Second Life. This problem can usually be cleared by logging into a different region by following these steps: 1. Open Second Life Preferences to the General tab and check the box ‘Show at Log in’ for the start location options to appear on the log in screen. 2. Using the drop down menu to the right of the Log In button on the Log in Screen, change the drop down to ‘Type region name’ and type in another region such as the region [Lime] 3. Click Log In. If this does not allow you to log in please submit a Support case using Technical Questions > Second Life Viewer Login Issues for assistance. The cause of this issue is currently under investigation.
  13. You don't. You sell your L$ and then send the dollars you get for the sale to PayPal >>> http://community.secondlife.com/t5/English-Knowledge-Base/Buying-and-selling-Linden-dollars/ta-p/700107
  14. Some issues you might encounter are due to “bad” gestures (for lack of a better term). In brief, one or more gestures may fail to load properly and cause the viewer to time out. Symptoms which may be the result of problem gestures include: You are unable to log in properly without having to clear cache fully before doing so. It should never be necessary to clear cache before logging in, so if you have to do this, something is wrong. Some find that if they don't clear cache each time, they get logged out within seconds of logging in, or perhaps they are ruthed or a cloud every time, or even that they crash shortly after log in.You are able to log in but find yourself under water (all you can see is a blue screen) at coordinates 10, 10, 10. If you log in to an all blue screen, check your location, see if you are near the SIM corner, at 10, 10, 10. If so, you almost certainly have a problem gesture.In some cases, you will see that there is an error in loading one or more gestures. If you do, make careful note of which ones, then find them and deactivate them - or better, delete them. If there is no such message, then please read on, here >>> http://wiki.phoenixviewer.com/doku.php?id=gesture_issues.
  15. Not another browser.... another viewer. All that happened was that your viewer got stuck on the TOS page. It's an old bug. Try Firestorm >>> http://www.phoenixviewer.com/downloads.php All you have to do is log in and accept the TOS. Then you can either continue in world with Firestorm or you can log out and go back to using V3 or whatever you were using before.
  16. Actually, you can't send L$ to Paypal, because they are just in-world tokens. What you do is sell your L$ for dollars. Those end up in your dollar account balance, so you can send them to Paypal. See >>> http://community.secondlife.com/t5/English-Knowledge-Base/Buying-and-selling-Linden-dollars/ta-p/700107
  17. That's one of the basic methods, and it's near the top of the list at http://wiki.phoenixviewer.com/doku.php?id=bake_fail , which the OP says she tried.
  18. You change your password by clicking on the Account menu on the left side of the page. I have no idea what question you want to ask ( or "rest"?? ), though, and there is no place on your dashboard to ask a question.
  19. If you have tried everything at http://wiki.phoenixviewer.com/doku.php?id=fs_bake_fail , and it still doesn't cure you, then you have a larger problem. You may find that the bake fail problem comes back repeatedly, even after you fix it with one of the suggestions on that wiki page. If so, you have a chronically weak Internet connection. There are many steps to take for repairing it. Perhaps the simplest ones -- ones that work best for most people -- are: (1) Don't Use WIRELESS. Wireless connections are inherently less stable than direct cable connections and are more vulnerable to interference. Then, (2) Reboot your router. Unplug it from the power for a few minutes to let it clear its RAM. The plug it back in and let it get a fresh hold on an IP address. If neither of those solutions help, check with your ISP to see if there are problems with your Internet service. You may also need to consider replacing your router.
  20. According to notes in the wiki at http://wiki.secondlife.com/wiki/Internal_Animations , hold_r_handgun is automaticlly replaced by aim_r_handgun in mouselook. That's the way those internal animations are designed to work. The aim_r_handgun animation triggers targeting, but the hold_r_handgun animation does not. You should probably try shopping for a simple animation for your project, or try your hand at making one of your own with QAvimator. See http://wiki.secondlife.com/wiki/How_to_create_animations .
  21. If you are using Firestorm, look in Preferences >> Firestorm for a box labelled “Don't send Avatar Physics to server”. If that box has been checked, then physics effects will not be transmitted to SL's servers so they can be viewed in world. I assume that there is a similar setting in V3.
  22. Most of the time when people have trouble logging in to SL, the problem is on their own computer or in their Internet connection. This last week's ghosting problem was a fairly rare exception, an unforeseen side-effect of changes that LL made to their own servers. If you are having trouble logging in, we'll need to have a lot more information before any of us can begin to recommend a solution. You didn't even tell us what kind of computer you have, or anything about it (What graphics card? How much memory? What kind o Internet connection?). You also didn't tell us which SL viewer you are using, or tell us about any error messages you might be getting. What happens when you try to log in? You can add all of that important information to your question by clicking on the Options link in its upper right corner and selecting EDIT. Please do NOT start a new thread.
  23. Restarting the sim is not likely to make any difference, so don't worry about that. If you have tried the recommended solution and it does not work for you, file a support ticket and wait patiently. By the time LL reviews your ticket, the problem will probably be fixed anyway >>> http://community.secondlife.com/t5/Second-Life-Server/Deploys-for-the-week-of-2012-01-30/m-p/1359977
  24. Be patient. If you have tried the recommended workaround and it has not worked, then LL will review your Support ticket as soon as they can. By the time they review it, however, the problem may be solved anyway. See >>> http://community.secondlife.com/t5/Second-Life-Server/Deploys-for-the-week-of-2012-01-30/m-p/1359977 .
  25. Chances are good that the problem lies with the SL servers or the voice provider, Vivox. Still, there are things you can try: What sometimes also helps to get voice working is disabling voice in Preferences → Sound & Media -> Voice Settings, hitting apply, waiting a minute and then enabling voice and hitting apply. When these methods fail (assuming voice usually works for you) it is usually the Vivox voice servers that are the problem.Try going to another region to see if voice works there. If so, then the issue is the region you were in before. Was voice disabled there? If not, a region restart might solve the problem.Try a relog, or even a reboot of the computer.Sometimes device settings can reset, so check in Preferences → Sound & Media -> Voice Settings → Audio Device Settings, to be sure that the input and output are set correctly.
×
×
  • Create New...