Jump to content

Rolig Loon

Resident
  • Posts

    46,473
  • Joined

  • Days Won

    5

Everything posted by Rolig Loon

  1. This forum is a place for people to learn how to script in LSL, and to share scripting insights. The place to post a request for someone else to write a script for you is the Wanted forum. Since you came here asking for help in modifying your script, let me recap the help you have received so far: The script consists of one state, with one event that contains only one command, and it works. You were handed the exact form (in fact, the exact wording) of the command that you need to make the script do what you want. You were given a very direct "hint" about exactly where to put the command. So, you have all the pieces that you need. Your experiments to make the script do what you wanted have been successful so far, so be confident. You can do this.
  2. You may find that the bake fail problem comes back repeatedly, or isn't solved at all, even after you fix it with one of the suggestions at http://wiki.phoenixviewer.com/fs_bake_fail. 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. Then plug it back in and let it get a fresh hold on an IP address. If those simple measures don't work, start with the diagnostic steps that Nalates suggests in her blog at http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/
  3. Generally, no. To quote LL directly ( http://community.secondlife.com/t5/English-Knowledge-Base/Billing/ta-p/700037#Section_.7.2 ) ..... Issues with prepaid and gift cards A common cause of payment method failure is the use of unsupported card types. At this time, the majority of prepaid cards are not compatible with our system, even if they bear the VISA/AMEX/Mastercard logo. This includes cards purchased at retail stores, rechargeable credit cards, and bank-issued check cards.
  4. It sounds as if you have a severe Internet connection issue. Your invenory is actually on Linden Lab's asset servers, or should be, but your own computer is not staying connected properly, so the locally cached copy of your inventory is incomplete. That means you can't reach what's on the servers. I suggest doing a very careful reading of Nalates's blog >>> http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/ , paying particular attention to your packet loss and ping sim diagnostics. If either of those numbers is out of line, you will be losing random pieces of data. One simple piece of advice first : If you have been on wireless, get off of it now. Wireless can be a major source of connection issues for SL residents, so use a direct cable instead.
  5. That's a truly sad and frustrating tale, Amza. I'll have to remember to add it to my growing list of good reasons not to use voice (I never have). This abuser is conducting a strategy of intimidation. If your husband had actually done anything to get him banned from SL, the abuser would have long since reported it. He obviously does not have any evidence at all, so his strategy has been to tgry and discredit your husband with his friends. Like your husband, I prefer to simpy ignore idiots and walk away, but that may not be the best idea here -- especially if his friends seem to believe the abuser. Your husband can certainly file an AR. In fact, he should have been filing them all along. Voice, unfortunately, leaves no record at all in the servers, but chat logs do. While it is true that the other person can edit chat logs, LL has the unedited ones in their servers -- at least until they are overwritten -- so they can always see what was really said. I suggest that whenever your husband gets an abusive chat message, he should file a new AR, referencing all previous ones.
  6. @ outtaspace: Yeah, that section of the TOS you quoted is just LL's own indemnification clause. All it's saying is that THEY are not responsible if someone else violates your privacy. It's not saying that they give other people the right to do it. The thing that got RedZone and Emerald in big time trouble was connecting bits of information (avatar name and IP address -- and thus, potentially, RL identity) and making it public. That's a violation of the bit that I quoted earlier, so that's what you have to watch out for. Personally, I value my own privacy so highly that I am very cautious about asking anyone else about theirs, so I avoid even coming close to that line. I don't ask who anyone I meet in SL might be in RL, and I don't care. But that's just me. Again, though, I think that asking people to register voluntarily to participate in a service is fine, so the direction that Darkie and others are suggesting here ought to be no problem.
  7. outtaspace wrote: Darkie, why do you say it would be against TOS to collect username on an external website? I think Darkie is referring to the notorious IP snooping violations a little over a year ago that resulted in a widely publicized banning of RedZone and the guy responsible --- or maybe to the equally notorious case of the Emerald viewer, which was banned a year before that. The relevant portion of the Community Standards (referenced un the TOS) says "Residents are entitled to a reasonable level of privacy with regard to their Second Life experience. Sharing personal information about your fellow Residents without their consent -- including gender, religion, age, marital status, race, sexual preference, alternate account names, and real-world location beyond what is provided by them in their Resident profile -- is not allowed." It's one thing to ask people to sign up for membership in a group and ask them to give information voluntarily. It's something entirely different to scrape it from their login without their knowledge. I'm NOT saying that's what the OP is doing. I'm just answering your question about where the pitfalls may lie.
  8. I wish I did, Peter. I watch the questions here and read the chatter in the Merchants forum. From those I can report my anecdotal impression that there are more4 failed deliveries recently than in the past. My own experience remains the same, however. In over five years, I have never failed to receive anything that I bought in Marketplace (or its predecessors), and I have never had a failed delivery to any of my customers. I have probably tempted the gods by saying that now --- or maybe I''m the typical one and we're just hearing from the minority of loud failures.
  9. Of course you can. That's just the starter kit. Nobody but newbies stay with that. You can buy avatars from creators who have made them and sell them either in world or on Marketplace. Or you can start with one of the standard models and modify it with your Appearance sliders. (See http://community.secondlife.com/t5/English-Knowledge-Base/Controlling-your-avatar-s-appearance/ta-p/700709) OR.... if you are skilled anough, you can create your own totally from scratch if you know how to create mesh. (See http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185 ). BTW, this is not a game. It's Second Life. Welcome aboard.
  10. If you have made a valiant effort to contact the merchant and have had no luck, your only other option is to file a support ticket at https://support.secondlife.com/create-case/ . Choose Marketplace >> Failed Marketplace Delivery from the pulldown menus. Linden Lab has been getting a lot of those recently, and AFAIK they have been responding fairly quickly.
  11. If his IMs are capped, so are notecards, group messages, group invitations, and any items he is sent. The cap applies to all of those.
  12. Voltaire is usually right (or at least Candide, speaking for Voltaire). I apologize for seeming to throw a rock at you, Peter. I was feeling snippy, but that's a poor excuse. I'm not too sure that turning the scripts on and off is any easier than making each of them a separate state in a new script. Either way, you need to write a control code. Having the control in state default and each of the other functions in a separate state in the same script feels to me like simplicity itself. And it saves having three scripts to do the work of one. Because the OP apparently has the two scripts already written, popping them into a composite script should be a snap. In any case, this is exactly the sort of debate we need in this forum. If the OP doesn't learn anything else from watching this, he should at least see that (1) there's usually more than one way to approach any interesting scripting problem and (2) choosing one can often come down to personal preference.
  13. You don't need to look at script state in your second script at all. You're turning it on and off with the main script. Not only that, but the test that says if (llGetScriptState(llGetScriptName() == TRUE) is pointless. If the script isn't running, it can't test itself, and if it is, then that's obvious. What your second script needs is 1. a llListen handle so that it can actually listen on channel -2345 2. A test to check when some kind of triggering message arrives from the main script (Oh, and you need to send that message from the main script....) 3. A set of actions to take place when someone clicks on a dialog button. Frankly, though, as much as I applaud Peter for coming up with this suggestion, IMO it is by far the clumsiest way to solve your problem (Sorry, Peter..... :smileysad: ). Innula's approach, combining the texturing script and the resizer into a single script, is easier to write, kinder to sim resources, and less likely to screw up in operation. If it helps to think of the two purposes (texturing and resizing) in separate states, do it that way and put the dialog that choses between them in state default.
  14. You rarely need to understand quaternions to handle rotations in LSL. That's why we have the handy functions llEuler2Rot and llRot2Euler. Those functions let you translate between quaternions (rotations) and vectors, saving you most of the trouble of figuring it out yourself. So, to rotate 10 degrees around the object's X axis, you can write llSetRot(llEuler2Rot( <10.0,0.0,0.0>*DEG_TO_RAD) * llGetRot() ); without ever having to write it as a quaternion. See http://wiki.secondlife.com/wiki/Rotation and http://wiki.secondlife.com/wiki/User:Void_Singer/Rotations for good, careful discussions of how rotations work.
  15. There are a limited number of possible places, so I suggest doing a little experiment to find out. (HINT: You probably don't want to delete the script until after it says its message.)
  16. Rolig Loon

    thanks

    Hmmmm.... That didn't help. My guess is that you are typing in Chinese or Korean and it's not copying well into this forum software.
  17. You might consider changing DNS servers too. Change your default DNS settings from whatever your ISP assigns you as a default by adding Google's free public DNS servers. Here's how >>> http://code.google.com/speed/public-dns/
  18. As far as I can tell, "good" and "simple" don't belong in the same sentence when you are talking about modelling or texturing software. It's worth your time to work through all of the Blender tutorials on line --- even the ones that seem irrelevant. The more practice you get, the more it will make sense.
  19. Neither one looks free to me, and the word "Free" doesn't appear in the ads. The Marketplace page for each item lists its price clearly as L$99, and that's what you were charged. It looks like they were delivered too. Because they were sold with copy perms, it's unlikely that the merchant will agree to refund your L$.
  20. The bulk of voice support is given by the external application called SLVoice, which is made by the SL voice provider, Vivox. Voice failures are almost always due to one of the following reasons: Your ISP is throttling or blocking the voice service; failure of the Vivox service; voice issues on the region you are on; voice being throttled by bandwidth set incorrectly - please check it by following the instructions here; voice hardware (mic, headset) not configured correctly in your operating system settings; voice hardware not configured correctly in the viewer; another application has your voice hardware in use (example, Skype); your anti virus software has “mangled” the voice application; see here. For more extended suggestions, try http://wiki.phoenixviewer.com/fs_voice
  21. The "something" message is probably telling you that your computer can't find the host -- in this case SL's servers. Your viewer and SL's servers have temporarily lost the ability to talk to each other. Unless there's a problem with the servers (Always check http://status.secondlifegrid.net/ first), it's probably something on your end. So.... (1) Try shutting off your computer, unplugging the router and modem for a couple of minutes, and then plugging them back in and restarting. That simple step may clear up everything (2) Change your DNS settings from whatever your ISP assigns you as a default. Use Google's free public DNS servers instead. Here's how >>> http://code.google.com/speed/public-dns/ (3) If things are STILL messed up, contact your ISP. Maybe they are working on their Internet connections. Mine go down for about 20 minutes once a month or so while they are vacuuming dust out of their servers, or whatever they do.
  22. There is a lot to read, but I think you will find many helpful suggestions here >>> http://wiki.secondlife.com/wiki/Lost_inventory . However, if you have been gone for a year, it may not be easy to recover items that have been missing for a long time.
  23. If you can't set the scripts to Not Running, then take Innula's advice and try just ripping them out of the sofa completely.
  24. You could use something like this .... http1 = llHTTPRequest(URL + "&name=" + avname ,[HTTP_METHOD, "POST"],""); // Send the data string to URL where name is a variable that the script in your external server expects to see, and avname is the value you are passing.
×
×
  • Create New...