Gray loading textures - still.

I have a terrible gray loading texture problem, just the same, on three different computers.

The problem is not affected by removing the router from the path.

There are no firewalls; Window's firewall is completely disabled, I uninstalled the security program that came with the main computer, and the router's firewall is completely disabled.

What can it be? Can this be caused by the cable company throttling bandwidth? Have the Lindens just decided that I specifically shouldn't get to see textures on time? Am I in some kind of run in the nylon fabric of the spacetime continuum?

I could try getting an additional Roadrunner account, and make them run the cable in from the other side of my apartment, if they would. Or do the same with Earthlink or AOL, although they are all Time Warner based and would come in on the same cable, and I think the data would follow the same path along the internet, although I don't know that for sure.

If many people had the grayness like I have it I don't think SL would be doing too well. I think there'd be a bit more complaining than there is.

I don't really want to spend a couple hundred bucks on an nVidia video card if that is not gonna fix the problem. Since the grayness happens on more than one computer, I don't think that a new video card would help.

Can you borrow an NVidia card from a friend just for testing?

I rarely see the loading texture on a machine that is barely at the minimum spec, so I doubt spending money on a high end video card is likely to help you much with your problem.

Something about your network would seem far more likely. Perhaps some router in common with all of the ISPs you have tried?

Computer

1. Windows XP Professional
   
2. Athlon XP 2200+
   
3. NVIDIA GeForce4 MX 4000
   
4. 1 gig RAM
   
5. 10 gig drive
   

Network

1. Speakeasy ADSL 3.0/768
   
2. NetGear RT314
   

Tracing route to sim784.agni.lindenlab.com [69.25.105.216] over a maximum of 30 hops:

1. 1 ms 1 ms 1 ms 192.168.0.1
   
2. 16 ms 18 ms 19 ms er1.nyc1.speakeasy.net [66.92.76.1]
   
3. 16 ms 15 ms 15 ms 220.ge-0-1-0.cr2.nyc1.speakeasy.net [69.17.83.201]
   
4. 15 ms 14 ms 15 ms 166.90.136.33
   
5. 15 ms 15 ms 14 ms ae-2-56.bbr2.NewYork1.Level3.net [4.68.97.161]
   
6. 206 ms 106 ms 132 ms so-3-0-0.mp1.SanFrancisco1.Level3.net [209.247.8.89]
   
7. 91 ms 92 ms 91 ms ge-6-0-0.gar1.SanFrancisco1.Level3.net [4.68.124.206]
   
8. 88 ms 88 ms 87 ms 4.78.242.18
   
9. 89 ms 88 ms 88 ms border1.ge2-1-bbnet2.sfo002.pnap.net [63.251.63.65]
   
10. 89 ms 89 ms 89 ms sim784.agni.lindenlab.com [69.25.105.216]
    

Pinged with packets of 128, 256, 512, 1024 and 4096 with no loss. The times did get up to 200 ms for the largest.

good thing we have big brothers at the laboratory to address this

I've got an nVidia 6800 AGP 4x and the clouds are usually the last to load by about five minutes following login, far slower than every other texture.

There is no packet loss anywhere in the stack from the lowest level to the client, the SecondLife.log reads clean. This "feature" is new as of 1.7ish, clearing cache doesn't change it, reinstallation doesn't clear it.

It is all my fault, I'm sure, probably because I stood by helplessly at the age of eight while the neighborhood miscreants killed a frog by dropping a large stone on it. Karma be a bitch.

I had the same problem, where it took many minutes to load textures. I fixed it by doing the following:

- uninstall
- run regedit, and remove all keys that contain "secondlife"
- reinstall

When I started SL after doing this, the textures came up almost instantly...

- Jon

I have done this several times before, though not since the latest version.

I don't remember what problem prompted me to do that, it wasn't the gray slowding texture problem, but whatever the problem was, it solved, I remember that.

Slowding, by the way, is a neologism made by combining slow and loading. Not a typo.

Can anyone think of other registry entrys to delete besides ones that say Second Life?

Can't hurt to try it again, so long as I don't screw the registry up.

It's kind of disappointing to think that the LL staff can't write proper install and uninstall routines, that the "It's your world, your imagination" view extends to the contents of the Windows Registry, but I supposed one can look at this as a way of prompting the creation of registry cleaning businesses run by SL members.