Object and values snapping back!!!

Okay, I just posted in another thread, that my experience improved, but I have one annoyance, a big one even.

Lately (weeks or so, maybe 2 months), objects that I move, snap back. Values that I change by typing them in the appropriate boxes (size, location, texture repeats, rotations, and so on) change back to what they were. Very often I have to do things twice to make them permanent. Makes building less fun... that's the civilized way of putting it

Now, is this behavior client side or server side? I work on a crappy laptop (actually, only crappy regarding graphics), have a high-speed connection (25Mbit), work wireless, if this info helps. I do see the changes I make on screen, and see it revert as well.

Dunno, but the same thing happens to me a lot lately. It's happened in the past too. Seems to be off and on.

Yes.

When you move something in the editor, you get feedback in real time, but it's not really set in stone yet. There will be some delay, normally very short, for the server to register the changes. If the sim doesn't get the changes (packet loss, etc.), you see the bounce back once the sim passes along its next update to the viewer.

I'm pretty sure it's a server side issue. It used to happen all the time in 2007 and early 2008, then the problem went away for a long while. I used to think that was down to an upgrade of my system but I noticed it happening again since they rolled out the new server.

I don't get it on the building side, but sometimes I really struggle getting textures to stay as I put them. Really weird when you can see the numbers changing over and over before your eyes.

I believe it's server-side, and yes, it's been driving me bonkers for the past couple months.

i encounter this frequently due to network issues (being 10,000 miles away and all).

Yesterday, I noticed that typed-in values sometimes didn't take; e.g. I'd type 0.100 into a box and it stayed as 0.000.

The only times I've come across what I've known to be a different cause was when I used to be silently logged out when editing an object. The edits went on for a long time as normal on the screen - sizes changed, positions altered, etc. etc. etc. - but behind the scenes I'd been silently logged out and all the work was wasted. I haven't had that happen in a couple of years though.

Oh gosh that used to be awful. I remember making something sitting up most of the night to find I had actually crashed and half the work was never actually done

I think what happens is that when you make a change, the viewer sends that change off to the sim then it (the viewer) shows you that change on your screen.

The problem happens when the sim doesn't get the update or is really slow to process it. Since it doesn't know the new setting, the object will snap back to the last settings that the sim knew whenever the sim updates that object.

Wireless is notorious for this sort of problem - network packets get lost and the sim can miss a lot of what you're trying to tell it to do, even though the client initially shows your changes to you.

Bugs in SL, namely SVC-4196 these last few months, also cause this. If the sim locks up for a bit, the edits you're sending it can get lost. Thankfully [sic], LL is planning to be all over that bug in only about 6 more months..

edit: er.. yeah.. like Viktoria said..

*Raises Hand*

Me too. Frustrating as hell.

So go vote for SVC-4196!!!

Thanks for all your reactions!

What I wonder, is why wireless packet loss, would have such an impact on SL, where each and every application I work with, works just fine. Somehow SL and wireless are indeed no good friends, but isn't it about time they change that? I mean, wireless is common these days, we are not living in the coax age anymore. Glad to know though, that this could be a cause, though I cannot solve it

Given any idiot can download a wep crack off the internet and be using up your bandwidth you pay for in seconds then basically only fools still use wireless. Well only fools or coffee houses still pay for the internet and hook up a wireless router for anyone to use. Throw it away and get a wire router.

This could all be fixed quite simply if LL would get rid of UDP and switch to HTTP for all client-server communications. The difference is huge: HTTP does not like dropped packets and will force a resend if a packet is dropped, whereas UDP ignores dropped packets entirely. The downside to this is, if you are on a problematic connection, the use of HTTP can cause your viewer to grind to a halt as your bandwidth gets clobbered with a ton of packet-resend requests and replies. UDP is great for streaming information that must be received in real-time, where timeliness is more important than accuracy, such as music and video streams, or other mainly-one-way traffic.

Only an idiot uses WEP these days. If you have a Wi-Fi connection and you're not using WPA or WPA2, with strong encryption keys, then you're a fool.

it's gotten so bad I've stopped building, it takes 3 or 4 times longer to get anything done, just a waist of time even trying till they get it fixed.