Unable to Cross Sim Borders after 1.13.2

After updating to 1.13.2, I have been unable to cross sim borders, whether that be by TP, walking, or flying. As soon as I hit the border, I crash. ATI All-In-Wonder 8500 may no longer meet the minimum system requirements of SL.

My system specs are:

CPU: 0.18 micron Intel Pentium 4 (1917 Mhz)
Memory: 1152 MB
OS Version: Microsoft Windows XP Service Pack 2 (Build 2600)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: RADEON 8500 DDR x86/SSE2
OpenGL Version: 1.3.1072 WinXP Release

I've tried to resolve this with Lucy, Teeple, Spike, George, and Lexa Linden, as well as placing a phone support message. The best we are able to come up with is that the ATI Radeon 8500 graphics card listed as meeting SL's minimum specifications requirements is no longer supported by SL. It doesn't appear related to my account, as I am able to TP when I use another, albeit significantly slower, PC. We've tried reinstalling the SL client & updating the catlyst graphics drivers for the ATI card (in addition to trying to TP to Georgean, removing all attachments/scripts, and walking/flying across sim borders).

It would be helpful to know if anyone successfully runs SL with the ATI All-In-Wonder 8500/8500DV card.

It seems odd that SL loads fine and runs fine while within one sim and that the crash is generated only when crossing a sim border, regardless of what's going on in terms of graphics usage at the sim border.

I've tried chaning a few of my graphics settings, including, lowering display details and running on fullscreen mode. If anyone has any further suggestions as to what changes in graphics settings, or any other settings for that matter, might help try to resolve the issue of crashing at sim borders, I would appreciate your feedback. I understand that my card is on the low end and I would improve my experience in SL by upgrading ... the point of this thread is ATI 8500 compatiblity and crashing when crossing sim borders with 1.13.2.

Four days after last week's patch, I'm able to TP again. It wasn't my client as the problems continued for 2 days after reinstalling SL and re-updating my drivers (which were already current). However, the problem did seem related to my network address; I was able to cross-sim borders on a different computer on a different network.

I believe it was a network problem .. something in the code that sometimes prevents a resident from being able to cross-sim borders and then clears up after a few days. Teeple seemed to think this was a possibility as he had recieved a few similar reports and was/is beginning to track the issue. Perhaps, someone's figured out a way to attack an AV that prevents them from crossing a sim border. I don't know why I would be targeted by such an attack, but, short of a code problem, that would explain it.

In any event, I just wanted to let people know if SL is only crashing upon a specific event in SL, and 'quits' as opposed to freezing or locking up, and are told they need to update their hardware and/or drivers which meet the minimum operating system requirements, wait a few days to see if the problems don't clear up before rushing out and getting new hardware. Once and if you have verified a network problem interfering with your SL experience, please post here to let the Lindens know about the problem so that it might be fixed/addressed sometime.

One might consider posting bugs using the bug tracking system at http://jira.secondlife.com .

thank you .. i will do that as this problem seems to have occurred again after yesterday's update. As before, I can no longer cross a sim border without client crashing. I suspect it will clear up in a few days.

Hey there, sorry you are having these problems. You're not alone though. Check out this thread with a user who has similar problems.

/327/73/163872/1.html

There are lots of suggestions in this thread including some from a Linden. It's possible it is not your graphics card at all and may be related to a rare occurence of an overactive firewall.

It took some bumping and grinding, but, I finally did confirm that it was my firewall, not an attachment, graphics card, or many of the other suggestions made.

The problem arose with the new network code brought in December and implemented in January.

The Linden Labs instructions for configuring a firewall state that you need to open port 12043 for TCP traffic. However, this is not enough. In addition to opening port 12043 to TCP traffic, you also need to set the flags to remember the state of connections made on port 12043 so that subsequent connections can be made on the same port through the same traffic stream. Not all firewalls set the appropriate flags simply by openning a port; many require you expressely set the flags to maintain persistent connections.

With IPF (a very common Linux/Unix based firewall) the correct setting is:

pass out quick on rl0 proto tcp from any to any port = 12043 flags S keep state

Complete rules for Second Life with IPF are as follows:

pass out quick on rl0 proto tcp from any to any port = 443 flags S keep state
pass out quick on rl0 proto udp from any to any port = 12035
pass out quick on rl0 proto udp from any to any port = 12036
pass out quick on rl0 proto tcp from any to any port = 12043 flags S keep state
pass out quick on rl0 proto udp from any to any port 12999 <> 13051
pass in quick on rl0 proto tcp from any to any port = 443 flags S keep state
pass in quick on rl0 proto udp from any to any port = 12035
pass in quick on rl0 proto udp from any to any port = 12036
pass in quick on rl0 proto udp from any to any port 12999 <> 13051

I will be posting this where it might be incorporated into the instructions for configuring firewalls so that others won't have so much difficulty figuring out what's not working right.

Little Gray

Love that ruleset language since someone mentioned they had a rule "pass out quick from cheap_gin" in theirs.