TECHNICAL SUPPORT / WEB APPs BUGS

Hello,

This is a problem that some players have regardless of operating system or computer setup; You are walking along normally, but then are thrown back 2m-5m (occasionally much more) and this can happen repeatedly and in rapid succession- so forward movement is slow or nearly impossible.

I personally have tried adjusting the graphics settings, freeing up more system memory, using older vs. newer clients, and even cleared the Ryzom cache, but the problem still occurs.

This happens for me, BUT only right after I logon, after about 15-30 seconds, it no longer happens, to me.

Generally spoken, rubberbanding stems from delayed synchronization of server and client position data. Of course, server position data are authoritative, while client position data are an interpolation in case updates respectively acks from server are not received in a timely fashion.

I suffered ways worse position updates in other MMOs, sometimes resulting in several 100m teleports, in worst case into the mid of agro mob packs. Compared with that, Ryzom rubberbanding, even when happening in a nasty way, is ways more benevolent in most cases. Ok, when running from KP, a setback of some 50m may be deadly ..

I did not suffer significant rubberbanding during the last months, the phenomenon was more widespread one or two years ago. I think the 64bit migration of server code or other engine or hardware updates brought significant improvements. Yet, synchronization over a worldwide network will always remain a challenge, and it is well possible that I am viewing it from my privileged position with a few ten milliseconds response time of shard.ryzom.com to my clients in Europe.

I'd check the connection. Changing from wireless to wired might help.

Hopefully a short read can help shed some light on this.
Ryzom as far as I am aware use UDP. as such the data can get out of order.

http://www.diffen.com/difference/TCP_vs_UDP

Fatecity: Most of the MMOs I know use UDP for frame exchange between client and server. Using TCP for that purpose would cause a lot of overhead and possible troubles as far as I understood this kind of architecture.

For the game ongoing it is not of any importance if client and server are out of sync for short periods of time, and it would cause lots of delays and overhead to force that. It is best practice to my understanding to allow some interpolation by the client during short periods of time when it is not in sync with the server, correcting that by a couple of methods which may in less pleasant cases result in teleporting or rubberbanding.

A fully synchronous connection would result in endless lags and/or server overload.

Daomei: I wasn't trying to say TCP was a solution it is not. 
My intent, and in retrospec was not clear, with the link was to show the differances, and what each is suited for.

In my case the "rubber banding" only shows up real badly during "prime-time" between 5pm and around 11pm local. This is, from my understanding, due to the increased traffic on the local networks making it easier for the packets to get lost.

Thanks for the response, Fatecity. I am aware how privileged we in Europe are being closer to the server. I assume you are in AU/NZ, are you? Possibly there is also a problem with the transcontinental links and hubs from Asia/Pacific to Europe, I recall from my work that we had to mind latencies at specific times in that direction but not A/P to the Americas.

No, I am in America, however it is a rural area. The western part of Colorado.
If I was nearer a larger metropolitan area it would not be an issue. There are still large areas in the "West" that are devoid of decent broadband connections. Even our cable connections here, are rather slow capped at around 50mbps. not that you ever see that speed given the nature of cable internet. The ASDL available is maxed in most areas near here to 12mbps Down and only 896kbps up.

P.S. There are large areas near me that the only options are satelite or dial-up and the dial up is only around 28kbps maxed.