leliel Mirihi

You don't need Ultra enabled to turn on Lighting and Shadows, just Hardware skinning. FBO is automatically enabled when selecting Lighting and Shadows (on the mesh viewer). You can actually disable everything but Basic Shaders and Hardware skinning with Lighting and Shadows still enabled. Altho last I checked the Bump mapping and Shiny option didn't work with it enabled, the Local Lights option probably doesn't either. Kind of pointless tho, if your GPU is fast enough for shadows there's no reason to disable Atmospheric shaders or Water Reflections.

Atilla Thei wrote: [...] and for that I can't find people with your search engine unless I'm using Phoenix/Emerald/etc. Please upload a video to youtube of you trying and failing to search for some one using viewer 2. Other wise I'll just assume you're lying. I could understand, and believe, if you had said you have trouble searching for stores on v2. But it's kind of hard to not think you are spreading FUD when you say that typing 'leliel Mirihi' into search on v2 doesn't come up with my profile.

I love how the two people who gave the wrong answer got kudos. Nyll Bergbahn's post is the correct answer for viewer 2.5.2.

SL time is just Pacific time. Last Sunday we switched from Pacific standard time to Pacific daylight time.

It's a bug. VWR-20185

You aren't paying for the account so why bother deleting it? Besides you've only been here for a day, I don't think that's long enough to have made up your mind already.

Maddox Prefect wrote: Does anyone know what might have changed with the new viewer that might be causing this problem? I tried going back to the 2.3 viewer but the login server is insisting that I use 2.5. STORM-809

The, now 3.5 years old, 9800GT is a waste of money on something as ancient as a Pentium 4.

Congratulations, you have the infamous and rather worthless GMA 900. This chip is so slow that honestly I'd recommend you don't even bother looking for drivers and just buy a used $10 graphics card which will be about 100 times faster. Yes, I am being serious.

You're getting such low frame rates because you're using an 8 year old low end graphics chip. It's time to upgrade.

It’s also important to note that we are going to remove the “voting” feature in JIRA in one month. Today, we do not use voting to triage or to make product decisions and the last thing that we want to do is set false expectations. So, when you are interested in what action we will take on a particular JIRA, use the JIRA “Watch” feature so that you will be immediately updated in email when there are new comments on that particular JIRA issue. We will continue to use the number of Watchers as an indication of the level of interest. I'm very sad to hear this. Just because I'm interested in something doesn't mean I want to follow the discussion or get emails about it. Especially with the issues that degenerate into flame wars with lengthy diatribe posts (e.g. VWR-24746)

LL already has done something about it. They updated the back end servers and fixed the name cache in viewer 2.5.

It was renamed to CameraOffsetRearView.

Just drop this script and an animation in a prim and wear it. default { attach(key id) { if (id != NULL_KEY) { llRequestPermissions(llGetOwner(), PERMISSION_TRIGGER_ANIMATION); } } run_time_permissions(integer perm) { if (perm & PERMISSION_TRIGGER_ANIMATION) { llStartAnimation(llGetInventoryName(INVENTORY_ANIMATION, 0)); } } }

Nyll Bergbahn wrote: I've never seen textures exceed available texture memory before as shown in your GLTot and Memory Bound figures so I really don't know what's going on. Hope someone else can comment on that. This can happen when the draw distance is too high, or when a large number of objects suddenly come into view when the pipeline is already using most of the memory. It is most likely the cause of the sudden drop in FPS as the viewer would be desperately trying to free up resources since you'd be spilling over into system ram. This theory is supported by the fact that frame rates actually improved when the texture memory slider was lowered to 64MB because when you go over the limit it would still be in vram. Since Zuriel is already running the graphics at low with the draw distance at 64m on a card that a few years ago could run on mid with windlight enabled I'd say it's time to upgrade. 128MB of vram is just not enough for sl these days when many sims are pushing 350MB+ worth of textures and avatars are hitting 20MB each.

CTS-284

To be honest I think you should buy a new machine. Even a $400 laptop would out perform what you have now. And as I said above, LL will be dropping support for your CPU in a few months.

Nyll Bergbahn wrote: Could you please clarify what graphics card you have. I never heard of a Radeon 7700 so I checked Google and it can't find one either. There is a Radeon 7500, Radeon 7000 or FireGL V7700. All are very old apart from the V7700 and if your card is a V7700, note SL does not support FireGL cards as performance is uncertain. Open SL to login screen > select Help > About Second Life and copy/paste the computer details into a reply here. Given the age of his CPU I think he most likely has a Radeon 9700 and just miss typed the number. On the subject of VBO, I ran some tests a couple of days ago in a Linden water sim and disabling this in Preferences actually reduced FPS by around 3 FPS. I re-ran the tests this morning in the exact same sim and disabling VBO resulted in an increase of 20 FPS. Teleporting to an infohub reversed that effect with VBO enabled giving an increase of 10 FPS but 15 minutes, the same setting showed a reduction of 5 FPS. The results are so unpredictable, it's difficult to make any recommendations one way or the other on VBO. I'll do some more tests over the next few weeks. I have a Radeon HD 5850. I used to disable VBO on an old ATI card I once had because that was the recommended solution for the onscreen artifacts created when enabled. Can't recall what enabling or disabling VBO did for FPS if anything at the time. This I find very weird. VBO should be giving you a rather large boost in FPS since the render pipeline no longer has to upload geometry data to the GPU every frame. This makes me very curious to know what the viewer is doing that cause ATI cards to barf when Nvidia cards don't seem to have a problem with it. The AMD 3200+ was released in 2003 so is probably struggling with Second Life which is very CPU intensive. And LL will be dropping support for this CPU when mesh rolls out.

Just shift or control click on the items, right click -> share and it will open up a people choser where you can select the people then hit share and you're done. The same thing works for teleporting multiple people.

Alexios Donardson wrote: /me thinks, i wanted to ignore him/her, but i had a second thought. Sorry for hijacking your thread, but v1 lovers never seem to answer these questions.

Cerise Sorbet wrote: Multiple open profiles will be returning to viewer 2.x, and when they do return it will be one of the changes that breaks 1.23. I know there are coming back, my point was that very few people open multiple profiles just because. Almost all the reasons people would do it were because of v1's poor UI. Who in their right mind would think dragging and dropping items one at a time on to a little box in a dozen profiles is a good idea? Not that it matters tho, v2 already has alternatives for the two main uses of multiple profile floaters.

Ceera.Murakami wrote: 2.x still takes more mouse clicks and time to do common tasks, and still makes things like looking at multiple profiles at once completely impossible. Do you just like looking at several profiles at once for fun, or is it that you are trying to do something and v1 forced you to open multiple profiles to do it? And yes I can guess what it is you want to do, I'm just trying to start a discussion about what it is you really want. I'm tired of hearing people say they can't do X in v2 when really they want to do Y. Such as building, the build floater is 99% identical between v1 & v2. What people really mean is the camera controls are bad in v2, or changing permissions on items is hard in v2, and so on. None of which has anything to do with building proper. So what is it that you really want? /me expects to be ignored

@ Winter.Ventura Develop -> UI -> Double-Click Teleport