Why do I keep moving.

Sometimes when I just move, either flying solo or in a jet, or walking, I just won't stop. Passing through sims underground, water, off the map. I have to kill the SL session and relog.

Any reason or answers or fixes. Just asking, I know it's alpha and good alpha at that.
So I "DO" thank all who made it and I'm not complaining. Because it's Linux I can live with it.

Yes, I run the Linux Native Client, too, but this does not sound linux-specific to me. Rather, this sounds like one of the many interesting varieties of "crash" that Second Life is prone to on any system. There is not much you can do about it, except to note if particular locations seem more prone to this than others, and to avoid such areas if you find any.

Oddities like this can happen at pretty much any time, but seem to me to be associated most closely with high packet loss, which is one of the items detailed in the Statistics Bar, which might help you track down the causes, and is enabled by a menu item of that name in the View Menu.

The Statistics Bar reveals much information that is both useful and useless for tracking the causes of problems. Clicking on an entry causes it to expand with a bar graph. Clicking again reveals an extended bar graph with more history. Clicking a third time returns to the original text display for that entry. Some "entries" are titles for whole folded SECTIONS. Play with this, and see if anything listed there correlates to when you have problems, then report back. When we have more data, we might be able to help you better.

Good luck!

That's an effect due to packet loss over the network, you continue on your last registered path as sometimes you suddenly snap back to a reasonable position. It happens both in windows and linux. Sometimes it is possible recover from such a thing if you were doing script assisted movement(fast movement) as you can sometimes get the map up or a saved location and teleport back onto a valid sim. Be careful on island or edge sims as assisted movement can launch you out of bounds sometimes.

I will try to work out the Stats Bar and keep an eye on it.
Yes it does seem to have happened in certain areas and I watched myself go out of bounds around the "fantastic" main sandpits and another one or two places and continue into the never never.
Also I have to persist with a 256k connection on a 1.6ghz pc and crossing sim boundaries in an aircraft gives a great jerky movement so I never know if I've survived for a few seconds.

(By aircraft, I mean a TerraClaw Jet that a young relative purchased for me while I wasn't watching him on my pc. I let him fly my av around and he found the showroom at Abbotts airport next to the sandpit I left him at. Now I have a great L$600 plane that I can't really use because of the lag. I've tried to fly around but always, always find the plane returned to me after comming unstuck.)

This is one of the biggest gripes I have. It happens in most places because I go there. It can move me a couple of sims or I bounce back.
I cant watch that system thing cause I dont know what its telling me and I dont want to learn.
If I had something else to do I'd do it.
(Dont reply)

This Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Offthis Really Pisses Me Off

If you want to see exactly when your connection drops, open the Client debug menu (CTRL ALT D) and switch off "Network / Velocity Interpolation" (from memory). This will disable the client's estimation where you or other objects will end up at their current velocity before waiting for the server to syncronize. You will notice a lot of jerky movement the client usually interpolates, but you will instantly see when you freeze.

Note that you also will not see llTargetOmega() movements anymore, so don't bug report this as I did once

Closed to keep the forum more focused on linux problems.