Gryphon Ronas

For sure, a good cleanup now and then makes everything so much better. You mentioned faulty connections - I think sometimes we forget just how many connections there are between us and the LL servers. Grab the IP address of your sim some time and run a quick traceip on it. That will show how many times each packet gets handed off between you and LL. One night my ping time to the sim was running about 115, I was like wth? Then I checked and found that for some reason, my ISP (or someone above them) was rerouting traffic - I had 37 handoffs between me and LL. OK, so I guess that nasty ol' 115ms wasn't so bad after all. So basically - unless everyone in the sim is having issues, don't look to LL for the problem. Look closer to hom. A lot closer...

When you install the viewer, if your graphics card can do shadows, but it is likely to put the frame rate below 10, then shadows will be off by default. But since your rig can understand the instructions, it will be possible for you to override the settings and turn it on. It goes back to the old saying tho - just because you can, doesn't mean you should. ;-) My FPS goes from 25-30 down to around 10-12 when I enable shadows. That kind of a drop insn't unexpected - real time dynamic lighting is a massive load on teh GPU. My ATI Radeon HD 4600 Series does a decent job - but there are definitley cards that will do better.

I used to crash 25-30 times a day if I was on all day. Anything might trigger it. If I stay in one place too long, if I move around too fast, if I did the unthinkable and actually tried to cam on something. It was bad. IM's crashed me, opening a group chat sent me to the desktop. I tried different viewers. It would get better for a day or so. Not good, but better. I tried every PC tune-up and registry trick in the book. So one day a couple months ago, I carefully backed up everything on my computer that mattered to me and I restored it to factory default. I still crash. But where it used to be on the average of every 20-30 minutes, it's more like once every few hundred hours of use. I had been downgrading graphics a bit at a time till I was nearly at basic. Now I run around with full shadows and everything. The lesson learned was, it wasn't LL that sucked - it was my computer. Maybe we shouldn't be so quick to jump to conclusions. If you think you have tried everything, and it still just won't run - assuming you are running hardware that actually can run it - maybe the problem isn't where you think it is? Might be worth a try. Worst case - you have a clean operating system again.

If you had additional presets that you added manually, and you uninstalled (or maybe it was automatic?) they might get zapped. You can add them back manually again and they will be there waiting for you on the next login. It does look as if maybe they cleaned up the list a bit - trimmed the fat so to speak, because there don't seem to be as many as there once were.

The layout isn't bad now that I found I could disable the wanna-be Facebook crap. Pity I can only get rid of it on my own tho. I'd love it if I had the option to never see it when I am browsing profiles as well.

The money isn't really gone. Just click your balance to force up date it.

Just tried this crap out before disabling it. Wow, once someone leaves a comment, it's there forever? Don't see a way to edit it. Leave it to LL to give the griefers a new toy. Great thinking guys.

OK, I think you are asking why you can see the effects of windlight on the vendor pics, even though you do not have those setting in use? The reason for that is, windlight controls how light is handled when the scene is rendered. When you look at a pic in world, be it on a vendor or a snapshot, you are not rendering the scene in the pic. You are basically looking at a partial screen capture that shows what the person was seeing at the moment that they took the picture. When it becomes a pic, not a rendered scene, we all see it pretty much the same. Which begs the question of vendors with overlit blown out messes passing for product shots - but that's another topic. If you have to run with shaders turned off, it's probably not worthwhile to put a ton of effort into windlight, since one of the primary things it does is handle how the Atmospheric Shaders work. Where windlight really shines is when you are running full graphics - shadows. You can tailor the amount of ambient light to give the shadows the right level of contrast as rendered by your video card and shown on your monitor. A given setting will not necessarily look the same for everyone since we have so many different types of hardware.

Nope - Not what I'm referring to at all. And I do have all maturity levels enabled anyway. What I am referring to is what somene at LL considers "Home" in a profile. One would think it would be the person's profile, but no... Clicking the home button from anywhere in the profile takes you to the Feeds tab, not the About tab, which is actually the profile.

Not sure if this change was across the board or what, but today I log in and hit a profile and I see something unrecognizable. It's what's left of resident profiles. I thought the general idea was to make SL 'fast, easy, and fun' and that the emphasis was supposed to be on retention? If so, then why in the world did someone think it was a good idea to make it so that the first thing you see when you open a profile is crap from other sites? I'm fine with changing the layout and all that, I really am. But when I open a profile, I want to see that person's profile... Their SECOND LIFE profile. To me, having the 'Home' page of a profile be all about other services is downright stupid. Another case of LL being out of touch with the user base. The vast and overwhelming majority of the people on SL do not link it to other social sites, so when we open their profiles, we see a blank page. Why do they feel the need to keep trying to cram this down our throats? I wonder - do Twitter and Facebook promote SL as heavily? If anyone could give me one reason why it's better to open the profile of a person who may be causing trouble, and get presented with the blank page instead of their profile - I'd love to hear it.

Has anyone told you yet today that you totally ROCK!? I stared at that for so long trying to see what made it go back.... THANK YOU! I was looking for something like a return, or a loop back kind of thing. I see now that the code executes once, and then stops and waits at the end, and the next touch starts it over again, but this time the varialbe has been changed so it does the opposite. I tested that out and the light goes on and off as it should, perfectly. What happens though if I need to add to it - like fullbright isn't enough? I guess what I am asking is, is there any way to define a set of parameters for 'lightoff'? Local lights are making it hard to tell from fullbright alone if it's lit or not. Here's what I tried: llSetLinkPrimitiveParams( 1, [ PRIM_GLOW, ALL_SIDES, 0.25, PRIM_FULLBRIGHT, ALL_SIDES, lighton ] ); That turned on the glow, but the !lighton can only work with TRUE or FALSE, and glow of course is different. Next I tried adding into the beginning: integer lightoff = 0;default { state_entry() { offset *= ((1.0 - min) / ns) * (offset * llGetScale()); hi_end_fixed -= 0.5; llSetLinkPrimitiveParams( 1, [ PRIM_GLOW, ALL_SIDES, 0.25, PRIM_FULLBRIGHT, ALL_SIDES, lighton ] ); llSetLinkPrimitiveParams( 1, [ PRIM_GLOW, ALL_SIDES, 0.00, PRIM_FULLBRIGHT, FALSE, lightoff ] ); } When I did that, I didn't get the glow to go off when I tried to use !lightoff, which I thought would change lightoff to 1 and set those parameters. Is this something I can define in the scope? LIke a set of parameters that tells it if lighton = 1 then glow = .25 else glow = 0.0 That kinda thing? I guess I didn't take into account the lighting in the area where this is used. It messes everything up.

Just looked back and I see I replied to the wrong person when I posted the code. Sorry - 4am will do that to ya. ;-) Also - I had wondered about a reset at the end of each event, but that won't work. No only would it turn the light on all the time, but when you resize the curtain, you stretch it then reset the script. That gives it a new value for its 'closed' size.

vector offset = <1,0,0>; //Prim moves/changes size along this local coordinatefloat hi_end_fixed = FALSE; //Which end of the prim should remain in place when size changes? //The one with the higher (local) coordinate? float min = 0.4; //The minimum size of the prim relative to its maximum sizeinteger ns = 10; //Number of distinct steps for move/size changedefault { state_entry() { offset *= ((1.0 - min) / ns) * (offset * llGetScale()); hi_end_fixed -= 0.5; llSetLinkPrimitiveParams( 1, [ PRIM_FULLBRIGHT, ALL_SIDES, TRUE ] ); } touch_start(integer detected) { integer i; llSetLinkPrimitiveParams( 1, [ PRIM_FULLBRIGHT, ALL_SIDES, FALSE ] ); do llSetPrimitiveParams([PRIM_SIZE, llGetScale() - offset, PRIM_POSITION, llGetLocalPos() + ((hi_end_fixed * offset) * llGetLocalRot())]); while ((++i) < ns); offset = - offset; }} You can see the 2 lines I added - and yeah - I dind't realize there was an "Insert Code" button..... duh. lol

Thanks. I tried copying those in, but dind't get the light response. I have managed to get the default state working using: llSetLinkPrimitiveParams( 1, [ PRIM_FULLBRIGHT, ALL_SIDES, TRUE ] ); The default state on teh curtain is closed, so the light on is correct. I also put it in right after the touch event starts, but with glow set to FALSE. It turns the light off as you open the curtain. Again - just what I want. The problem is, it never comes on agaion when you close the curtain again. The curtain doesn't move, it resizes from one end. I think I can see how it doies that, but how it goes back to a closed state is a mystery to me. If I could figure that out, maybe I could guess where to put the line to turn the light back on. The curtain can't be the root prim because if it is, when it closes.opens, it moves the other prim with it. So I seem to be a bit stuck there with that. I tried to post the code here, but it's s jumbled mess when I paste it. (It's an open source script, so it would have been OK to post) This is driving me nuts. I finally got a handle on how to set the params of the prim fromm touching the other prim.... Now I can't make it do it more than once. I really do appreciate all the help from everyone though. :-)

Tried looking up the first two suggestions, and I obviously don't know enough for the wiki to amke any sense. By trying the 'stick it in wherever it will take it' method, I was able to put the set primitive params and LINK_ROOT one in the curtain, and I was able to trigger the root prim. But the curtain no longer works. Maybe I don't need a light on there as bad as I thought I did. It may not be impossible to do for some - but for some of us, I guess it is. Thanks for the help guys. :-)

Looking those up now - Thank you. The biggest problem in searching for something like this seems to be you kinda have to know what to search for. Without the right terms to look up, a lot of time gets wasted. Thanks again for the quick response!!!

I thought this would be a simple thing. Two days of Googling and being baffled, asking in groups and getting answers that don't work... OK, so maybe it isn't simple. The items (including their scripts) are modifiable, so I can change whatever I need to - if I can grasp how to. I have a light that goes fullbright and glows slightly when touched. I have a curtain that opens and closes by resizing on touch. All I want to do is link them either to each other, or to a separate root prim, like a button. Click the button, the curtain closes and the light goes on. (Think of something like a voting booth) If one of the two has to be the root, that's fine too. Actually, preferable - I would rather touch the curtain prim and have it close and trigger the other script (make the light glow). Is there any way to do this? I have been told I can do it with listeners, but I have heard so many times that isn't a good idea. Any help is greatly appreciated! Thanks!