Rolig Loon

It should be easy to tell whther you are wearing the object by just teleporting to another sim and seeing if the message stops. If it does, the script is in something near you, not on you. Open a beacon (CTRL + Shift + Alt + N and select "Scripts") to find it. If it's on you, though, open your inventory's Worn tab and start detaching things until it stops.

You want free lunch? The only way to get more than a trickle of L$ is to buy them. That's what most people do. At L$1,000 per $4 US, you can get a lot of Lindens for the price of a Big Mac and fries. The next best way is to earn your L$, but that takes a lot of talent, a lot of time, or both. If you are a skilled creator or performer, you can earn a few thousand L$ a day if you're lucky, but that presupposes that you are (a) skilled and (b) lucky. Meanwhile, with much less work, you can earn the same amount of money in RL and import it. Yes, I know there are games in SL you can play for cash too, but hey... you're looking at chump change. Except for a few people who have made it rich on real estate or by building another business empire, SL residents simply don't earn enough to get excited about. If you love to work in SL (I do, BTW), go for it. If you're working bcause you need the L$, though, save your time. Skip lunch in RL and upload your lunch money instead.

Innula's right. You're in the wrong forum for this. You'll need to post in Inworld Employment if you want to hire a scripter or Wanted if you want help finding something ready-made.

Well, the rotation you're using in llRezAtRoot is evidently wrong. Instead of using llGetRot(), you're going to have to multiply it by a correcting rotation. Not knowing what the geometry of your rezzer or arrow looks like, it's hard to say exactly what rotation to suggest. Try the usual suspects, though, and see what happens.. llEuler2Rot(<0.0,PI/2,0.0>) * llGetRot() or llEuler2Rot(<PI/2,0.0,0.0>) * llGetRot()

Well, you could use typed chat, the way most of us do, but I understand your frustrations at not getting voice to work. Voice has always been a bit flaky, unfortunately. Viewers play a minor part in voice functionality. 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. You can test voice by going to Voice Echo Canyon. If voice is working correctly for you, anything you say there will be echoed back to you. Of all the things listed above, the one I think is most often a cause is having Maximum Bandwidth set improperly. If it's too low, you start to get laggy. If it's too high, you lose voice and streaming media. For best performance, Maximum Bandwidth should be about 75% to 80% of your measured download bandwidth (see http://www.speedtest.net/ ).

If sculpties are not rezzing properly, there's a good possibility that your LOD factor is set too low. (Sculpties normally take up to 10 seconds or so to rez for many people, however.) You didn't say which viewer you are using, so let me give you two sets of directions to choose from. If you are using Firestorm, use the Quick Preferences button that is on your lower task bar. Click it and you should see the LOD setting. Increase it to about 3.5 if it is not already there. It's probably not a good idea to set it any higher, because that might cause other problems. If you are using a V3 viewer, you can adjust the same factor by opening your Advanced menu (CTRL + Alt + D) and then Debug Settings >> RenderVolumeLODFactor. Again, set it to about 3.5. ETA: BTW, No matter what your LOD setting is, sculpties will always rez with a lower-quality shape when they are farther away than when they are nearby. That is normal behavior, meant to save your graphics card all the work of rendering a high-quality view of something that it probably too far away to be worth it.

Die alte 1,23-Viewer ist mittlerweile veraltet, so gibt es keine Garantien, dass es weiterhin gut in SL wird. Firestorm und Phoenix sollten beide funktionieren jedoch. Es ist sehr wahrscheinlich, dass Ihr Inventar nicht fehlen überhaupt, sondern, dass Ihre lokalen Cache-Kopie Inventar beschädigt wurde. Die Lösung ist in der Regel, um die Cache-Kopie vollständig zu entfernen und lassen Sie Ihre Zuschauer bauen eine neue Kopie. Ich schlage vor, es wieder aufzubauen manuell von außen SL. Hier sind die Anweisungen (auf Englisch) >>> http://wiki.phoenixviewer.com/cache_clear

When did you try logging in most recently? Linden Lab was performing schduled rolling restarts on all main channel sims today, so each sim was off line for a certain period of time. Always check the grid status reports when you have connection issues. [Completed] Second Life Main Channel Rolling Restart [Completed 12:04pm PDT, 24 July 2012] Today’s rolling restarts have been completed. [updated 4:52am PDT, 24 July 2012] We will be beginning today’s rolling restarts on the main Second Life server channel shortly. [Posted 2:25pm PDT, 23 July 2012] We will be performing rolling restarts for regions on the main Second Life server channel. They will begin on Tuesday, July 24th at approximately 5:00AM PDT. Please refrain from rezzing no copy objects, making inworld L$ transactions and remember to save all builds.

Hej, då. If you and your wife are both connected to the Internet through the same router and modem, then I agree that it's not likely to be a problem with the Internet beyond your home. Probably not even the router, which is a common trouble spot. Your system ought to be able to handle SL well, but you may have a failing component. The GE Force 9500GS is an older card by now, but still a good one, and you have adequate memory in the CPU. I still worry about the possibility of overheating, which I mentioned in your previous thread. Because your card is now old, it may be more vulnerable to heat than it was in its younger days. When you are running SL, that card is almost certainly drawing more power and generating more heat than it does normally. Please do check that the insides of your computer are clean and that all of your fans are spinning freely. A good set of fans and a can of air are cheap investments in the life of your card.

Thread continues at http://community.secondlife.com/t5/Technical/System-details/qaq-p/1611655#M25073

Continued from http://community.secondlife.com/t5/Technical/Hej-I-have-installed-Viewer3-and-just-like-Firestorm-it-crashes/qaq-p/1610537 . Click on the Options link in the upper right corner of your question and select EDIT to add information. Please do NOT start a new thread.

Well, here are a few relevantl comments from reviews on the Internet .... "Netbooks are arguably on the way out, but as one of the last of a dying breed, the Asus Eee PC X101CH makes for a nice finale. Performance from its new Intel ‘Pine Trail’ Atom processor isn’t a huge improvement and you’re still restricted to light workloads, but the ability to finally play Full HD video smoothly makes this netbook a far more attractive proposition than many." "Integrated processor graphics card (e.g. in the Atom N2600) without dedicated memory. Most likely based on a PowerVR design similar to the GMA 500 but with higher clock rates. Only some 3D games with very low demands are playable with these cards." "65%: Such a bad rating is rare. There exist hardly any notebooks, which are rated worse." That pretty much says it all. You'll be very lucky to get this computer to run in SL at all. If you do, it will have to be on Low graphics settrings and with a V1 style viewer like Imprudence or Cool VL.

You have discovered lag, perhaps the most commonly discussed topic in SL. As Val says, it's impossible to know what's causing your lag --- there are so many possible causes -- but here's a starter list to work on >>> http://wiki.phoenixviewer.com/fs_very_laggy . Oh, and here's another one >>> https://wiki.secondlife.com/wiki/Lag . And another (I could keep at this all morning :smileytongue: ) >>> http://community.secondlife.com/t5/English-Knowledge-Base/How-to-improve-Viewer-performance/ta-p/1316923 . BTW, a wireless connection is NOT an excellent way to connect to SL. In fact, it's one of the leading causes for poor performance. Wireless was never built to handle the heavy back-and-forth continuous data traffic that SL depends on, and it is vulnerable to all sorts of interference. Switch to a cable connection if you can.

Yay Alisha! Thanks for posting your success and for adding it to https://jira.secondlife.com/browse/VWR-29307 so that other people can benefit. :smileywink:

You can use Puppeteer or similar software to animate the body's limbs, but you still need a script to move it from one place to another. That's the hard part.

You need to write a script, as I described in my earlier posts. The mesh model is a potentially moveable object, but without a script it's a lawn ornament.

Yup. Yesterday was a soft brain day here. :smileyembarrassed:

Wow....... necropost........ :smileyhappy:

Error message? Nope. It works great for me. I'm on Firefox. The only time I ever look at the web profiles is when someone here asks about them, and they always seem to be there.

In addition to the excellent suggestions already in this thread, consider the possibility that your computer is filthy inside. Dust can create a serious overheating problem for a computer that is already using a lot of power for high-level graphics. Your computer's defense is to shut down the application when the temperature gets too high --- often after 3 or 4 minutes. If you keep using it without cleaning out the dust bunnies and cat hair, it will eventually burn out. You can stretch its lifetime by using viewers like Phoenix, Imprudence, Cool VL, and Singularity that don't put such heavy demands on your graphics card as Firestorm and V3, but it's smarter to just open the case once a month and blow it out with a can of air.

You're there, honest >>> https://my.secondlife.com/miles1 . I just looked. If you are having trouble getting there, try changing your web browser. SL doesn't get along well with IE, so try Firefox or Chrome.

Patrick032986 wrote: I just come to realize that they have a serious bug retaining to firestorm being unreadable for the special characters in the display name or I was told now that makes me wonder how that can be possible cause I had a problem with everything not being clickable in my firestorm when I woke up a few mins ago. Are you talking about https://jira.secondlife.com/browse/SVC-6608 ? That's a server bug that affects all viewers. It's not Display Names, but group names. If you put illegal characters in them, you get locked out of SL for a very long time.

When you end up sitting wonky, it's generally because a sit target has been screwed up. That's not likely to happen spontaneously, but it could happen if you added a new script that also has a defined sit target in it. The script that was most recently reset would impose its sit target on the object, overriding whatever was there before. I can imagine another possibility as well. Unless the mesh chair is a single prim, it's possible that you have either (1) a second script with a sit target in one of the child prims or (2) a link sit target defined in your main script. If either of those is true, you might end up sitting on one sit target if you click the root prim and a very different one if you click on another part of the chair. And yet one more, final possibility. Not all animations are oriented the same way. If you have a script that works perfectly well for one animation and then you replace it with an animation that expects to be sideways, you'll sit sideways. This one drives scripters nuts when they are writing scripts for objects that have a stack of animations in them. They have to change the sit target each time the user selects a different animation from the menu. If a user comes along later and yanks out one or more of the animations to replace them with her own, the whole system can get screwed up, so none of the animations sit right. At one time or another, I have made each of those mistakes, so I can report with mild embarrassment that they do happen.

Hehe ... That's what I just did, by example. PERMISSION_CONTROL_CAMERA | PERMISSION_TRIGGER_ANIMATION is a boolean combination of 0x800 and 0x10. That is, the bits in the two are combined to make 1000 0000 0000 OR 0000 0001 0000 = 1000 0001 0000 The composite has "1"s in the places where they occured in either 0x800 OR 0x10 and "0"s everywhere else. That's like cutting a mask out of a piece of paper. It has solid parts (the "1"s) and holes (the "0"s). If you compare it with something else that also has solid parts and holes, the two will only line up if the solid parts and the holes are in the same places. That's what testing the match with & is doing. EDIT: Ack .. typed too fast and didn't look at the numbers I was typing... :smileyembarrassed:

Yes, and in that context the parameter is yet another beast .... a flag that is being used as part of a mask. Each of those flags has a binary value. You can combine several of them with the boolean OR operation, so that they act as a composite. If you are requesting permissions in a script, for example, you can write llRequestPermissions(My_av's_UUID, PERMISSION_CONTROL_CAMERA | PERMISSION_TRIGGER_ANIMATION); Those two permission flags have been combined into a single composite mask by the OR ( the "|") between them. When you encounter them again in the run_time_permissions event, the script can check to see whether either of the two has been met by asking if the composite mask AND ("&") the detected permissions granted have the same bits set. run_time_permissions (integer perm){ if (perm & (PERMISSION_CONTROL_CAMERA | PERMISSION_TRIGGER_ANIMATION) ) { // Do something }}