Jump to content

Rolig Loon

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Rolig Loon

  1. Wait a week. You're only allowed to change your Display name once every seven days. You can Reset your name, of course. Doing that sets your Display name to your username, the official name that you use when you log in.
  2. There are many causes for bake failure, so the same one won't work for everyone every time. Go to http://wiki.phoenixviewer.com/doku.php?id=fs_bake_fail and start trying things, startring at the top of their list and going down one at a time until you find the one that works for you. Something always does. BTW, those suggestions work for any viewer you may be using.
  3. It probably doesn't know that you are the owner. A well-written script that contains any functions which depend on the owner should always include a changed event that looks like this ... changed(integer change){ if(change&CHANGED_OWNER) { llResetScript(); }} That will force the script to reset itself if the object changes owners (as when you give it to an alt, or vice versa). If it's not there, the script will remember who the owner used to be, and only listen to that person. So .... if you can't modify the script or don't care to, just select the object and use Build
  4. LOL... I can relate to OCD. Welcome to the clubhouse. So, you have discovered that CTRL+Alt+T will help you find transparent objects. It doesn't help find objects that are inside other ones or that are really tiny. So, Click on your Build menu at the top of the screen. Select Options and be sure that the Select By Surrounding option is checked. Then type CTRL + 3 to open your Build edit window and drag a selection rectangle around some suspicious-looking area. Anything inside the rectangle will be selected, even if it is inside another object. If it's tiny, you may want to zoom in to
  5. Find yourself a full perm pose ball and take it apart. If you look at the script, you'll see that there's a changed event that is triggered when someone sits on it. That changed event then goes on to ask permission to animate whoever is sitting. Well, you don't want to animate someone -- you want to fire off a particle display instead. So that's where you put the llParticleSystem function to do it. The only other thing you need to do is look at the part of the changed event that is activated when the avatar stands up. That's where you put the llParticleSystem([]) function to stop the part
  6. Noooo.... I was agreeing with you that you can get rid of almost all of the sound preloading, because most of the time the same person will be hearing all of your sound files in a continuous loop. You really only need to preload files the first time that person hears them. So, I suggested getting rid of the sound() function entirely, leaving only a vestige of the preloading business at the tail end of the timer event. Here's a version of what I was suggesting. I have removed all of the global functions that were only used in the sound() function and have tightened up the remaining script a
  7. Yup. You can click Help at the top of this page and then select Contact Support from the menu on the right side of the page, or you can go directly to https://support.secondlife.com/create-case/. .
  8. Picks? You go to a favorite spot and then open the Picks tab in your profile and click the + sign in the lower left corner. Select "New Pick". That will add the spot to your picks. Once you have created a new pick, open it and click the Edit button to make any changes you like.
  9. You ought to be able to. If you have trouble doing it, call LL's billing office (free from Canada!) at 800.294.1067 The Billing team is available 24 hours a day, seven days a week. You might also try using one of the approved third party currency exchanges listed at https://wiki.secondlife.com/wiki/Linden_Lab_Official:Linden_Dollar_Marketplace
  10. You take some of them off. That's what the notice is telling you. If you are carrying around more than about 50 scripts, for a total memory use of more than 2 Mb, then you are probably having some TP problems and may be generating some lag for people around you. Scripted hair and other attachments (shoes, bling...) can be very unfriendly this way.
  11. I suggest re-installing the previous version of the LL viewer or switching to a third party viewer. People are having a lot of trouble with the video driver message since the latest upgrade. When you re-install, be sure to go into Preferences and disable the checkbox that authorizes LL to upload new versions automatically.
  12. Good catch. Until you click the dialog button to select an animation, there's none defined. So pick one and make it the default. Just add anim = "girltype"; at the top of your touch_start event so that it's always the one that plays until you change it. The stopping, starting business is probably in your anims themselves, as you said. You might be able to beat it, though, by tricking the viewer into deliberately restarting the anim each time the timer is triggered. Try llStopAnimation(anim); llStartAnimation(anim); instaed of just starting the anim.
  13. It's a little hard to follow the logic of this script, but it looks as if it's running slowly because you added that user-defined function, sound(). You really shouldn't need that. I think you can do with removing that function and the top part of the timer event..... if( i > last_wave_file_number ) { sound();//This is what I changed or added to keep it looping till you touch it again and stop it. All the rest below was either already omitted or omitted by me where ie: // play = FALSE; was done by me and //llSay(0, "finished."); was omitted by the original maker
  14. YW. Incidentally, if this really is a HUD script, then you don't need the variable that you called toucher, and you don't need to test for it in the touch_start event. After all, only the owner can touch a HUD.
  15. First of all, please remove his name from your post so that you don't get in trouble here for violating Community Standards. Then, consider the possibility that the seller hasn't been in world for a few days (this is a weekend, you know, and most of us have RL to tend to) so he may not have received your note. If he hasn't been in for a while, it's also rather likely that he will never receive it, because his "in box" has capped. If he has received more than 25 IMs, group notices, group invitations, notecards, and objects, the system will simply be trashing any new ones without delivering t
  16. Preloading refers to giving advance notice of what the sound will be to the avatar who will be listening . If the listening avatar hasn't already cached the sound file locally on his/her own machine, it has to be downloaded before the viewer can play it. The delay that you're talking about occurs because it takes time to download the file. So, preloading simply means sending the file to the avatar before it's needed. You can do that by using llPreloadSound. Since you'll be looping the sound indefinitely, though, it's easier to just let the listener deal with a delay the first time the fil
  17. You log in to a different area by specifying the sim's name on your login page, in the pulldown menu just to the right of our password.
  18. You have a very good start. The biggest problem, as you noticed, is the way you are identifying the animation. Instead of using the global variable anim the way you have, replace it with string anim; That's all you need there. Then, in the listen event, that's where you identify which animation to use, as you already have: else if (message == "Male") { anim == "boytype"; } else if (message == "Female") { anim = "girltype"; } Assuming that those are the exact names of the animations in the object's inventory, that should do it. When you get t
  19. If you are not in world to receive items that are sent to you, or if you are in world but in Busy mode, you may fail to receive things. Each of us has an "in box" that holds IMs, group messages, group invitations, notecards, and any items that people send when we are not around or are busy. That "in box" will only hold 25 items. Once it is full, it refuses to accept any more. It doesn't return them, and it doesn't even tell the person who sent them ..... it just deletes them -- Poof! -- forever.
  20. Yup. The new LL viewers only require a single name for login, but the older ones and many of the TPVs all do, so "Resident" is LL's clever way of giving every one-named person a dummy second name to keep those viewers happy.
  21. Rolig Loon

    lindens missing

    Contact the LL Billing office and ask a live person there for assistance. The 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
  22. 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 w
  23. The servers in SL have been touchier than usual lately, so the crashing may not be entirely your fault. Still, that's probably the best bet. Try logging in to a different sim, especially one that is virtually lag-free, like Pooley or Smith. See if you still crash there. If so, it's probably not SL's servers giving you trouble. So then, open your statistics bar (CTRL+Shift+1). Particularly if you are seeing packet loss more than 0.5% or so, the problem is probably on your end, possibly your router, as already suggested. If you're on wireless, switch to a direct cable connection instead, beca
  24. Your last name is Resident. It's like that special name that the U.S. Postal Service puts on your junk mail: " ...or Current Resident." Current Resident is your second cousin, once removed.
  25. Are you using Firefox as your browser? (Good choice. It's the only one I can give you advice for. :smileytongue: ) If so, open the "Tools" menu at the top of your Firefox screen. Then select Options >> Applications. Scroll down till you find secondlife in the left hand column. Then , in the right hand column, browse to the location where your Firestorm viewer's exe file is stored on your hard drive. (Probably in C:\Programs.) Set that as the application, and close the window. That will make it so Firefox automatically opens Firestorm whenever you click on a SLURL on a web site.
  • Create New...