You know what's NOT helpful in a technical issues thread?

Saying you DON'T have the problem mentioned in the thread. People who interrupt technical issue threads only to say, "Well, gee, I don't have that problem," are hijacking the thread with useless info.

Those of us WITH the problem the thread is about DO NOT CARE that you don't have the problem. We want to communicate with PEOPLE WHO DO have the problem so we can find common issues.

Hmmm. My forums don't seem to have posts like that. :::hrug::::

The sorts of posts you mention have never troubled me.

However, having Kendra beat me to the "Submit Reply" button by seconds really irks me.

Huh. Interesting. I always seem to post at the exact same time as Kendra. ::hrug::::

Just saying "I never noticed that." is unhelpful, I will agree.

But saying "I tried to replicate that glitch, using this hardware and OS version, and these steps, and it didn't happen for me." Is entirely different. Knowing someone else has seriously tried to replicate a bug, and has failed to do so, is a very valuable bit of diagnostic information. Especially if they indicate they are using a setup similar to your own.

Agreed, but I didn't say someone trying to recreate a bug wasn't helpful. I said those people who chime in, in post after post, with "that doesn't happen to me, must be how you have your computer set up" do nothing to help.

It doesn't bother me when people say this. I just figure they are bragging about their systems like anyone really cares.

Saying someone doesn't have the problem informs you that it is possible that the problem occurs because of your environment or at least there is a trigger to happen.

TRUE... but I'm specifically talking about the people who say NOTHING other then "I'm not having that problem, it must be you," when, in fact the fault is in the client.

Example: A acouple of months ago there was a bug where users would experience a massive slowdown in the client whenever they opened the Find window. The threads went on for weeks with no response from LL. FINALLY the bug was acknowledged in the upcoming patch notes, and LL said that the bug appeared on slower systems. MANY people quickly jumped on that and pointed out that the bug was not just on "slow" systems but decked-out gaming rigs as well. Not everyone was experiencing the bug, so it took people who were actually experiencing the bug on all types of systems to report it. ALL the people in those threads that said, "Not happening to me," did not help LL at ALL. The only responses that helped LL were the ones from users experiecing the bug because it was those people who showed LL that the bug was a problem with the client and had nothing to do with anyone's system.

I have a gaming rig. Every part in it is built for speed, from the motherboard to the RAM, to the power supply and cooling system. I've been building computers for more than 15 years and I know them inside and out. When Second Life works for me on Monday, there's a client update on Tuesday and on Tuesday Second Life now runs like crap for me -- it's not my system. It's the client. Something changed with the way the client communicates with my system or some part of it.

Heh, I guess you don't want me to tell you I'm not seeing any unusual problems and I got about a 3 fps boost in speed from the last update then. In my opinion, data is data and the more data you have the better decisions you can make. Desisions made on "OMG OMG! SL is the brokken, Fix dis shit now!!!" probably won't be the best ones.

Well, I have found something interesting with this upgrade.

I tend to frequent two sims, Umber, my home sim, and also Takes where I used to own land.

Up until the upgrade before last, I was getting pretty bad performance all over sl. But for some reason with that particular upgrade, my performance in Umber improved dramatically. In fact so good was it, that I was able to implement local lighting, with draw distance set at 128, which was great.

Unfortunately Takes was just as bad as normal, and when I went there I suffered from freezing and low (sub 5) frame rates.

I found, with the latest upgrade, that Umber has slowed right down. I've had to uncheck local lighting and reduce my draw distance to get reasonable (round about 10) frame rates. However, when I visited Takes last night, I found it was running very much faster.

Are servers swapped around when an upgrade is carried out? I can't see any other reason why this should happen.

The only other possibility I can think of at the moment--is Local Lighting itself--which I've found to be terribly polar and horribly temperamental, depending on light sources nearby, not-so-nearby, and possibly other factors. I remember coming back to an area which had been smooth for me earlier--and I enjoy Local Lighting very much--and my framerate crawled into the sub-single digits. I soon found out someone left a stack of light cubes under a set of floorboards, but it took me a long time to find that out.

Wish there was an easier "Local Lighting meter" to show how much load light objects are having on your performance--but in the meantime, I use FAST TIMERS under DEBUG. That can help nail things (some words in the legend on the left are quite obvious, some not so much), altho as I understand it, the technical terms change fairly frequently and being a debug feature, it's raw and documentation is time-consuming to do. Still useful info to have, however. I feel FAST TIMERS is underrated. ^_^

local lighting seems to work perfectly well for me at night. Unfortunately during the daylight periods local lighting grinds my machine to a halt. I may have 30 frames per second at night with beautiful lighting affects but local lighting during daylight periods can cause my machine to run at between one and five frames per second. Seems to me local lighting is being left on during daylight periods when it should not be. This may be the root cause of why a local lighting is such a problem for most computers.

Ok, thanks for that, Torley. Nothing changed in Umber between the fast - preupdate- running and the slow - postupdate. But I will have a look at FAST TIMERS in the hope that it might mean something to me.

When Umber was running well with local lighting switched on, I have to say that I noticed no difference in framerate between day and night.

Anyway, I shouldn't have mentioned local lighting in the posting, because it seems to have confused people.

The basic isssue is that before the update Umber was very fast and Takes was slow.
After the update, Umber is slow and Takes is fast.

I don't have a problem with these kind of posts.

Pictures of optical illusions like the one below don't help much either.

now i feel like I have technical issues with my eyes