|
|
|
Eren, this is something that is more related to your specific computer rather than all users as a whole. I am unable to reproduce a 20 minute texture load on either of my two machines. You are free to contact support on this.
Alexa, with all due respect, this is NOT something related to my computer. I'm sorry you can't reproduce the problem... but maybe you need to try from a remote system that's not directly connected to Linden Lab networks.
This texture loading problem is widespread and has had numerous complaints from users all over the grid. The texture loading issue is well-known, well-documented, and I guarantee you it is not specific to my computer. I have a killer quad-core system, an Nvidia 8800 512meg graphics card, 4 gigs of ram, a 6.5mb clean cable internet feed, and I'm a systems analyst. So I think I know my stuff, my computer rocks... and Linden Lab has serious texture resolution problems. Once again Lindens... your customers and their computers are not the problem. IT'S YOUR SOFTWARE and DATABASE STRUCTURES. I mean seriously, no insult intended, but your company can't even get chat right and your databases lose inventory items on a regular basis. So the problem is my computer? Get serious and let's put the blame where the blame lies. It's not your customer's computers. Forgive me putting it this way, but no wonder Linden Lab has major bugs that are years old. It's like the alcoholic who denies he has a problem. To fix the problem, you have to first recognize it exists. Examining the history of similar reports on this JIRA:
REFERENCE: This user did not report a "20 minute texture load" (although such is very common on SL). He reported being in a market for 20 minutes, and after clicking on a vendor the texture still not showing up after two minutes. As claimed in this JIRA, texture loading bugs are prevalent, documented and as Lex Neva pointed above, Linden Lab is aware of it. This would appear to not be a problem with the user computer but as pointed out, coding and database issues. This calls to question why this bug report was twice marked as "resolved" by Linden Lab, why it was labeled as "misfiled" and why the poster was directed to contact customer support. This is a reported and widespread bug, not a customer specific problem. Seems like Linden Lab employees are getting tired of handling multitudinous JIRA reports. ; ) This is a problem because in the 5 years since it was first reported, Linden Labs hasn't bothered to convert the UDP texture loading to HTTP; which is well known to be much, much faster. And, despite hundreds of people voting for this issue to be fixed, the Lindens have put bells & whistles ahead of fixing this very basic problem which is the cause of the vast majority of the lag problems in Second Life. If they would just fix this, the number of complaints they'd have to field would drop significantly, giving them more time to work on their infernal bells & whistles.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
So if we don't file bugs about textures on JIRA... exactly where do we file them? And as a Linden Lab employee, how do you consider it proper customer response to say something is "misfiled" without a word of explanation or suggestion as to how to better file it?
No disrespect intended Alexa, but seriously folks, you make customers wonder why we even waste our time with this. We don't file JIRA reports just because we enjoy paperwork.