Second Life™ users have been seeing textures load in blurry and progress toward a new crisp image. That is where things are supposed to stop. But, quit often people are seeing them repeatedly load blurry and re-render to a nice crisp image and then repeat and repeat and repeat…
The video card for some reason is discarding the texture already in memory, and redoing it. Some think the video cache is more than full and just cycling through textures in your field of view.
There are HUD’s that which are known to cause the problem. So, if you are seeing the problem, remove you HUD’s and relog. Then watch to see if it happens again. If not add your HUD’s back 1 by 1. You’ll figure out which HUD triggers the problem, or possibly the sum of a set of HUD’s triggers the problem.
There are a couple of HUD’s reported to always cause the problem. But, I can’t confirm that. So, ratting them out would be unjust.
The textures in a region likely contribute to the problem too. So, do your HUD testing in an empty region.
Over on SLUniverse there is a post telling how to solve the problem with some video cards running in a Mac OS. (Post)
The reason it’s probably worse with the LL viewer is because they set the texture memory multiple to 0.5 by default for Mac which means if you have a 256 card like in your case it will lock the [Preferences-Graphics-Hardware] slider maximum to 128. This can be remedied by setting the RenderTextureMemoryMultiple Debug Setting to 1.0 and then setting the texture memory slider as high as you want it. Some of the TPVs like FS automatically do this for the Mac version so it might seem better since its utilizing more of the available video memory.
I don’t have a Mac, so I can’t test it. You are on your own.
On the Windows side, typically the value for RenderTextureMemoryMultiple is already set to 1. I can’t find any way to get my Preferences slider above 512mb of graphics memory. I have 2gb of video ram.
If your slider is maxing at something less than 512, this Debug Setting might help you clear the problem. It hasn’t helped me get it past 512.
I can’t get a sense of how many people are having this problem. I am hearing people bring it up more often. Some are saying they have been living with it on and off since 2007/2008.
If you are having this problem, please file a JIRA. The Lindens seem totally oblivious to this problem. That usually happens when JIRA on a problem are being filed.
Also, we see a bunch of new viewer versions coming out as release candidates and probably will for the rest of the year. So, if you see the problem again, after your viewer updates, make an addition to your JIRA report or file a new JIRA.
This problem is not going to go away until the Lindens fix it. They won’t fix anything they haven’t heard about or that is not an issue for a significant number of people. They have lots of things to fix plus the new stuff they want to add.