Well, folks, I said I would play it all out here, here it is.
Start 06-06-06, somewhere about midnight, a conversation in SL:
"Sorry my friends, I want to start the club, but I am having severe technical issues. Live help was a total ass to me, so I am going to email LL in the morning."
I emailed, and recieved a quick and encouraging response:
**************************************
Hello,
Thank you for your inquiry.
I appreciate your detailed description of the issue. I also see that
you've been submitting crash logs whenever you crash. This is quite helpful.
Here's what I see that stands out in your crash logs:
Wearable download failed: Asset request: failed
*edited for privacy*
This message is repeated throughout your log, and leaves me to believe
that it's possible that an attached object may be the source of your
troubles.
I would like for you to detach all objects from yourself and respond
with the results.
If detaching all objects does not resolve the issue, I would like for
you to attach the log file generated by Second Life during its inital
startup phase in your reply.
The file is labeled Secondlife.log and is usually located in the
C:\Documents and Settings\(your user name)\Application
Data\SecondLife\logs folder on your hard drive.
If it does not appear in that directory, you will need to turn on hidden
file types. To do so, please select the "Tools" option at the top of
your open folder, then select "Folder Options." Next, click the "View"
tab and select "Show Hidden Files."
As a side-note, you've probably got this covered, but just to be sure:
You mentioned you have a fresh install of Windows and that you are not
running any firewalls. Have you shut off Windows Firewall?
Also, have you checked to make sure your router is configured for Second
Life? Check here for information on how that's done:
http://secondlife.com/tiki/tiki-index.php?page=TechConfigFirewall
Regards,
*****************************************
My next email I replied with the information that was requested, made sure my router had the correct serttings (it did), and sent some screen shots in. The reply was next day, and although not as quick, still as hopeful.
******************************************
Hello,
Thank you for your reply.
Your log file looks much, much cleaner, but I'm seeing an unusual number
of dropped and delayed packets.
I'd like to see if we might be able to track down the source of the delay.
A link to a useful program (WinMTR) for tracking down the source of
problems with connecting to Second Life, along with instructions, can be
found here:
https://secondlife.com/tiki/tiki-index.php?page=Experiencing%20packet%20loss
Please get back to us with these logs and we will see where the problem
comes from.
Also, could you please tell me what type of router you are using?
*************************************
Again, faithful and happy that I am getting something done, and there are responses and questions. A ball is rolling, until the next day......
*****************************
Greetings,
Ouch. That's definately some heavy packet loss. The first node would
be your own network then usually the 2nd/3rd node is with the ISP. We
can only control behaviour that goes on in the pnap area as that's our
own network. The team is looking at improving stability for computers
that meet our system requirements so hopefully the next couple patches
will stabilize such despite the heavy packet loss. I would keep running
WinMTR for a while at times to see if the packet loss continues and show
those logs to your ISP.
Regards,
(this was a different Linden than the one originally emailing me)
*******************************
Needless to say, I am not happy.
Why the hell am I shunted off the tech who was working with me? Why the hell am I told off basically, and told to wait for patches? Yah know, I might have stayed and continued paying for months, if I felt I was being worked with, and my problem was under investigation. I am so angry over this, and even though I wrote and asked the same question, all I was given was a blank How are we doing response. SINCE I GAVE ONE ALREADY, this is doubly frustrating, and insulting as well.
If 1.10.3 does not fix the problem, I will leave, as I have basically been told I don't matter.
and as to how long has this problem been going on
/111/8a/110189/1.html
the one forum I posted in, out of approximately 20 that I counted and read with very simuliar problems, and an unestimated number of folks who responded and said they had these problems too.
From this side of the fence, it looks like LL needs to fix this with 1.10.3