You may have seen the syndrome of your avatar stuck in a perpetual cycle of rebaking. Blurry one second, clear the next, rinse and repeat. This is most likely due to HTTP textures not playing well with your system and or network. HTTP textures is one of those settings that either works for you, or it doesn’t. If it doesn’t, well, you get the aforementioned scenario. Then there are others who are able to use it, and textures come in to view quickly and without any hair pulling by you, your computer and network, or the viewer. So what’s best? On or off? Well, it depends. HTTP textures are kind of iffy. When they work, things rez beautifully and quickly. When they don’t…eh….they don’t.
But what is HTTP textures you ask? It’s simply a second way for your viewer to pull textures from the server to your cache. It’s one of two ways, actually. The first way is called UDP. With UDP, textures are requested by your viewer to the region. The region then tells the server “I need these textures to go to this viewer, please.” Then the server says, “one minute. Let me find them.” When the server finds the textures, it hands it off to the region and the region then hand delivers the textures to your viewer that then caches it locally on your computer.
With HTTP textures, you skip the hand off between the viewer and the region and pull the textures directly from the server via HTTP protocol. In most cases, it’s a very fast and efficient method to pull the info for what’s needing to be rendered. In the worst case scenario, it gets botched up somewhere and just doesn’t work well. That’s when you get the blurry-clear-blurry-clear-rinse and repeat syndrome in how your avatar ultimately bakes. The graphic below will help walk you through basic troubleshooting of this annoying occurrence that will hopefully fix you. Do keep in mind that if turning OFF HTTP textures fixes the issue, it’s best to leave them off for the future.
NOTE: The following image is fairly large, but it should load quickly on a decent connection.