Teleport Crash - No Forum Answers Have Worked

[Charolotte Caxton]

Here are some ideas: teleport? no

 

[Charolotte Caxton]

Here are some ideas: teleport? no

 

[Peggy Paperdoll]

The message stating that you have been logged out usually indicates a network problem.  Since there's no widespread complaints about the same issue it appears it's not on the server end.  That leaves somewhere between LL's servers and your RJ-45 connector on the back of your computer if you are hardwired.  If you are wireless, the problem is somewhere between your computer's wireless transciever and LL's servers.

 

A few things to try on your end.  If wireless, try connecting via a CAT5 Ethernet cable (hardwired).  Reset both your modem and router (if one exists in your home network).  Check for driver updates for your network card/adapter.  Check for firmware updates for your router (if one exists in your network).

 

If none of that fixes your problem you might try calling your ISP.  I know your upload and download speeds seem fine...........but it may not be if you are supposed to be getting 30 mbps down and 4 up.  Also we don't know your pings.  Go here:

http://www.speedtest.net/

Run a couple speed tests each to San Francisco, CA and to Dallas, TX..........those should be pretty close you what you are paying your ISP for at your service level.  Then run a couple ping tests each to the same locations.......your pings might be higher than you might expect but that's could be contributed to the total distance the test pings travel to the servers and back to your computer (anything under about 200 should be okay.......not excellent but enough that you should not time out and get disconnected from the LL servers).  One of the tests the Ping test does is it measures the packet loss..........if you are getting 3% packet loss you are marginal for staying connected to the servers.

 

[Nalates Urriah]

When you have a technical problem like this it is best to give us the specs of your computer. Login and click HELP in the top menu. Next ABOUT. Copy and paste that information with your request for help. That will save everyone time and hopefully get you a quick answer.

When your viewer crashes it is a good idea to restart your computer. Often processes remain running that create problems when you try to open the viewer. Also, the video state can be left in an unpredictable state. A restart handles both of those issues.

If you have an ATI video card, search the forum here for more information about your card and possible problems. Apple is not very good at supporting OpenGL something that SL uses heavily. Unfortunately the newest drive for ATI is not always the best driver for SL. The tp may have a video problem as textures load and unload. But, its a slim possibility.

Often crash problems are from bad settings. I don't know where they keep them on a Mac. The file is named settings.xml and it lives in a folder named user_settings. Where that is on your Mac can be found in the SL wiki. Rename that file and restart the viewer.

Teleport problems can be caused by the scripts you are wearing. Shoes and hair may have hundreds of scripts. Strip to clothes only and try tp'ing. Anything over 100 scripts on an avatar can cause problems. THe busier a region is the more likely the scripts will cause a problem.

Also where you are tp'ing from can make a difference. A seriously lagged region can cause tp problems. In Preferences->General is a setting to show a login location when opening the viewer. You can type in a region name like Pooley and login. Pooley is mostly deserted and empty. You should be able to tp out of that region. If not...

When you get the HELP-ABOUT info we can tell if you are in one of the release channels (RC). This past week they have had lots of problems. An update has a problem. Today they were rolled back. If you were in the RC's, it may be SL and not you.

 Peggy Paperdoll's suggestions are the most likely fix. But, this will give you bit more to consider.

[Peggy Paperdoll]

Thanks for updating your post.  So many people just don't do that........you're an exception.  Also thanks for the heads up with your PM a few minutes ago.  :matte-motes-big-grin:

 

Okay, I'm a Windows person and know next to nothing about Macs so I'm sort at a loss for much else you can do except update your network interface adapter.  The problem as you discribe it a network problem.  No amount of tweaking on the viewer is going to fix it.........you can "side-step" the problem with lowering your graphics preferences sometimes (but, as you know, not all the time).  The problem is that something is causing you to lose your connection to the servers.  When your viewer makes the requests for all that data to be downloaded for everything around you the servers are going to send it......if it overwhelms your connection the data stream will break down and the servers will dump your conneciton.  That problem can occur almost anywhere and the only things you can do to fix it are the things directly related to your computer and your home network.  It probably is not a video problem or CPU problem (both those devices in your computer are very capable of running SL fairly trouble free).  It could be your system RAM but I doubt it (by the way I don't see your RAM listed in the specs you posted....maybe Macs are different).  You might check with U-Verse........if they slow your connection down (or dump it) when they detect high rates of data being sent they might throttle it.  And that could disconnect you from the servers.  I'm not sure they will admit to that but you can check anyway.

 

Beyond that, I'm pretty much out of ideas.  Hopefully some Mac user(s) will come along with something else.

 

----------------------------------------------------------------------------------------

My speedtest results are good: http://www.speedtest.net/result/1374416990.png Here's where I tested to the San Francisco server: http://www.speedtest.net/result/1374418211.png

I'm using a hardwired RJ-45, no wireless, no router - I have AT&T U-Verse, so there is just a "Gateway". I restarted everything, to no avail.

Also, I'm not running any scripts or anything - I don't even have anything but the preloaded stuff in my inventory. I tried renaming the settings file, as well. AT&T is notorious for capping bandwidth and all kinds of wackiness, so I suppose it could have something to do with them.

Here's my sys info from SL:

Second Life 2.7.2 (233432) Jun 21 2011 17:17:16 (Second Life Release)Release Notes
You are at 261536.0, 233542.0, 22.3 in Zebrasil located at sim9700.agni.lindenlab.com (216.82.45.34:13006)Second Life Server 11.06.29.234329[ Release Notes]
CPU: Intel® Core i3 CPU         540  @ 3.07GHz (3060 MHz)Memory: 4096 MBOS Version: Mac OS X 10.6.8 Darwin 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386Graphics Card Vendor: ATI Technologies Inc.Graphics Card: ATI Radeon HD 4670 OpenGL Engine
OpenGL Version: 2.1 ATI-1.6.36
libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1J2C Decoder Version: KDU v6.4.1Audio Driver Version: FMOD version 3.750000Qt Webkit Version: 4.7.1 (version number hard-coded)Voice Server Version: Vivox
Built with GCC version 40001Packets Lost: 0/5008 (0.0%)

--------------------------------------------------------------------------------------------------------

[Madeea Nakamura]

I am having the same exact issue with the latest official release... 

 

Second Life 3.0.0 (238864) Aug 18 2011 13:35:24 

CPU: Intel® Core2 Duo CPU     T9600  @ 2.80GHz (2800 MHz)Memory: 4096 MBOS Version: Mac OS X 10.6.8 Darwin 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386Graphics Card Vendor: NVIDIA CorporationGraphics Card: NVIDIA GeForce 9600M GT OpenGL Engine
OpenGL Version: 2.1 NVIDIA-1.6.36
libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1J2C Decoder Version: KDU v6.4.1Audio Driver Version: FMOD version 3.750000Qt Webkit Version: 4.7.1 (version number hard-coded)Voice Server Version: Not ConnectedBuilt with GCC version 40001

[conner Svoboda]

After a great deal of searching, it is DEFINITELY a problem with Uverse and SL...and it only effects the Mac. In other words, the same modem will work perfectly on the same Mac running Windows with Bootcamp.

I have no idea where to start with solving their problem, and definitely don't have the hours to spend solving THEIR problem. Linden Labs should be discussing it with them, because chances are, many Mac users (like me) just aren't going to use SL until I hear they noticed the problem and fixed it.